X/Twitter Changelog Post Writer

Write an X/Twitter changelog post following these strict guidelines.

Format Structure

[One clear thought/headline - what shipped or what's new]

• [Bullet 1 - key capability or feature]
• [Bullet 2 - key capability or feature]
• [Bullet 3 - key capability or feature]
• [Bullet 4 - optional, key capability or feature]

[Optional: Final CTA or statement with arrow if linking below]

Rules

Formatting

• Start with one strong declarative statement about what shipped
• Follow with empty line, then 3-4 bullets using • (not -)
• Optional: End with CTA line using arrow Unicode (↓ or →) if there's a reply with link
• Use Oxford commas in all lists

What to Avoid

• No emoji ever
• No hashtags ever (down-ranked by algorithm)
• No em dashes (use commas or periods instead)
• No self-mentions/tags (never @YourCompany in your own posts)
• No filler words ("just", "simply", "easily", "really")
• No passive voice
• No jargon or complex words when simple ones work

Writing Style

• Active voice only
• Implicit second person (don't say "you can" - just state what's possible)
• Concise and direct
• Focus on what developers can do now
• Focus on what's newly possible
• Simple words only

Technical Notes

• Use whitespace Unicode character (ㅤ) to prevent unwanted URL unfurling
• Use whitespace Unicode to avoid starting a post with a mention
• Don't include both image/video AND a link in same post
• If using video: add reply tweet with link, end main post with CTA like "Learn more below ↓"

Examples of Good Structure

Example 1 - Feature Launch:

Instant Rollbacks are now available.

• Revert any deployment in one click
• Automatic traffic shifting with zero downtime
• Full audit log of all rollback events
• Works with all framework presets

Available now in your dashboard.

Example 2 - With Video CTA:

Ship faster with our new AI code review.

• Catches bugs before they hit production
• Suggests performance optimizations inline
• Learns your codebase patterns over time
• Integrates with your existing PR workflow

See it in action below ↓

Example 3 - API Update:

The Edge Config API now supports atomic writes.

• Batch multiple updates in a single request
• Guaranteed consistency across all edge locations
• Sub-millisecond propagation worldwide

Read the docs →

Task

Write an X changelog post for the following update. Ask clarifying questions if needed about the feature, target audience, or whether there will be accompanying media.

$ARGUMENTS