Skip to content
Back to skills

Portfolio Case Study Writer

ASecurity

Transform resume bullets into detailed portfolio case studies

  • 8 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 20, 2026
businessgoperformance

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 20, 2026

npx -y skills add tstapler/dotfiles --skill portfolio-case-study-writer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Portfolio Case Study Writer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Portfolio Case Study Writer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tstapler-portfolio-case-study-writer/badge)](https://www.skillsdirectory.com/skills/tstapler-portfolio-case-study-writer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: portfolio-case-study-writer
description: Transform resume bullets into detailed portfolio case studies
---

# Portfolio Case Study Writer

## When to Use This Skill

Use this skill when the user:
- Wants to create portfolio case studies
- Needs to expand resume bullets into detailed writeups
- Is building a portfolio website
- Wants to showcase project work in depth
- Mentions: "case study", "portfolio", "project writeup", "work samples", "portfolio piece"

## Core Capabilities

- Transform resume bullets into detailed case studies
- Structure case studies for maximum impact
- Create compelling project narratives
- Balance technical detail with business context
- Format for portfolio websites
- Tailor depth to audience

## Case Study Purpose

**Why Case Studies Matter:**
- Resumes show WHAT you did; case studies show HOW and WHY
- Demonstrate thinking process, not just outcomes
- Allow deeper showcase of skills
- Differentiate you from other candidates
- Required for many PM, UX, and creative roles

## The Case Study Structure

### Standard Structure

```
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)
```

### Time to Read
- **Quick Read:** 3-5 minutes (essential for portfolio)
- **Deep Dive:** 10-15 minutes (for interested readers)

## Section-by-Section Guide

### 1. Overview Section

**Purpose:** Hook the reader, provide context

**Include:**
- Project name and company
- Your role
- Timeline
- Team size
- One-sentence summary of impact

### 2. Problem Section

**Purpose:** Set up why this work mattered

**Include:**
- Business context
- User pain points
- Key metrics or goals
- Constraints

### 3. Process Section

**Purpose:** Show your thinking and methodology

**Include:**
- Research conducted
- Stakeholders involved
- Hypotheses formed
- Options considered
- Decisions made (and why)

### 4. Solution Section

**Purpose:** Show what you actually created

**Include:**
- Visual artifacts (mockups, screenshots, diagrams)
- Key features/changes
- Technical implementation (if relevant)
- How it addressed the problems

### 5. Results Section

**Purpose:** Prove impact with data

**Include:**
- Quantitative results (with timeframe)
- Comparison to goals
- Secondary metrics affected
- Business impact

### 6. Learnings Section

**Purpose:** Show growth mindset and self-awareness

**Include:**
- What worked well
- What you'd do differently
- Unexpected challenges
- Skills developed

See `references/section-examples.md` for a complete worked example of each of the six sections above (Overview, Problem, Process, Solution, Results, Learnings).

## Case Study Types by Role

### Product Manager Case Study
**Focus on:**
- Strategy and prioritization
- Stakeholder management
- Metrics and outcomes
- Technical trade-offs

### UX/Product Designer Case Study
**Focus on:**
- User research
- Design process
- Visual artifacts
- Usability improvements

### Software Engineer Case Study
**Focus on:**
- Technical architecture
- Problem-solving approach
- System design
- Code quality/performance

### Marketing Case Study
**Focus on:**
- Strategy and targeting
- Creative execution
- Channel performance
- ROI and attribution

## Visual Elements

### Must-Have Visuals
- Before/after comparisons
- Key screens or deliverables
- Process diagrams
- Results charts

### Nice-to-Have Visuals
- User journey maps
- Wireframes evolution
- Research artifacts
- Team photos

### Visual Tips
- Use consistent image sizing
- Add captions explaining each image
- Blur sensitive data if needed
- Ensure mobile-friendly image sizes

## Output Format

Structure the finished case study as: quick facts (role, company, timeline, team, impact), then Overview, Problem, Process (research/approach/key decisions), Solution (with visual descriptions), Results (with a before/after metrics table), Learnings, and a visual asset list.

See `references/output-report-template.md` for the ready-to-fill template.

## Case Study Quality Checklist

- ✅ Clear problem statement
- ✅ Evidence of user/customer focus
- ✅ Process clearly explained
- ✅ Your specific contributions are clear
- ✅ Quantified results
- ✅ Visual artifacts included
- ✅ Honest about challenges/learnings
- ✅ Appropriate length (3-10 min read)
- ✅ Proofread and polished
- ✅ Can discuss in detail in interview

---

## Related Skills

| Skill | When to apply |
|-------|--------------|
| `resume-bullet-writer` | Condense case study results into resume achievement bullets |
| `resume-quantifier` | Find or estimate metrics for the Results section |
| `creative-portfolio-resume` | Integrate case study links into a designed portfolio resume |
| `interview-prep-generator` | Build STAR stories from the case study's Process section |
| `writing-humanize` | Make AI-drafted narrative sections sound natural |
| `pdf-proof` | Proofread final case study before publishing to portfolio |
| `meta-research-workflow` | Research audience expectations for case study depth and format |

Files in this skill

  • SKILL.md5 KB
  • references/output-report-template.md846 B
  • references/section-examples.md4.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…