From customer-insight
Use when building a persona, customer profile, or journey-prep brief from a product, audience clue, or usage context, especially for persona、人物誌、顧客輪廓、使用者輪廓、目標客群、5W1H、接觸點盤點、顧客旅程前置分析、或需要簡報化的顧客研究摘要。
How this skill is triggered — by the user, by Claude, or both
Slash command
/customer-insight:customer-persona-framerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create persona-first outputs in Traditional Chinese.
Create persona-first outputs in Traditional Chinese.
Stop at a reusable persona when the task is only about customer definition, or expand into a journey-framing brief that can be handed to customer-journey-mapper.
Use this skill first when someone wants customer-journey-mapper output but no completed persona exists yet.
Default output is structured Markdown.
If the user explicitly asks for 簡報、投影片、教學圖、slides、deck, keep the same information architecture but rewrite each section as presentation-ready bullets.
Use mode: auto | persona-only | journey-framing.
If the user wants customer-journey-mapper output but no persona is available yet, choose journey-framing first so the result can be handed off downstream.
auto rules:
persona、人物誌、顧客輪廓、使用者輪廓、目標客群分析、輪廓建模, choose persona-only.5W1H、顧客旅程、接觸點、情緒、階段、旅程地圖前置, choose journey-framing.只要 persona、先不要旅程, lock to persona-only even if journey words also appear.Need at least one of:
產品或服務目標客群初步 persona 線索Optional:
使用情境品牌/產業背景既有接觸點輸出用途modeDefault assumptions:
If the available input is enough to define one coherent persona, generate directly.
If critical information is missing and the user did not ask for speed:
If the user asks for a quick draft, for example:
先做一版快速版可先假設直接幫我整理Then:
3-5 assumptions firstAlways answer in Traditional Chinese.
persona-onlyOutput sections in this order:
Persona 卡核心特徵與限制需求/痛點/期望persona_blockRecommended Persona 卡 fields:
角色代稱年齡層/人生階段背景與生活型態主要目標決策線索使用情境persona_block must be compact and reusable.
Use this shape:
### persona_block
- 顧客輪廓: ...
- 角色背景: ...
- 核心需求: ...
- 主要痛點: ...
- 使用情境: ...
- 決策線索: ...
Do not add handoff_to_customer_journey_mapper in persona-only.
journey-framingOutput sections in this order:
Persona 卡5W1H 摘要旅程五元素摘要階段定義handoff_to_customer_journey_mapper5W1H 摘要 must cover:
WhoWhatWhenWhereWhyHow旅程五元素摘要 must cover:
personastagestouchpointsemotionsmetricsDefault stage names must align with customer-journey-mapper:
認知考慮/研究決策/購買使用關係建立metrics stay in this summary only.
Do not copy metrics into the mapper handoff block.
Use this handoff shape:
### handoff_to_customer_journey_mapper
- 顧客輪廓: ...
- 產品或服務: ...
- 品牌/產業背景: ...
- 目標市場: ...
- 目前接觸點: ...
- 輸出用途: ...
When information is unknown:
persona-only or journey-framing.journey-framing, convert the persona into 5W1H, five journey elements, and stage definitions.journey-framing, produce handoff_to_customer_journey_mapper as the final section.需求, 痛點, and 期望; do not collapse them into one vague list接觸點 concrete, such as search, LINE, store visit, DM, app push, or friend referral情緒 a real state or transition, not a marketing adjectivemetrics observable, such as click-through, consultation rate, trial start, repeat use, or support resolutionUse $customer-persona-framer to create a Traditional Chinese persona profile from 產品或服務 and 目標客群.Use $customer-persona-framer to create a Traditional Chinese journey-framing brief with persona, 5W1H, and a handoff block for customer-journey-mapper.npx claudepluginhub timlai666/skills --plugin customer-insightGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.