x-devs

Files (2)

• README.md
• SKILL.md

SKILL.md (first lines)

# 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

| Segment | What they share | What they consume |
|---------|-----------------|-------------------|
| Open source maintainers | Project updates, war stories | Industry news, peer projects |
| Tech leads | Team learnings, hiring | Architecture, management |
| Indie hackers | Building in public, MRR | Growth tactics, tools |
| DevRel | Content, events, community | Trends, developer sentiment |
| Framework authors | Updates, opinions | Feedback, community vibes |
| Learning devs | Questions, progress | Tutorials, inspiration |

### What Works on Dev Twitter

| Content type | Engagement level | Notes |
|--------------|------------------|-------|
| Technical threads | High | Deep dives get saved/shared |
| Code screenshots | High | Visual, scannable |
| Hot takes | High (risky) | Can backfire spectacularly |
| Building in public | High | Journey > destination |
| Memes | Medium-high | Know your audience |
| Announcements | Medium | Better with context |
| Tutorial links | Medium | Need compelling hook |
| Retweets with comment | Low-medium | Add real value |
| Plain links | Low | Algorithm deprioritizes |

### The Algorithm (As We Understand It)

| Factor | Impact |
|--------|--------|
| Replies in first hour | High — signals engagement |
| Time spent on post | High — threads > tweets |
| Profile visits from post | High — interesting content |
| Bookmarks | High — "save for later" |
| Retweets | Medium — distribution |
| Likes | Medium — engagement signal |
| Link clicks | Low — X wants you on platform |
| External links | Negative — deprioritized |

---

## 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

| Pattern | Example |
|---------|---------|
| **Contrarian** | "Hot take: You don't need Kubernetes for most apps" |
| **Promise** | "How we reduced our AWS bill by 60% (thread)" |
| **Story** | "Last week our API went down for 4 hours. Here's what happened:" |
| **List tease** | "7 TypeScript tricks that changed how I code:" |
| **Question** | "Why do most startups get database migrations wrong?" |
| **Result** | "We went from 0 to 10K users in 30 days. Here's the playbook:" |

### Thread Writing Best Practices

| Element | Guideline |
|---------|-----------|
| **Length** | 5-12 tweets optimal |
| **First tweet** | Hook — no hashtags, no links |
| **Each tweet** | One idea, complete thought |
| **Numbering** | Use X/10 format or emoji bullets |
| **Code** | Screenshots > text (more engaging) |
| **Pacing** | Mix short punchy + longer explanatory |
| **Last tweet** | CTA: follow, reply, bookmark |

### 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:

From jonathimer/devmarketing-skills, MIT.

More from jonathimer/devmarketing-skills