chore(skill): add post-forge-feature skill for Twitter/X posts

[tusharmath]

Summary

Add a post-forge-feature skill that generates concise, developer-friendly Twitter/X posts for ForgeCode features, with a consistent style guide enforcing tone, vocabulary, and formatting rules.

Context

Promoting ForgeCode features on social media requires a consistent voice and format. Without a structured skill, posts risk using hype-y language, inconsistent product naming, or poor formatting. This skill codifies the rules once so every generated post is on-brand and ready to publish alongside an attached video.

Changes

• Added .forge/skills/post-forge-feature/SKILL.md: skill definition with a 3-step workflow (understand the feature, craft the post, present for approval) and key constraints (2-3 sentences, no em dashes, always use "ForgeCode", no video references)
• Added .forge/skills/post-forge-feature/references/style-guide.md: detailed style guide covering tone, vocabulary rules, approved hashtags, four example posts, and a pre-publish checklist

Key Implementation Details

The skill uses a two-level progressive disclosure design. SKILL.md contains the core workflow and constraints (loaded when the skill triggers). The style guide is a separate reference file loaded only when drafting, keeping context usage minimal. The references/style-guide.md explicitly bans em dashes and "Forge" alone as the product name, with those rules also mirrored in the checklist so nothing slips through.

Use Cases

• User asks: "Write a tweet for the new ForgeCode shell plugin feature"
• User asks: "Create a Twitter post about the context compaction update"
• User asks: "Promote this ForgeCode release on social media"

In each case the skill investigates the feature from source/docs, drafts a 2-3 sentence post using ForgeCode branding and the approved hashtag set, then presents it for approval before finalizing.

Testing

Load the skill in a new session (skills are registered at session start) and prompt:

Write a Twitter post for the ForgeCode multi-file edit feature.

Verify the output:

• Uses "ForgeCode" (not "Forge")
• Contains no em dashes
• Is 2-3 sentences
• Ends with #ForgeCode and 1-2 relevant hashtags
• Does not mention the attached video

[augmentcode]

🤖 Augment PR Summary

Summary: Adds a new Forge skill for generating concise Twitter/X posts that promote ForgeCode features.

Changes:

• Introduced the post-forge-feature skill with a short workflow and concrete post constraints (2–3 sentences, benefit-led, no hype)
• Added a dedicated style guide covering tone, banned vocabulary, required structure, approved hashtags, and sample posts

Technical Notes: The skill centralizes writing rules by pointing authors to references/style-guide.md before drafting.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 3 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

The skill description says “highlighting a Forge feature”, which conflicts with the later constraint to never refer to the product as “Forge” alone; consider aligning the metadata wording to avoid inconsistent outputs.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

This says “relevant hashtag line”, but the referenced style guide requires always ending with #ForgeCode plus 1–2 approved tags; consider restating that here so the constraint can’t drift from the guide.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

“Em dashes (--)” is a bit ambiguous since -- isn’t an em dash character (—); consider clarifying which forms are disallowed (e.g., both — and --) to prevent misinterpretation.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[graphite-app]

Inconsistent product naming violates the stated constraint. The description says "Forge feature" but line 25 explicitly states "Always refer to the product as 'ForgeCode', never 'Forge' alone." This creates conflicting guidance that could cause the skill to generate incorrect posts.

description: Generate a Twitter/X post highlighting a ForgeCode 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.

Suggested change

	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.
	description: Generate a Twitter/X post highlighting a ForgeCode 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.

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.