x-devs

Name: x-devs
Author: jonathimer

70installs6forks

How to install x-devs?

jonathimer/devmarketing-skills/x-devs

$npx -y skills add jonathimer/devmarketing-skills --skill x-devs

Installs into the current project.

Summary

When the user wants to build a developer following on Twitter/X, write technical threads, or understand what works for dev audiences on X. Trigger phrases include "Twitter," "X," "developer Twitter," "tech Twitter," "technical threads," "building dev following," or "Twitter for d

Files · 1

View on GitHub

SKILL.md

1	# X/Twitter for Developers
2
3	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.
4
5	---
6
7	## Before You Start
8
9	1. Read `.agents/developer-audience-context.md` if it exists
10	2. Audit your current X presence (bio, pinned, recent posts)
11	3. Understand: Developer Twitter rewards authenticity and technical depth
12
13	---
14
15	## Understanding Dev Twitter
16
17	### Who's on Dev Twitter
18
19	\| Segment \| What they share \| What they consume \|
20	\|---------\|-----------------\|-------------------\|
21	\| Open source maintainers \| Project updates, war stories \| Industry news, peer projects \|
22	\| Tech leads \| Team learnings, hiring \| Architecture, management \|
23	\| Indie hackers \| Building in public, MRR \| Growth tactics, tools \|
24	\| DevRel \| Content, events, community \| Trends, developer sentiment \|
25	\| Framework authors \| Updates, opinions \| Feedback, community vibes \|
26	\| Learning devs \| Questions, progress \| Tutorials, inspiration \|
27
28	### What Works on Dev Twitter
29
30	\| Content type \| Engagement level \| Notes \|
31	\|--------------\|------------------\|-------\|
32	\| Technical threads \| High \| Deep dives get saved/shared \|
33	\| Code screenshots \| High \| Visual, scannable \|
34	\| Hot takes \| High (risky) \| Can backfire spectacularly \|
35	\| Building in public \| High \| Journey > destination \|
36	\| Memes \| Medium-high \| Know your audience \|
37	\| Announcements \| Medium \| Better with context \|
38	\| Tutorial links \| Medium \| Need compelling hook \|
39	\| Retweets with comment \| Low-medium \| Add real value \|
40	\| Plain links \| Low \| Algorithm deprioritizes \|
41
42	### The Algorithm (As We Understand It)
43
44	\| Factor \| Impact \|
45	\|--------\|--------\|
46	\| Replies in first hour \| High — signals engagement \|
47	\| Time spent on post \| High — threads > tweets \|
48	\| Profile visits from post \| High — interesting content \|
49	\| Bookmarks \| High — "save for later" \|
50	\| Retweets \| Medium — distribution \|
51	\| Likes \| Medium — engagement signal \|
52	\| Link clicks \| Low — X wants you on platform \|
53	\| External links \| Negative — deprioritized \|
54
55	---
56
57	## Thread Structure
58
59	### Thread Anatomy
60
61	```
62	Tweet 1: HOOK
63	↓
64	Tweet 2: Context/Promise
65	↓
66	Tweets 3-8: The meat (examples, steps, insights)
67	↓
68	Tweet 9: Summary/Takeaway
69	↓
70	Tweet 10: CTA + Engagement ask
71	```
72
73	### Hook Patterns That Work
74
75	\| Pattern \| Example \|
76	\|---------\|---------\|
77	\| Contrarian \| "Hot take: You don't need Kubernetes for most apps" \|
78	\| Promise \| "How we reduced our AWS bill by 60% (thread)" \|
79	\| Story \| "Last week our API went down for 4 hours. Here's what happened:" \|
80	\| List tease \| "7 TypeScript tricks that changed how I code:" \|
81	\| Question \| "Why do most startups get database migrations wrong?" \|
82	\| Result \| "We went from 0 to 10K users in 30 days. Here's the playbook:" \|
83
84	### Thread Writing Best Practices
85
86	\| Element \| Guideline \|
87	\|---------\|-----------\|
88	\| Length \| 5-12 tweets optimal \|
89	\| First tweet \| Hook — no hashtags, no links \|
90	\| Each tweet \| One idea, complete thought \|
91	\| Numbering \| Use X/10 format or emoji bullets \|
92	\| Code \| Screenshots > text (more engaging) \|
93	\| Pacing \| Mix short punchy + longer explanatory \|
94	\| Last tweet \| CTA: follow, reply, bookmark \|
95
96	### Thread Template
97
98	```
99	🧵 [Hook: Compelling statement or question]
100
101	Here's what I learned [context]:
102
103	1/ [First key point]
104
105	[Supporting detail or example]
106
107	2/ [Second key point]
108
109	[Code screenshot or visual]
110
111	3/ [Third key point]
112
113	The counterintuitive part:
114
115	[Insight that surprises]
116
117	4/ [Fourth key point]
118
119	Common mistake to avoid:
120
121	[What not to do and why]
122
123	5/ [Summary]
124
125	TL;DR:
126	• Point 1
127	• Point 2
128	• Point 3
129
130	If this was helpful, give me a follow @handle for more [topic].
131
132	What's your experience with [topic]? 👇
133	```
134
135	---
136
137	## Code Screenshots
138
139	### Why Screenshots Beat Code Blocks
140
141	\| Screenshots \| Code blocks \|
142	\|-------------\|-------------\|
143	\| Syntax highlighting \| Plain text \|
144	\| Control over appearance \| Platform formatting \|
145	\| Can include context \| Just code \|
146	\| More visual stops \| Scroll past \|
147	\| Better engagement \| Lower engagement \|
148
149	### Code Screenshot Tools
150
151	\| Tool \| Best for \|
152	\|------\|----------\|
153	\| Carbon (carbon.now.sh) \| Beautiful, customizable \|
154	\| Ray.so \| Clean, modern \|
155	\| Snappify \| Annotations, animations \|
156	\| CodeSnap (VS Code) \| Quick from editor \|
157	\| Silicon (CLI) \| Automation \|
158
159	### Screenshot Best Practices
160
161	\| Do \| Don't \|
162	\|----\|-------\|
163	\| Use dark theme \| Light theme (harder to read) \|
164	\| Include file name \| Remove context \|
165	\| Highlight key lines \| Show walls of code \|
166	\| Keep width reasonable \| Make text tiny \|
167	\| Use consistent styling \| Different

People who liked this also viewed

6 picks

Type

x-devs

70installs6forks

View on GitHub

How to install x-devs?

jonathimer/devmarketing-skills/x-devs

$npx -y skills add jonathimer/devmarketing-skills --skill x-devs

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# X/Twitter for Developers
2
3	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.
4
5	---
6
7	## Before You Start
8
9	1. Read `.agents/developer-audience-context.md` if it exists
10	2. Audit your current X presence (bio, pinned, recent posts)
11	3. Understand: Developer Twitter rewards authenticity and technical depth
12
13	---
14
15	## Understanding Dev Twitter
16
17	### Who's on Dev Twitter
18
19	\| Segment \| What they share \| What they consume \|
20	\|---------\|-----------------\|-------------------\|
21	\| Open source maintainers \| Project updates, war stories \| Industry news, peer projects \|
22	\| Tech leads \| Team learnings, hiring \| Architecture, management \|
23	\| Indie hackers \| Building in public, MRR \| Growth tactics, tools \|
24	\| DevRel \| Content, events, community \| Trends, developer sentiment \|
25	\| Framework authors \| Updates, opinions \| Feedback, community vibes \|
26	\| Learning devs \| Questions, progress \| Tutorials, inspiration \|
27
28	### What Works on Dev Twitter
29
30	\| Content type \| Engagement level \| Notes \|
31	\|--------------\|------------------\|-------\|
32	\| Technical threads \| High \| Deep dives get saved/shared \|
33	\| Code screenshots \| High \| Visual, scannable \|
34	\| Hot takes \| High (risky) \| Can backfire spectacularly \|
35	\| Building in public \| High \| Journey > destination \|
36	\| Memes \| Medium-high \| Know your audience \|
37	\| Announcements \| Medium \| Better with context \|
38	\| Tutorial links \| Medium \| Need compelling hook \|
39	\| Retweets with comment \| Low-medium \| Add real value \|
40	\| Plain links \| Low \| Algorithm deprioritizes \|
41
42	### The Algorithm (As We Understand It)
43
44	\| Factor \| Impact \|
45	\|--------\|--------\|
46	\| Replies in first hour \| High — signals engagement \|
47	\| Time spent on post \| High — threads > tweets \|
48	\| Profile visits from post \| High — interesting content \|
49	\| Bookmarks \| High — "save for later" \|
50	\| Retweets \| Medium — distribution \|
51	\| Likes \| Medium — engagement signal \|
52	\| Link clicks \| Low — X wants you on platform \|
53	\| External links \| Negative — deprioritized \|
54
55	---
56
57	## Thread Structure
58
59	### Thread Anatomy
60
61	```
62	Tweet 1: HOOK
63	↓
64	Tweet 2: Context/Promise
65	↓
66	Tweets 3-8: The meat (examples, steps, insights)
67	↓
68	Tweet 9: Summary/Takeaway
69	↓
70	Tweet 10: CTA + Engagement ask
71	```
72
73	### Hook Patterns That Work
74
75	\| Pattern \| Example \|
76	\|---------\|---------\|
77	\| Contrarian \| "Hot take: You don't need Kubernetes for most apps" \|
78	\| Promise \| "How we reduced our AWS bill by 60% (thread)" \|
79	\| Story \| "Last week our API went down for 4 hours. Here's what happened:" \|
80	\| List tease \| "7 TypeScript tricks that changed how I code:" \|
81	\| Question \| "Why do most startups get database migrations wrong?" \|
82	\| Result \| "We went from 0 to 10K users in 30 days. Here's the playbook:" \|
83
84	### Thread Writing Best Practices
85
86	\| Element \| Guideline \|
87	\|---------\|-----------\|
88	\| Length \| 5-12 tweets optimal \|
89	\| First tweet \| Hook — no hashtags, no links \|
90	\| Each tweet \| One idea, complete thought \|
91	\| Numbering \| Use X/10 format or emoji bullets \|
92	\| Code \| Screenshots > text (more engaging) \|
93	\| Pacing \| Mix short punchy + longer explanatory \|
94	\| Last tweet \| CTA: follow, reply, bookmark \|
95
96	### Thread Template
97
98	```
99	🧵 [Hook: Compelling statement or question]
100
101	Here's what I learned [context]:
102
103	1/ [First key point]
104
105	[Supporting detail or example]
106
107	2/ [Second key point]
108
109	[Code screenshot or visual]
110
111	3/ [Third key point]
112
113	The counterintuitive part:
114
115	[Insight that surprises]
116
117	4/ [Fourth key point]
118
119	Common mistake to avoid:
120
121	[What not to do and why]
122
123	5/ [Summary]
124
125	TL;DR:
126	• Point 1
127	• Point 2
128	• Point 3
129
130	If this was helpful, give me a follow @handle for more [topic].
131
132	What's your experience with [topic]? 👇
133	```
134
135	---
136
137	## Code Screenshots
138
139	### Why Screenshots Beat Code Blocks
140
141	\| Screenshots \| Code blocks \|
142	\|-------------\|-------------\|
143	\| Syntax highlighting \| Plain text \|
144	\| Control over appearance \| Platform formatting \|
145	\| Can include context \| Just code \|
146	\| More visual stops \| Scroll past \|
147	\| Better engagement \| Lower engagement \|
148
149	### Code Screenshot Tools
150
151	\| Tool \| Best for \|
152	\|------\|----------\|
153	\| Carbon (carbon.now.sh) \| Beautiful, customizable \|
154	\| Ray.so \| Clean, modern \|
155	\| Snappify \| Annotations, animations \|
156	\| CodeSnap (VS Code) \| Quick from editor \|
157	\| Silicon (CLI) \| Automation \|
158
159	### Screenshot Best Practices
160
161	\| Do \| Don't \|
162	\|----\|-------\|
163	\| Use dark theme \| Light theme (harder to read) \|
164	\| Include file name \| Remove context \|
165	\| Highlight key lines \| Show walls of code \|
166	\| Keep width reasonable \| Make text tiny \|
167	\| Use consistent styling \| Different

People who liked this also viewed

6 picks

Type