/developer-audience-context

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:

1. Auto-draft from your codebase (README, docs, landing pages)
2. Walk through 10 sections conversationally

Files

The 10 Sections

1. Product Overview — Name, one-liner, category, tech, pricing
2. Developer Persona — Role, seniority, company size, tech stack
3. Where They Hang Out — Reddit, Discord, Twitter, podcasts, conferences
4. Problems & Pain Points — Functional, emotional, trigger moments
5. Current Alternatives — Competitors, DIY, do nothing
6. Key Differentiators — Technical, DX, ecosystem, philosophy
7. Verbatim Developer Language — Exact quotes, not polished copy
8. Technical Trust Signals — GitHub stars, downloads, notable users
9. Conversion Actions — Awareness → Activation → Conversion
10. 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-content
• hacker-news-strategy
• developer-onboarding
• developer-seo
• competitor-tracking