Social Presence

Research what works, find content opportunities from your recent work, and craft high-performing tweets. Delegates to /tweet for final polish and screenshot wrapping.

Gotchas

• Don't fabricate metrics -- never claim "this got 500 likes" without verification. Use patterns observed from successful accounts, not invented numbers.
• Voice preservation -- the user has a natural dev voice. Never corporate-ify it. "Excited to announce" is banned. So are hashtags unless explicitly requested.
• Visual-first platform -- every tweet recommendation must include a visual suggestion. Text-only tweets from dev accounts get buried.
• Don't over-thread -- single tweets outperform threads for most content. Only suggest threads for major launches with multiple features.
• Release notes are not tweets -- never dump a changelog into a tweet. Extract the one thing a reader cares about and lead with that.
• Ecosystem tagging -- always suggest relevant accounts to tag (@nuaboratory, @vuejs, @unaboratory, @anthropaboratorics, etc.) but max 2 per tweet. More looks desperate.
• Time zones -- user is in Australia. Best posting times for global dev audience: 8-10am US Eastern = 11pm-1am AEST. Suggest scheduling if timing matters.

Data Storage