Post Forge 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.

Twitter Post Style Guide - ForgeCode Features

Tone

• Direct and technical, written by a developer, for developers.
• Confident but not hype-y. Let the feature speak for itself.
• Conversational, not corporate.

Vocabulary

Prefer:

• "ForgeCode", "agent", "task", "context", "codebase", "workflow"
• Short, active-voice sentences.
• Concrete nouns over abstract ones ("file watcher" not "intelligent monitoring capability").

Avoid:

• "Forge" alone as the product name. Always use "ForgeCode".
• Em dashes (--) anywhere in the post. Use commas, colons, or periods instead.
• "excited to announce", "thrilled", "proud to share"
• "game changer", "revolutionary", "supercharge", "unlock", "seamlessly"
• Passive voice ("it can be used to...")
• Jargon that non-Rust developers won't know (unless the feature is Rust-specific)

Structure Template

[Problem statement or developer benefit, 1 sentence]
[What the feature does / how it works, 1 sentence]
[Optional: when to use it or a concrete example, 1 sentence]

#ForgeCode #[FeatureTag] #AICode

Approved Hashtags

Always end with #ForgeCode. Add 1-2 from the list below that best fit:

• #AICode - general AI-assisted coding posts
• #DevTools - tooling and workflow improvements
• #RustLang - Rust-specific features
• #CLI - command-line interface features
• #CodeReview - review and diff-related features
• #Agents - agent orchestration features
• #ContextWindow - context management features
• #Autocomplete - code completion features

Example Posts

Custom agents:

ForgeCode lets you define custom agents for specific tasks: code review, refactoring, docs. Each agent gets its own system prompt and tool set. Less context noise, better results.

>

#ForgeCode #Agents #DevTools

Shell integration:

ForgeCode's shell plugin tracks your terminal history and feeds relevant context to the agent. No more copy-pasting commands to explain what went wrong.

>

#ForgeCode #CLI #DevTools

Multi-file edits:

ForgeCode can plan and apply changes across multiple files in a single task. Rename a type, update all call sites, fix the tests, done in one pass.

>

#ForgeCode #AICode #DevTools

Context compaction:

Long tasks no longer blow up the context window. ForgeCode automatically compacts older turns while keeping the essential state. Tasks that used to fail mid-way now run to completion.

>

#ForgeCode #ContextWindow #AICode

Checklist Before Finalizing

• [ ] 2-3 sentences, fits ~280 characters
• [ ] No banned phrases
• [ ] No em dashes
• [ ] Product is referred to as "ForgeCode" throughout
• [ ] Leads with benefit or problem, not feature name
• [ ] Does not reference the attached video
• [ ] Ends with #ForgeCode and 1-2 relevant hashtags