Post ForgeCode Feature
Generate a punchy, developer-friendly Twitter/X post for a ForgeCode feature. The post always accompanies a video, so no need to describe every detail; the video does the showing.
Workflow
-
Understand the feature: use tools to read the relevant source code, docs, or changelogs. Answer:
- What does it do?
- When would a developer reach for it?
- What pain does it remove?
-
Craft the post: follow the constraints in
references/style-guide.md. -
Present for approval: show the post and ask if the user wants tweaks before finalizing.
Key Constraints
- 2-3 sentences max (fits ~280 chars).
- No filler phrases ("excited to announce", "game changer", "introducing").
- Always refer to the product as "ForgeCode", never "Forge" alone.
- No em dashes anywhere in the post.
- Lead with the developer benefit or the problem solved, not the feature name.
- The video is attached. Do not say "watch the video" or describe what is in it.
- End with a relevant hashtag line (see style guide for approved tags).
Reference Files
references/style-guide.md: tone, vocabulary, approved hashtags, and example posts. Read this before drafting.