Portfolio Case Study Builder

Overview

Portfolio Case Study Builder is a prompt-flow skill that transforms work projects into compelling portfolio case studies. It guides individual practitioners — designers, developers, marketers, consultants — through structuring their project narrative to demonstrate process, impact, and craft, optimized for portfolio websites, job interviews, and award submissions.

Unlike corporate B2B case studies (handled by case-study-storyteller), this skill focuses on personal project showcase — what you did, how you did it, and why it mattered.

When to Use

Use this skill when the user asks to:

Write a case study for their portfolio website
Prepare a work sample narrative for a job interview
Create a freelancer pitch project showcase
Draft an award submission project description
Write a Dribbble or Behance project description
Document a project for professional reference

Trigger keywords: portfolio case study, project case study, work sample write-up, portfolio project description, design case study, UX case study, project showcase, work portfolio narrative

Workflow

Step 1 — Project Information Capture

Collect from the user:

Project name and type
Their role and contribution (especially in team projects)
Client or context (with permission)
The problem or brief they were given
Process steps taken
Solution delivered
Results or metrics achieved
Visual assets available (for pairing suggestions)
Target audience for the case study
Desired length and depth

Step 2 — Problem Framing

Frame the initial challenge in a way that hooks the reader:

What was the situation before the project?
What specific problem needed solving?
Why was this problem worth solving?
What constraints existed (time, budget, technical)?

Step 3 — Process Storytelling

Narrate the journey, not just the steps:

Research / Discovery: How did you understand the problem?
Ideation / Exploration: What approaches did you consider?
Development / Execution: How did you build or create?
Iteration / Refinement: What changed and why?
Collaboration: How did you work with others? (Be accurate about individual contribution.)

Step 4 — Solution Articulation

Describe the final solution with clarity:

What was delivered?
How does it solve the original problem?
What makes it distinctive or innovative?

Step 5 — Impact Quantification

Present results honestly:

Quantified metrics where available (conversion rates, user growth, time saved)
Qualitative feedback (client satisfaction, user testimonials)
Personal learning and growth

Step 6 — Visual Pairing Suggestions

Suggest where visuals would strengthen the narrative:

"Show wireframe sketches here"
"Include before/after comparison"
"Embed a short demo video at this point"

Templates

Design Case Study

For UX/UI, graphic, and product designers. Emphasizes design thinking, user research, and visual outcomes.

Development Project Showcase

For software engineers and developers. Emphasizes architecture decisions, technical challenges, and code quality.

Marketing Campaign Case Study

For marketers and growth professionals. Emphasizes strategy, execution, and measurable results.

Consulting Engagement Summary

For consultants and strategists. Emphasizes problem diagnosis, methodology, and client impact.

Research Project Narrative

For researchers and analysts. Emphasizes methodology, findings, and implications.

Output Format

The output includes:

Case Study Draft — Structured with section headers and narrative flow
Visual Pairing Notes — Where to insert screenshots, mockups, or demos
Role Accuracy Note — If team project, highlights accurate individual contribution description
Length Variants — Full version + shorter summary for different contexts

Safety & Compliance

No fabricated project results or metrics — use only data the user provides
No disclosure of client-confidential information without explicit permission
Encourage accurate representation of personal contribution within team projects
If the user describes a team project, prompt: "What specifically was your role?"
This is a descriptive prompt-flow skill with zero code execution, zero network calls, and zero credential requirements

Acceptance Criteria

User describes a project; output is a structured case study with problem, process, solution, and impact sections
Visual pairing suggestions are included where relevant
For team projects, individual contribution is accurately described
No fabricated metrics or confidential client information
Multiple length variants are provided when requested

Examples

Example 1: Design Portfolio

User says: "I redesigned a banking app. It increased user retention by 30%. I did the UX research and UI design. Help me write it up for my portfolio."

Skill guides: Frame the banking UX problem, narrate research and design process, showcase the solution, quantify the impact with the 30% metric, suggest visual pairings.

Example 2: Development Project

User says: "I built an internal tool that saved my team 20 hours a week. I was the sole developer. Need a case study for interviews."

Skill guides: Frame the inefficiency problem, narrate technical decisions, describe the solution architecture, quantify the time savings, emphasize personal contribution.