Pages: Customer Stories
Guides customer story and case study page content, structure, and conversion.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, proof points, and customer language.
Identify:
- 1. Story format: Full case study, quote snippet, video
- Industries/use cases: Who to showcase
- Metrics: What results to highlight
Best Practices
Structure (Challenge -> Solution -> Results)
| Section | Content |
|---|
| Headline | Benefit-driven; lead with outcome |
| Challenge |
Client's problem, pain points |
|
Solution | How your product helped |
|
Results | Quantifiable metrics, before/after |
|
Quote | Direct testimonial from client |
|
CTA | Next step (demo, contact, read more) |
Content Principles
- - Lead with results: Outcomes first, not background
- Specific metrics: "Increased revenue 40%" not "great results"
- Quotes: Direct, attributed, credible
- Scannable: Consistent template; easy to skim
- Concise: Enough value without losing interest
Visual Elements
- - Logos: Client branding (with permission)
- Charts/graphs: Before-after, metrics
- Video: Testimonials, interviews
- Expandable sections: For deeper detail
Why It Matters
- - 54% of buyers review case studies before purchasing
- 73% of successful content marketers use them
- Builds credibility, justifies pricing, shortens sales cycles
Storytelling
- - Problem = beginning
- Solution = climax
- Results = resolution
- Hard facts: Statistics for impact
Output Format
- - Template structure
- Story outline (challenge, solution, results)
- Metrics to capture
- SEO metadata and schema (if indexing)
- Internal linking to product/pricing
Related Skills
- - landing-page-generator: Case studies and testimonials for LP social proof (step 2)
- url-slug-generator: URL slug for case study pages (e.g. /customers/case-slug); 3-5 words
- about-page-generator: Social proof complements About
- pricing-page-generator: Case studies support pricing justification
- homepage-generator: Customer stories on homepage
- schema-markup: CaseStudy schema
页面：客户案例
指导客户故事和案例研究页面的内容、结构和转化。
调用时：首次使用时，如有帮助，先用1-2句话说明本技能涵盖的内容及其重要性，然后提供主要输出。后续使用或用户要求跳过时，直接进入主要输出。
初步评估
首先检查项目上下文： 如果存在 .claude/project-context.md 或 .cursor/project-context.md，读取其中的产品、验证点和客户语言。
识别：
- 1. 故事形式：完整案例研究、引用片段、视频
- 行业/用例：展示对象
- 指标：突出哪些成果
最佳实践
结构（挑战 -> 解决方案 -> 成果）
客户的问题、痛点 |
|
解决方案 | 产品如何提供帮助 |
|
成果 | 可量化指标、前后对比 |
|
客户引述 | 客户直接推荐语 |
|
行动号召 | 下一步（演示、联系、了解更多） |
内容原则
- - 以成果为先：先讲结果，而非背景
- 具体指标：收入增长40%而非效果显著
- 引述：直接、署名、可信
- 易于浏览：一致的模板；便于快速阅读
- 简洁：提供足够价值而不失趣味
视觉元素
- - 标识：客户品牌标识（经许可）
- 图表：前后对比、指标
- 视频：推荐语、访谈
- 可展开部分：用于更详细的内容
为何重要
- - 54%的买家在购买前会查看案例研究
- 73%的成功内容营销人员使用案例研究
- 建立可信度、证明定价合理性、缩短销售周期
故事叙述
- - 问题 = 开端
- 解决方案 = 高潮
- 成果 = 结局
- 硬事实：有影响力的统计数据
输出格式
- - 模板结构
- 故事大纲（挑战、解决方案、成果）
- 需捕获的指标
- SEO元数据和结构化数据（如需索引）
- 内部链接到产品/定价页面
相关技能
- - landing-page-generator：着陆页社交证明的案例研究和推荐（步骤2）
- url-slug-generator：案例研究页面的URL别名（例如 /customers/case-slug）；3-5个词
- about-page-generator：社交证明补充关于页面
- pricing-page-generator：案例研究支持定价合理性
- homepage-generator：首页上的客户故事
- schema-markup：案例研究结构化数据
