developer-audience-context
Foundation skill — All other skills reference this first.
What It Does
Creates and maintains .agents/developer-audience-context.md — a single document capturing everything about your target developers. Define your audience once, and every other skill automatically has context.
When to Use
- Starting any developer marketing project
- Before running other skills (automatically referenced)
- When you say "developer persona," "target developers," "ICP," or "who are our developers"
Quick Start
/developer-audience-context
Create our developer audience context. We're building an open source
API testing library for Node.js/TypeScript developers.
The skill will either:
- Auto-draft from your codebase (README, docs, landing pages)
- Walk through 10 sections conversationally
Files
| File | Description |
|---|---|
SKILL.md |
Full skill instructions |
references/template.md |
Blank template to fill out |
references/example-apitest.md |
Filled example for a fictional dev tool |
The 10 Sections
- Product Overview — Name, one-liner, category, tech, pricing
- Developer Persona — Role, seniority, company size, tech stack
- Where They Hang Out — Reddit, Discord, Twitter, podcasts, conferences
- Problems & Pain Points — Functional, emotional, trigger moments
- Current Alternatives — Competitors, DIY, do nothing
- Key Differentiators — Technical, DX, ecosystem, philosophy
- Verbatim Developer Language — Exact quotes, not polished copy
- Technical Trust Signals — GitHub stars, downloads, notable users
- Conversion Actions — Awareness → Activation → Conversion
- Voice & Tone — How you sound when talking to developers
Tools
- Octolens — Monitor developer conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter to capture verbatim language and find where your developers hang out.
Related Skills
Skills that reference this context:
devrel-contenthacker-news-strategydeveloper-onboardingdeveloper-seocompetitor-tracking