X/Twitter for Developers

Twitter/X remains the real-time pulse of the developer community. This skill covers thread structure, code screenshots, engagement tactics, and building an authentic developer following without being cringe.

Before You Start

1. Read .agents/developer-audience-context.md if it exists
2. Audit your current X presence (bio, pinned, recent posts)
3. Understand: Developer Twitter rewards authenticity and technical depth

Understanding Dev Twitter

Who's on Dev Twitter

What Works on Dev Twitter

The Algorithm (As We Understand It)

Thread Structure

Thread Anatomy

Tweet 1: HOOK
↓
Tweet 2: Context/Promise
↓
Tweets 3-8: The meat (examples, steps, insights)
↓
Tweet 9: Summary/Takeaway
↓
Tweet 10: CTA + Engagement ask

Hook Patterns That Work

Thread Writing Best Practices

Thread Template

🧵 [Hook: Compelling statement or question]

Here's what I learned [context]:

1/ [First key point]

[Supporting detail or example]

2/ [Second key point]

[Code screenshot or visual]

3/ [Third key point]

The counterintuitive part:

[Insight that surprises]

4/ [Fourth key point]

Common mistake to avoid:

[What not to do and why]

5/ [Summary]

TL;DR:
• Point 1
• Point 2
• Point 3

If this was helpful, give me a follow @handle for more [topic].

What's your experience with [topic]? 👇

Code Screenshots

Why Screenshots Beat Code Blocks

Code Screenshot Tools

Screenshot Best Practices

Engagement Timing

Best Posting Times

Posting Frequency

Thread Timing

• Post threads in morning (7-10 AM PT)
• Engage replies for first 2 hours
• Quote tweet your thread later in day
• Post follow-up content same day

Hashtags (Use Sparingly)

Developer Hashtags

Hashtag Rules

Building a Dev Following

The Flywheel

1. Create valuable content → People engage
2. Engage with replies → Build relationships
3. Reply to others' posts → Get discovered
4. Consistency → Algorithm favors you
5. Followers grow → More reach
6. Repeat

Profile Optimization

Bio formula:

[Role] at [Company/Project]. Building [what].
Tweeting about [topics]. [Credibility signal].

Examples:

Engineering @ Vercel. Building the web, one component at a time.
Tweeting about React, Next.js, and developer experience.

Indie hacker. Building saas.com ($10K MRR).
Writing about startups, coding, and building in public.

Reply Strategy

Good reply patterns:

• Add information they missed
• Share your experience
• Ask thoughtful follow-up
• Respectfully disagree with reasoning

What to Avoid (The Cringe Zone)

Content That Fails

Behaviors to Avoid

The Authenticity Test

Before posting, ask:

1. Would I say this in person?
2. Is this genuinely useful or interesting?
3. Am I adding to the conversation?
4. Would I respect someone who posted this?

Platform-Specific Do's and Don'ts

Do's

1. Do share real experiences and learnings
2. Do use visuals (code screenshots, diagrams)
3. Do engage in first hour after posting
4. Do build in public authentically
5. Do reply thoughtfully to others
6. Do share credit and amplify others
7. Do be consistent in posting schedule
8. Do have opinions (respectfully)

Don'ts

1. Don't be a reply guy with no original content
2. Don't use AI to generate generic content
3. Don't copy popular threads verbatim
4. Don't pitch in DMs uninvited
5. Don't use more than 2 hashtags
6. Don't post links without context
7. Don't be negative/dunking constantly
8. Don't automate engagement

Content Calendar

Weekly Template

Content Mix

Tools

Thread Checklist

Before posting:

• Hook is compelling (no links, no hashtags)
• Each tweet is a complete thought
• Code is in screenshots, not text
• Thread is 5-12 tweets
• Summary/TL;DR included
• CTA at the end
• Scheduled for optimal time
• Ready to engage for first 2 hours

Related Skills

• developer-audience-context — Know who you're talking to
• dev-to-hashnode — Turn threads into blog posts
• linkedin-technical — Cross-post for B2B reach
• hacker-news-strategy — Drive traffic from X to HN posts