post-forge-feature · git:20260321.bba73fb · 2026-03-21 · sha256 94b54017d7a71dc6
post-forge-feature git:20260321.bba73fbA
Immutable. This exact content never changes and is served at /api/v1/blob/94b54017d7a71dc6.
---
name: post-forge-feature
description: Generate a Twitter/X post highlighting a Forge feature. Use when the user asks to write a tweet, create a Twitter post, or promote a ForgeCode feature on social media. The post always accompanies an attached video demonstrating the feature.
---
# 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
1. **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?
2. **Craft the post**: follow the constraints in `references/style-guide.md`.
3. **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.