Summary

Draft the social posts that seed the ApexYard v1.0 launch blog post (me2resh/me2resh.com#56). Outputs live in this repo at projects/apexyard/launch/social.md so they can iterate independently.

Scope

1. Twitter thread (6 tweets)

• Tweet 1: opening hook — "I shipped 5 products alone with Claude Code. Here's what I learned about prompting."
• Tweets 2-4: one per gate (merge gate, migration gate, ticket-vocabulary rule) — one concrete failure mode + one hook that blocks it, per tweet
• Tweet 5: what changes in practice ("one inbox, zero accidental merges, every decision has an AgDR")
• Tweet 6: CTA + link to the blog post + link to the landing page

Each tweet ≤ 280 chars. No threading characters (1/, 2/). Cohesive but each tweet standalone-readable.

2. LinkedIn post (one longer post, ~250-350 words)

Same arc as Twitter thread but in prose form. Opening hook, problem, ApexYard as the answer, three concrete gates, what changes, CTA + link. LinkedIn rewards longer-form than Twitter.

3. Placeholder URL

Link to https://me2resh.com/blog/apexyard-where-projects-get-forged (matches the slug of the blog post's file). Link is dormant until me2resh/me2resh.com#56 merges; user publishes socials after the blog post is live.

Acceptance criteria

• Both drafts live at projects/apexyard/launch/social.md
• Twitter thread has 6 tweets, each ≤ 280 chars (including URLs counted as 23)
• LinkedIn post 250-350 words
• Voice matches the launch blog post (direct, em-dashes, second person)
• Both drafts reference the blog URL + the landing URL (yard.apexscript.com) + the GitHub URL

Out of scope

• Publishing the posts to Twitter / LinkedIn — user publishes manually after the blog post goes live
• Bluesky, Mastodon, Hacker News, or any other channel (can be added later if wanted)
• Images / screenshots for the posts (prose only for the first pass)