Agent skill · marketing growth · sickn33
developer-audience-context
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.
Why this skill is useful
Provides a structured approach to defining developer personas and audience context that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Developer Audience Context When to Use Use this skill when you need 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... 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. --- Before You Start Check if .agents/developer-audience-context.md exists: If it exists: Read it and offer to update specific sections If it doesn't exist: Create the directory and file, then walk through each section --- Two Ways to Build Context Option 1: Auto-Draft from Codebase (Recommended) Analyze existing materials to draft an initial version: 1. README.md — Product description, features, getting started 2. Documentation — /docs, API reference, tutorials 3. Landing pages — index.html, marketing copy 4. package.json / pyproject.toml — Dependencies reveal ecosystem 5. GitHub Issues — Common questions, frustrations, use cases 6. Existing blog posts — Technical content, tutorials After drafting, walk through each section to validate and fill gaps. Option 2: Start from Scratch Ask questions section-by-section. Don't advance until the current section is complete. --- The 10 Sections to Capture 1. Product Overview Field What to capture ------- ----------------- Product name Official name and any aliases One-liner "We help [developers] do [X] without [Y]" Category API, SDK, CLI, SaaS, open source library, infrastructure Core technology Languages, frameworks, platforms supported Pricing model Free/open source, freemium, usage-based, seat-based 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/developer-audience-context