developer-audience-context

Name: developer-audience-context
Author: jonathimer

76installs6forks

How to install developer-audience-context?

jonathimer/devmarketing-skills/developer-audience-context

$npx -y skills add jonathimer/devmarketing-skills --skill developer-audience-context

Installs into the current project.

Summary

When the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded. Trigger phrases include "developer persona," "target developers," "who are our developers," "developer

Files · 1

View on GitHub

SKILL.md

1	# Developer Audience Context
2
3	This skill helps you create and maintain `.agents/developer-audience-context.md` — a foundational document that captures everything about your target developers. All other developer marketing skills reference this document first, so you only define your audience once.
4
5	---
6
7	## Before You Start
8
9	Check if `.agents/developer-audience-context.md` exists:
10
11	- If it exists: Read it and offer to update specific sections
12	- If it doesn't exist: Create the directory and file, then walk through each section
13
14	---
15
16	## Two Ways to Build Context
17
18	### Option 1: Auto-Draft from Codebase (Recommended)
19
20	Analyze existing materials to draft an initial version:
21
22	1. README.md — Product description, features, getting started
23	2. Documentation — `/docs`, API reference, tutorials
24	3. Landing pages — `index.html`, marketing copy
25	4. package.json / pyproject.toml — Dependencies reveal ecosystem
26	5. GitHub Issues — Common questions, frustrations, use cases
27	6. Existing blog posts — Technical content, tutorials
28
29	After drafting, walk through each section to validate and fill gaps.
30
31	### Option 2: Start from Scratch
32
33	Ask questions section-by-section. Don't advance until the current section is complete.
34
35	---
36
37	## The 10 Sections to Capture
38
39	### 1. Product Overview
40
41	\| Field \| What to capture \|
42	\|-------\|-----------------\|
43	\| Product name \| Official name and any aliases \|
44	\| One-liner \| "We help [developers] do [X] without [Y]" \|
45	\| Category \| API, SDK, CLI, SaaS, open source library, infrastructure \|
46	\| Core technology \| Languages, frameworks, platforms supported \|
47	\| Pricing model \| Free/open source, freemium, usage-based, seat-based \|
48
49	### 2. Developer Persona
50
51	Not "developers" generically — get specific:
52
53	\| Field \| What to capture \|
54	\|-------\|-----------------\|
55	\| Primary role \| Backend, frontend, full-stack, DevOps, data, ML, mobile \|
56	\| Seniority \| Junior, mid, senior, staff, lead, architect \|
57	\| Company size \| Solo, startup, scale-up, enterprise \|
58	\| Industry verticals \| Fintech, healthtech, e-commerce, gaming, B2B SaaS \|
59	\| Tech stack \| Languages, frameworks, cloud providers they use \|
60	\| Decision authority \| Individual contributor, team lead, buyer, influencer \|
61
62	Ask: "Describe the developer who gets the most value from your product in one paragraph. What's their day-to-day like?"
63
64	### 3. Where They Hang Out
65
66	Developers research before they buy. Know where:
67
68	\| Channel \| Specifics to capture \|
69	\|---------\|---------------------\|
70	\| Communities \| Specific subreddits, Discord servers, Slack groups \|
71	\| Social \| Twitter/X hashtags, LinkedIn groups \|
72	\| Content \| Blogs they read, newsletters they subscribe to, podcasts \|
73	\| Events \| Conferences, meetups, hackathons \|
74	\| Code \| GitHub topics, Stack Overflow tags \|
75
76	Pro tip: Use social listening tools to monitor conversations across Hacker News, Reddit, Stack Overflow, GitHub, and Twitter. See where discussions about your problem space happen organically.
77
78	### 4. Problems & Pain Points
79
80	Capture the actual problems, not your solution's features:
81
82	\| Level \| What to capture \|
83	\|-------\|-----------------\|
84	\| Functional \| "I can't do X" / "X takes too long" / "X is error-prone" \|
85	\| Emotional \| Frustration, anxiety, embarrassment, fear \|
86	\| Situational \| When does the pain occur? What triggers the search? \|
87
88	Ask: "What's the #1 frustration that brings developers to you?"
89
90	Research: Search Reddit, Hacker News, and Stack Overflow for complaints about your problem space. Capture verbatim quotes.
91
92	### 5. Current Alternatives
93
94	What are developers using today instead of you?
95
96	\| Alternative type \| Examples \|
97	\|-----------------\|----------\|
98	\| Direct competitors \| Tools that solve the same problem \|
99	\| DIY / build it yourself \| Custom scripts, internal tools \|
100	\| Indirect solutions \| Workarounds, manual processes \|
101	\| Do nothing \| Live with the pain \|
102
103	For each alternative, capture:
104	- Why developers choose it
105	- What's frustrating about it
106	- What would make them switch
107
108	### 6. Key Differentiators
109
110	What makes you different — in developer terms:
111
112	\| Differentiator type \| Example \|
113	\|--------------------\|---------\|
114	\| Technical \| "10x faster," "No dependencies," "Type-safe" \|
115	\| DX (Developer Experience) \| "5-minute setup," "Great docs," "First-class CLI" \|
116	\| Ecosystem \| "Works with X," "Built for Y framework" \|
117	\| Philosophy \| "Open source," "Privacy-first," "Local-first" \|
118
119	Warning: Avoid marketing fluff. Developers see through "best-in-class" and "enterprise-grade." Use specific, provable claims.
120
121	### 7. Verbatim Developer Language
122
123	Capture exact phrases develope

People who liked this also viewed

6 picks

Type

developer-audience-context

76installs6forks

View on GitHub

How to install developer-audience-context?

jonathimer/devmarketing-skills/developer-audience-context

$npx -y skills add jonathimer/devmarketing-skills --skill developer-audience-context

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Developer Audience Context
2
3	This skill helps you create and maintain `.agents/developer-audience-context.md` — a foundational document that captures everything about your target developers. All other developer marketing skills reference this document first, so you only define your audience once.
4
5	---
6
7	## Before You Start
8
9	Check if `.agents/developer-audience-context.md` exists:
10
11	- If it exists: Read it and offer to update specific sections
12	- If it doesn't exist: Create the directory and file, then walk through each section
13
14	---
15
16	## Two Ways to Build Context
17
18	### Option 1: Auto-Draft from Codebase (Recommended)
19
20	Analyze existing materials to draft an initial version:
21
22	1. README.md — Product description, features, getting started
23	2. Documentation — `/docs`, API reference, tutorials
24	3. Landing pages — `index.html`, marketing copy
25	4. package.json / pyproject.toml — Dependencies reveal ecosystem
26	5. GitHub Issues — Common questions, frustrations, use cases
27	6. Existing blog posts — Technical content, tutorials
28
29	After drafting, walk through each section to validate and fill gaps.
30
31	### Option 2: Start from Scratch
32
33	Ask questions section-by-section. Don't advance until the current section is complete.
34
35	---
36
37	## The 10 Sections to Capture
38
39	### 1. Product Overview
40
41	\| Field \| What to capture \|
42	\|-------\|-----------------\|
43	\| Product name \| Official name and any aliases \|
44	\| One-liner \| "We help [developers] do [X] without [Y]" \|
45	\| Category \| API, SDK, CLI, SaaS, open source library, infrastructure \|
46	\| Core technology \| Languages, frameworks, platforms supported \|
47	\| Pricing model \| Free/open source, freemium, usage-based, seat-based \|
48
49	### 2. Developer Persona
50
51	Not "developers" generically — get specific:
52
53	\| Field \| What to capture \|
54	\|-------\|-----------------\|
55	\| Primary role \| Backend, frontend, full-stack, DevOps, data, ML, mobile \|
56	\| Seniority \| Junior, mid, senior, staff, lead, architect \|
57	\| Company size \| Solo, startup, scale-up, enterprise \|
58	\| Industry verticals \| Fintech, healthtech, e-commerce, gaming, B2B SaaS \|
59	\| Tech stack \| Languages, frameworks, cloud providers they use \|
60	\| Decision authority \| Individual contributor, team lead, buyer, influencer \|
61
62	Ask: "Describe the developer who gets the most value from your product in one paragraph. What's their day-to-day like?"
63
64	### 3. Where They Hang Out
65
66	Developers research before they buy. Know where:
67
68	\| Channel \| Specifics to capture \|
69	\|---------\|---------------------\|
70	\| Communities \| Specific subreddits, Discord servers, Slack groups \|
71	\| Social \| Twitter/X hashtags, LinkedIn groups \|
72	\| Content \| Blogs they read, newsletters they subscribe to, podcasts \|
73	\| Events \| Conferences, meetups, hackathons \|
74	\| Code \| GitHub topics, Stack Overflow tags \|
75
76	Pro tip: Use social listening tools to monitor conversations across Hacker News, Reddit, Stack Overflow, GitHub, and Twitter. See where discussions about your problem space happen organically.
77
78	### 4. Problems & Pain Points
79
80	Capture the actual problems, not your solution's features:
81
82	\| Level \| What to capture \|
83	\|-------\|-----------------\|
84	\| Functional \| "I can't do X" / "X takes too long" / "X is error-prone" \|
85	\| Emotional \| Frustration, anxiety, embarrassment, fear \|
86	\| Situational \| When does the pain occur? What triggers the search? \|
87
88	Ask: "What's the #1 frustration that brings developers to you?"
89
90	Research: Search Reddit, Hacker News, and Stack Overflow for complaints about your problem space. Capture verbatim quotes.
91
92	### 5. Current Alternatives
93
94	What are developers using today instead of you?
95
96	\| Alternative type \| Examples \|
97	\|-----------------\|----------\|
98	\| Direct competitors \| Tools that solve the same problem \|
99	\| DIY / build it yourself \| Custom scripts, internal tools \|
100	\| Indirect solutions \| Workarounds, manual processes \|
101	\| Do nothing \| Live with the pain \|
102
103	For each alternative, capture:
104	- Why developers choose it
105	- What's frustrating about it
106	- What would make them switch
107
108	### 6. Key Differentiators
109
110	What makes you different — in developer terms:
111
112	\| Differentiator type \| Example \|
113	\|--------------------\|---------\|
114	\| Technical \| "10x faster," "No dependencies," "Type-safe" \|
115	\| DX (Developer Experience) \| "5-minute setup," "Great docs," "First-class CLI" \|
116	\| Ecosystem \| "Works with X," "Built for Y framework" \|
117	\| Philosophy \| "Open source," "Privacy-first," "Local-first" \|
118
119	Warning: Avoid marketing fluff. Developers see through "best-in-class" and "enterprise-grade." Use specific, provable claims.
120
121	### 7. Verbatim Developer Language
122
123	Capture exact phrases develope

People who liked this also viewed

6 picks

Type