mcpField
P
portfolio-case-study-writer

portfolio-case-study-writer

github.com/paramchoudhary文档处理2.9k9.9k 次安装19 周前更新
代码仓库

关于 portfolio-case-study-writer

portfolio-case-study-writer 是帮助求职者把简历要点扩展为作品集案例的写作技能,适用于 PM、UX、设计及其他创意岗位。它提供从问题、过程到结果与复盘的结构,并指导如何按受众调整内容和呈现方式。

主要功能

  1. 01将简历要点扩展为案例
  2. 02按问题、过程和结果组织内容
  3. 03结合技术细节与业务背景
  4. 04按受众调整案例深度
  5. 05提供作品集网站排版建议

适用场景

  1. 01把项目经历写成作品集案例
  2. 02为 UX 或 PM 求职展示工作过程
  3. 03将技术项目整理为案例叙述

安装

复制下面的命令,在终端中运行。

$npx skills add https://github.com/paramchoudhary/resumeskills --skill portfolio-case-study-writer

安装后在 Claude Code 中输入/portfolio-case-study-writer确认已加载。

详细介绍

作品集案例研究撰写

何时使用此技能

在用户遇到以下情况时使用此技能:

  • 想要创建作品集案例研究
  • 需要将简历要点扩展为详细的项目说明
  • 正在构建作品集网站
  • 想要深入展示项目成果
  • 提到“案例研究”“作品集”“项目说明”“工作样例”或“作品集项目”

核心能力

  • 将简历要点转化为详细的案例研究
  • 以最能体现价值的方式组织案例研究
  • 创作引人入胜的项目叙述
  • 平衡技术细节与业务背景
  • 为作品集网站排版
  • 根据受众调整内容深度

案例研究的目的

案例研究为何重要:

  • 简历展示你做了什么;案例研究展示你如何做以及为何这样做
  • 展示思考过程,而不仅仅是结果
  • 更充分地展示技能
  • 让你在其他候选人中脱颖而出
  • 许多产品经理、用户体验和创意类岗位都要求提供案例研究

案例研究结构

标准结构
1. Overview (Project summary)
2. Problem (What needed to be solved)
3. Process (How you approached it)
4. Solution (What you created/delivered)
5. Results (The impact)
6. Learnings (What you'd do differently)
阅读时长
  • 快速浏览: 3-5 分钟(作品集必备)
  • 深入阅读: 10-15 分钟(适合感兴趣的读者)

分部分指南

1. 概览部分

目的: 吸引读者,提供背景

包括:

  • 项目名称和公司
  • 你的角色
  • 时间线
  • 团队规模
  • 一句话概述项目影响

示例:

# Redesigning the Checkout Flow

**Company:** E-Commerce Inc.
**Role:** Lead Product Designer
**Timeline:** 6 weeks
**Team:** 2 designers, 3 engineers, 1 PM

**Summary:** Reduced cart abandonment by 35% through a streamlined 3-step checkout process, generating $2M in recovered revenue.
2. 问题部分

目的: 说明这项工作为何重要

包括:

  • 业务背景
  • 用户痛点
  • 关键指标或目标
  • 限制条件

示例:

## The Problem

E-Commerce Inc. was experiencing 68% cart abandonment—significantly higher than the industry average of 55%. Exit surveys and user research revealed several issues:

- **Too many steps:** Our checkout had 7 screens
- **Forced account creation:** Users had to register before purchasing
- **Hidden costs:** Shipping wasn't shown until step 5
- **Mobile friction:** Forms weren't optimized for mobile

**Goal:** Reduce cart abandonment to below 50% within 3 months.

**Constraints:**
- No changes to existing payment integrations
- Had to maintain PCI compliance
- 6-week timeline before holiday season
3. 过程部分

目的: 展示你的思路和方法

包括:

  • 开展的研究
  • 参与的利益相关者
  • 提出的假设
  • 考虑过的方案
  • 做出的决策(以及原因)

示例:

## Process

### Research
I started by understanding the problem deeply:
- Analyzed Mixpanel funnel data for drop-off points
- Conducted 10 user interviews with recent abandoners
- Reviewed heatmaps and session recordings
- Benchmarked against 5 competitor checkout flows

**Key Insight:** 73% of drop-offs occurred at the account creation screen. Users wanted to purchase, not commit to a relationship.

### Ideation
I explored several approaches:
1. Guest checkout only (simplest)
2. Social login options (lower friction)
3. Progressive profiling (collect info over time)
4. One-page checkout (Amazon-style)

After weighing feasibility, timeline, and impact, we chose a hybrid approach...

### Decisions Made
- **Guest checkout first:** Made registration optional and post-purchase
- **Transparent pricing:** Showed shipping on the first screen
- **Mobile-first design:** Designed for mobile, then adapted for desktop
- **Progress indicator:** Added clear "Step 1 of 3" indicator
4. 解决方案部分

目的: 展示你实际创建的内容

包括:

  • 视觉材料(模型图、屏幕截图、示意图)
  • 关键功能/变更
  • 技术实现(如相关)
  • 如何解决这些问题

示例:

## Solution

### The New Checkout Flow

**Before:** 7 screens with mandatory registration
**After:** 3 screens with optional guest checkout

[IMAGE: Before/After comparison]

### Key Changes

**1. Transparent Pricing Widget**
[IMAGE: Pricing widget mockup]
Showed order total, shipping, and taxes from the start. No surprises.

**2. Guest Checkout Option**
[IMAGE: Guest checkout screen]
Made account creation optional with clear value proposition for why to register.

**3. Smart Form Design**
[IMAGE: Form design]
- Single-column layout on mobile
- Auto-format for phone/card numbers
- Address autocomplete integration
- Clear error messaging

**4. Trust Signals**
Added security badges, money-back guarantee, and customer service contact throughout the flow.
5. 结果部分

目的: 用数据证明影响

包括:

  • 定量结果(注明时间范围)
  • 与目标的对比
  • 受到影响的次要指标
  • 业务影响

示例:

## Results

### Primary Metrics (90 days post-launch)

| Metric | Before | After | Change |
|--------|--------|-------|--------|
| Cart Abandonment | 68% | 44% | -35% |
| Checkout Completion | 32% | 56% | +75% |
| Mobile Conversion | 18% | 41% | +128% |
| Revenue per Visitor | $2.40 | $3.85 | +60% |

### Business Impact
- **$2M additional revenue** in first quarter
- **15% increase in mobile orders**
- **Customer support tickets about checkout** dropped by 45%

### Secondary Effects
- Account creation actually increased 20% (post-purchase)
- Average order value stayed stable
- Return customer rate improved
6. 经验总结部分

目的: 展示成长型思维和自我认知

包括:

  • 哪些方面做得很好
  • 你会如何改进
  • 意料之外的挑战
  • 培养的技能

示例:

## Learnings

### What Worked
- **Early user research** prevented us from building the wrong solution
- **Cross-functional alignment** meetings kept everyone on the same page
- **Launching with analytics** let us measure impact immediately

### What I'd Do Differently
- **More A/B testing:** We launched the full redesign at once. Would have preferred to test individual changes to understand what drove results.
- **Earlier mobile focus:** We designed desktop-first then adapted. Starting mobile-first would have been more efficient.
- **Stakeholder education:** Spent too long convincing leadership. Would start stakeholder alignment earlier next time.

### Skills Developed
- Advanced Figma prototyping
- Working with A/B testing frameworks
- Presenting data-driven design decisions to executives

按角色划分的案例研究类型

产品经理案例研究

重点关注:

  • 战略与优先级排序
  • 利益相关者管理
  • 指标与成果
  • 技术权衡
用户体验/产品设计师案例研究

重点关注:

  • 用户研究
  • 设计流程
  • 视觉材料
  • 可用性改进
软件工程师案例研究

重点关注:

  • 技术架构
  • 问题解决方法
  • 系统设计
  • 代码质量/性能
市场营销案例研究

重点关注:

  • 战略与目标受众定位
  • 创意执行
  • 渠道表现
  • 投资回报率与归因

视觉元素

必备视觉材料
  • 前后对比
  • 关键界面或交付成果
  • 流程图
  • 结果图表
可选视觉材料
  • 用户旅程图
  • 线框图演进过程
  • 研究材料
  • 团队照片
视觉建议
  • 统一图片尺寸
  • 添加说明文字,解释每张图片
  • 如有需要,对敏感数据进行模糊处理
  • 确保图片尺寸适合移动设备

输出格式

创建案例研究时:

# CASE STUDY: [PROJECT NAME]

## Quick Facts
- **Role:** [Your role]
- **Company:** [Company]
- **Timeline:** [Duration]
- **Team:** [Team composition]
- **Impact:** [One-line result]

---

## Overview
[2-3 sentence summary of the project]

## Problem
[Context and challenges - what needed to be solved]

## Process
### Research
[What you learned]

### Approach
[How you tackled it]

### Key Decisions
[Important choices and rationale]

## Solution
[What you built/created - include visual descriptions]

### Feature 1
[Description]

### Feature 2
[Description]

## Results
[Quantified impact]

| Metric | Before | After | Change |
|--------|--------|-------|--------|

## Learnings
[Reflections and growth]

---

## Visual Asset List
[List of images/screenshots needed]

案例研究质量检查清单

  • ✅ 问题陈述清晰
  • ✅ 体现以用户/客户为中心
  • ✅ 清楚说明过程
  • ✅ 清楚说明你的具体贡献
  • ✅ 结果经过量化
  • ✅ 包含视觉材料
  • ✅ 坦诚说明挑战与经验
  • ✅ 长度适当(阅读时长为 3-10 分钟)
  • ✅ 校对完善
  • ✅ 能在面试中详细讨论

评论

支持 Markdown