菜单
Use when you need to define target buyers - builds detailed personas with pain points, goals, channels, and objections grounded in market research
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | customer-personas |
| description | Use when you need to define target buyers - builds detailed personas with pain points, goals, channels, and objections grounded in market research |
Build detailed buyer personas grounded in market research. Produces persona profiles that downstream skills (positioning-strategy, campaign-builder) reference for targeted messaging.
Announce at start: "I'm using the customer-personas skill to build buyer profiles."
Step 1: Context gathering
docs/marketing/market-research.md if it exists (use findings as input)Step 2: Scope the personas
Step 3: Present personas
Step 4: Write output
docs/marketing/customer-personas.mdStep 5: Handoff
globalcoder-marketing:brand-identity or globalcoder-marketing:positioning-strategyUse when executing an implementation plan with four or more independent tasks touching different files, via the experimental agent-teams flag — parallel implementer teammates plus continuous async reviewers. Higher token cost; requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Use when starting creative work — adding features, building components, adding functionality, modifying existing behavior, or any time the user describes a new idea or capability they want to build.
Use when adding, modifying, or removing database tables, columns, indexes, views, functions, or RLS policies — any schema change targeting a shared or production database
Use when facing two or more independent investigations or research tasks in the current session — debugging multiple unrelated failures, exploring different solution approaches, or running parallel reads. Not for executing implementation plans (use subagent-driven-development, agent-team-development, or tmux-parallel-development for those).
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup