developer-audience-context

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Developer Audience Context

开发者受众语境

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.

本技能可帮助您创建和维护

.agents/developer-audience-context.md

— 一份记录目标开发者所有信息的基础文档。所有其他开发者营销技能都会首先参考这份文档，因此您只需定义一次受众。

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

检查

.agents/developer-audience-context.md

是否存在：

若已存在：阅读文档并提供特定章节的更新服务
若不存在：创建目录和文件，然后逐步完成每个章节的内容

Two Ways to Build Context

两种构建语境的方式

Option 1: Auto-Draft from Codebase (Recommended)

选项1：从代码库自动生成草稿（推荐）

Analyze existing materials to draft an initial version:

README.md — Product description, features, getting started
Documentation —
```
/docs
```
, API reference, tutorials
Landing pages —
```
index.html
```
, marketing copy
package.json / pyproject.toml — Dependencies reveal ecosystem
GitHub Issues — Common questions, frustrations, use cases
Existing blog posts — Technical content, tutorials

After drafting, walk through each section to validate and fill gaps.

分析现有资料以生成初始版本：

README.md — 产品描述、功能特性、快速开始指南
文档 —
```
/docs
```
、API参考、教程
着陆页 —
```
index.html
```
、营销文案
package.json / pyproject.toml — 依赖项可揭示生态系统信息
GitHub Issues — 常见问题、痛点、使用场景
现有博客文章 — 技术内容、教程

生成草稿后，逐一检查每个章节以验证内容并填补空白。

Option 2: Start from Scratch

选项2：从零开始

Ask questions section-by-section. Don't advance until the current section is complete.

逐个章节提出问题。当前章节完成后再进入下一章节。

The 10 Sections to Capture

需要涵盖的10个章节

1. Product Overview

1. 产品概述

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

字段	需记录的内容
产品名称	官方名称及所有别名
一句话介绍	“我们帮助[开发者]在无需[Y]的情况下完成[X]”
产品类别	API、SDK、CLI、SaaS、开源库、基础设施
核心技术	支持的语言、框架、平台
定价模式	免费/开源、免费增值、按使用量付费、按席位付费

2. Developer Persona

2. 开发者角色

Not "developers" generically — get specific:

Field	What to capture
Primary role	Backend, frontend, full-stack, DevOps, data, ML, mobile
Seniority	Junior, mid, senior, staff, lead, architect
Company size	Solo, startup, scale-up, enterprise
Industry verticals	Fintech, healthtech, e-commerce, gaming, B2B SaaS
Tech stack	Languages, frameworks, cloud providers they use
Decision authority	Individual contributor, team lead, buyer, influencer

Ask: "Describe the developer who gets the most value from your product in one paragraph. What's their day-to-day like?"

不要笼统地定义“开发者” — 需具体化：

字段	需记录的内容
主要角色	后端、前端、全栈、DevOps、数据、ML、移动开发
资历	初级、中级、高级、资深、主管、架构师
公司规模	个人开发者、初创公司、成长期企业、大型企业
行业领域	金融科技、医疗科技、电子商务、游戏、B2B SaaS
技术栈	开发者使用的语言、框架、云服务商
决策权限	个人贡献者、团队负责人、采购者、影响者

提问示例：“用一段话描述从您的产品中获得最大价值的开发者。他们的日常工作是怎样的？”

3. Where They Hang Out

3. 他们的活跃渠道

Developers research before they buy. Know where:

Channel	Specifics to capture
Communities	Specific subreddits, Discord servers, Slack groups
Social	Twitter/X hashtags, LinkedIn groups
Content	Blogs they read, newsletters they subscribe to, podcasts
Events	Conferences, meetups, hackathons
Code	GitHub topics, Stack Overflow tags

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.

开发者在购买前会进行调研。了解他们活跃的渠道：

渠道	需记录的具体信息
社区	具体的Reddit子版块、Discord服务器、Slack群组
社交媒体	Twitter/X话题标签、LinkedIn群组
内容平台	他们阅读的博客、订阅的通讯、收听的播客
活动	会议、线下聚会、黑客松
代码平台	GitHub话题、Stack Overflow标签

专业提示：使用社交监听工具监控Hacker News、Reddit、Stack Overflow、GitHub和Twitter上的对话。了解您的问题领域中自然发生讨论的地方。

4. Problems & Pain Points

4. 问题与痛点

Capture the actual problems, not your solution's features:

Level	What to capture
Functional	"I can't do X" / "X takes too long" / "X is error-prone"
Emotional	Frustration, anxiety, embarrassment, fear
Situational	When does the pain occur? What triggers the search?

Ask: "What's the #1 frustration that brings developers to you?"

Research: Search Reddit, Hacker News, and Stack Overflow for complaints about your problem space. Capture verbatim quotes.

记录实际存在的问题，而非您的产品功能：

层级	需记录的内容
功能层面	“我无法完成X” / “X耗时太长” / “X容易出错”
情感层面	沮丧、焦虑、尴尬、担忧
场景层面	痛点何时出现？是什么触发了他们的搜索？

提问示例：“促使开发者选择您的产品的头号痛点是什么？”

调研方式：在Reddit、Hacker News和Stack Overflow上搜索与您的问题领域相关的抱怨。记录原文引用。

5. Current Alternatives

5. 当前替代方案

What are developers using today instead of you?

Alternative type	Examples
Direct competitors	Tools that solve the same problem
DIY / build it yourself	Custom scripts, internal tools
Indirect solutions	Workarounds, manual processes
Do nothing	Live with the pain

For each alternative, capture:

Why developers choose it
What's frustrating about it
What would make them switch

开发者目前在使用什么来替代您的产品？

替代方案类型	示例
直接竞争对手	解决相同问题的工具
自制/自行开发	自定义脚本、内部工具
间接解决方案	变通方法、手动流程
不采取任何行动	忍受痛点

针对每个替代方案，记录：

开发者选择它的原因
它的不足之处
什么会促使他们切换

6. Key Differentiators

6. 核心差异化优势

What makes you different — in developer terms:

Differentiator type	Example
Technical	"10x faster," "No dependencies," "Type-safe"
DX (Developer Experience)	"5-minute setup," "Great docs," "First-class CLI"
Ecosystem	"Works with X," "Built for Y framework"
Philosophy	"Open source," "Privacy-first," "Local-first"

Warning: Avoid marketing fluff. Developers see through "best-in-class" and "enterprise-grade." Use specific, provable claims.

用开发者能理解的语言描述您的独特之处：

差异化类型	示例
技术层面	“快10倍”、“无依赖”、“类型安全”
DX（开发者体验）	“5分钟完成设置”、“完善的文档”、“一流的CLI”
生态系统	“与X兼容”、“为Y框架打造”
理念层面	“开源”、“隐私优先”、“本地优先”

注意：避免营销空话。开发者能看穿“行业领先”和“企业级”这类表述。使用具体、可验证的声明。

7. Verbatim Developer Language

7. 开发者原话记录

Capture exact phrases developers use — not polished marketing copy:

Category	Examples
Describing the problem	"This is such a pain," "I wish I could just..."
Describing your product	How they explain it to others
Objections	"But what about...", "I'm worried that..."
Praise	Testimonials, tweets, GitHub comments

Sources: GitHub issues, Twitter mentions, Hacker News comments, support tickets, sales calls, community Slack/Discord.

记录开发者使用的准确表述 — 而非经过润色的营销文案：

类别	示例
描述问题	“这太麻烦了”、“我希望我能直接...”
描述您的产品	他们向他人解释产品的方式
异议	“但是关于...呢？”、“我担心...”
好评	推荐语、推文、GitHub评论

来源：GitHub Issues、Twitter提及、Hacker News评论、支持工单、销售电话、社区Slack/Discord。

8. Technical Trust Signals

8. 技术信任信号

What proof points matter to developers:

Signal type	Examples
Adoption	GitHub stars, npm downloads, Docker pulls
Quality	Test coverage, security audits, uptime SLA
Community	Contributors, Discord members, forum activity
Credibility	Backed by X, used by Y, created by Z
Transparency	Open source, public roadmap, changelog

哪些证明点对开发者重要：

信号类型	示例
采用度	GitHub星标、npm下载量、Docker拉取量
质量	测试覆盖率、安全审计、正常运行时间SLA
社区活跃度	贡献者数量、Discord成员数、论坛活动
可信度	由X支持、被Y使用、由Z创建
透明度	开源、公开路线图、更新日志

9. Conversion Actions

9. 转化行动

What does success look like at each stage?

Stage	Primary action	Secondary actions
Awareness	Star repo, follow on Twitter	Read blog post, share content
Consideration	Clone repo, read docs	Watch demo, join Discord
Trial	Sign up, install SDK	Complete quickstart, make first API call
Activation	Reach "Hello World" moment	Integrate into real project
Conversion	Upgrade to paid	Add team members, expand usage

每个阶段的成功标志是什么？

阶段	主要行动	次要行动
认知阶段	给仓库点星标、关注Twitter	阅读博客文章、分享内容
考虑阶段	克隆仓库、阅读文档	观看演示、加入Discord
试用阶段	注册、安装SDK	完成快速开始指南、首次调用API
激活阶段	达成“Hello World”时刻	集成到实际项目中
转化阶段	升级到付费版	添加团队成员、扩大使用范围

10. Voice & Tone

10. 语气与风格

How should you sound when talking to these developers?

Dimension	Spectrum
Formality	Casual ← → Professional
Technicality	Accessible ← → Deep technical
Personality	Neutral ← → Opinionated
Humor	Serious ← → Playful

Examples:

Stripe → Professional, precise, clean
Vercel → Modern, confident, developer-first
Supabase → Friendly, accessible, community-driven
Tailwind → Opinionated, direct, practical

与这些开发者沟通时，您应该采用怎样的语气？

维度	范围
正式程度	随意 ← → 专业
技术深度	通俗易懂 ← → 深入技术
个性	中立 ← → 有主见
幽默感	严肃 ← → 活泼

示例：

Stripe → 专业、精准、简洁
Vercel → 现代、自信、开发者优先
Supabase → 友好、通俗易懂、社区驱动
Tailwind → 有主见、直接、实用

Output Format

输出格式

Save to

.agents/developer-audience-context.md

with this structure:

markdown

undefined

将内容保存到

.agents/developer-audience-context.md

，格式如下：

markdown

undefined

Developer Audience Context

Last updated: [DATE]

Product Overview

[Section content]

Developer Persona

[Section content]

Where They Hang Out

[Section content]

Problems & Pain Points

[Section content]

Current Alternatives

[Section content]

Key Differentiators

[Section content]

Verbatim Developer Language

[Section content]

Technical Trust Signals

[Section content]

Conversion Actions

[Section content]

Voice & Tone

[Section content]

---

[Section content]

---

Maintenance

维护

Update this document when:

You learn something new from user research
You find great verbatim quotes
Your positioning or differentiation changes
You expand to new developer segments

在以下情况时更新此文档：

从用户研究中获得新的见解
发现优质的开发者原话
您的定位或差异化优势发生变化
拓展到新的开发者细分群体

Tools

工具

Tool	Use case
Octolens	Monitor developer conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter. Essential for capturing verbatim language, finding pain points, and understanding where your developers hang out.
GitHub Search	Find how developers describe problems in issues
Twitter Advanced Search	Find discussions about your space
Google Alerts	Track mentions of competitors and problem keywords

工具	使用场景
Octolens	监控GitHub、Hacker News、Reddit、Stack Overflow、Twitter上的开发者对话。对于记录开发者原话、发现痛点以及了解开发者的活跃渠道至关重要。
GitHub Search	查找开发者在Issues中描述问题的方式
Twitter Advanced Search	查找与您的领域相关的讨论
Google Alerts	追踪竞争对手和问题关键词的提及

developer-audience-context

Original

Translation

Developer Audience Context

开发者受众语境

Before You Start

开始之前

Two Ways to Build Context

两种构建语境的方式

Option 1: Auto-Draft from Codebase (Recommended)

选项1：从代码库自动生成草稿（推荐）

Option 2: Start from Scratch

选项2：从零开始

The 10 Sections to Capture

需要涵盖的10个章节

1. Product Overview

1. 产品概述

2. Developer Persona

2. 开发者角色

3. Where They Hang Out

3. 他们的活跃渠道

4. Problems & Pain Points

4. 问题与痛点

5. Current Alternatives

5. 当前替代方案

6. Key Differentiators

6. 核心差异化优势

7. Verbatim Developer Language

7. 开发者原话记录

8. Technical Trust Signals

8. 技术信任信号

9. Conversion Actions

9. 转化行动

10. Voice & Tone

10. 语气与风格

Output Format

输出格式

Developer Audience Context

Developer Audience Context

Product Overview

Product Overview

Developer Persona

Developer Persona

Where They Hang Out

Where They Hang Out

Problems & Pain Points

Problems & Pain Points

Current Alternatives

Current Alternatives

Key Differentiators

Key Differentiators

Verbatim Developer Language

Verbatim Developer Language

Technical Trust Signals

Technical Trust Signals

Conversion Actions

Conversion Actions

Voice & Tone

Voice & Tone

Maintenance

维护

Tools

工具

Related Skills

相关技能