Case Study
Turn a finished design project into a portfolio-ready narrative with process, decisions, and measurable impact.
Overview
Case Study is an agent skill most often used in Launch (also Validate and Grow) that crafts portfolio-ready design narratives with a 6-section structure and visual storytelling rules.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill case-studyWhat is this skill?
- 6-part narrative arc: Overview, Challenge, Process, Solution, Impact, Reflection
- Visual storytelling guidance: sketches, wireframes, iterations, before/after, annotated decisions
- Impact section expects quantitative metrics, qualitative feedback, and honest “what I’d do differently”
- Overview hook pattern: role, team, timeline, and one key outcome metric up front
- 6-section case study structure (Overview through Reflection)
Adoption & trust: 574 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You finished strong design work but only have screenshots—no clear story of challenge, process, and impact for portfolios or pitches.
Who is it for?
Designers and founder-designers publishing portfolio pieces, deck appendices, or client proof after shipping a feature or product slice.
Skip if: Raw UX research plans or wireframe generation before you have a project outcome to narrate.
When should I use this skill?
User wants a portfolio-ready design case study, presentation narrative, or structured story of a design project with process and impact.
What do I get? / Deliverables
You get a structured, presentation-ready case study covering overview through reflection, with hooks for metrics and annotated design decisions.
- Structured case study outline or draft copy
- Visual storytelling checklist for iterations and annotations
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch is the canonical shelf because case studies are primarily distribution artifacts—portfolios, pitches, and stakeholder presentations that get work in front of buyers and hiring managers. Distribution fits storytelling assets that prove credibility beyond the product itself.
Where it fits
Document a validation prototype’s user pain and iteration loop before full build funding.
Publish a portfolio case study with a one-line hook metric for hiring or client outreach.
Repurpose the Impact and Reflection sections into a blog post that compounds authority.
How it compares
Use instead of free-form “write about my project” chat when you need a repeatable 6-section portfolio framework.
Common Questions / FAQ
Who is case-study for?
Solo designers, indie founders, and small teams who need credible portfolio or pitch narratives that demonstrate process and impact.
When should I use case-study?
At Launch when distributing portfolio or sales proof; at Validate when documenting a prototype’s story for stakeholders; at Grow when turning shipped work into content that compounds trust.
Is case-study safe to install?
It is editorial and template guidance only—review the Security Audits panel on this Prism page for the package source, and avoid pasting confidential client data into prompts.
SKILL.md
READMESKILL.md - Case Study
# Case Study You are an expert in crafting compelling design case studies for portfolios and presentations. ## What You Do You structure case studies that tell the story of a design project, demonstrating process, thinking, and impact. ## Case Study Structure ### 1. Overview - Project title and one-line summary - Your role and team composition - Timeline and scope - Key outcome or metric (the hook) ### 2. Challenge - Business context and problem statement - User needs and pain points - Constraints and requirements - Why this problem mattered ### 3. Process - Research methods and key findings - Ideation and exploration (show breadth) - Key decisions and rationale (show depth) - Iteration based on feedback or testing ### 4. Solution - Final design walkthrough - Key features and interactions - How it addresses the original challenge - Design system and technical considerations ### 5. Impact - Quantitative results (metrics, data) - Qualitative results (user feedback, team response) - Business impact - What you would do differently ### 6. Reflection - Key learnings - Challenges overcome - Skills developed - How this work influenced future projects ## Visual Storytelling - Show the journey, not just the final product - Include sketches, wireframes, and iterations - Use before/after comparisons - Annotate key design decisions - Include real screenshots, not just mockups ## Writing Tips - Write in first person for your contributions - Be specific about your role vs team contributions - Quantify impact wherever possible - Keep it scannable (clear headings, short paragraphs) - Edit ruthlessly — shorter is better ## Best Practices - Lead with the most impressive outcome - Show process, but don't document every step - Highlight moments of insight or pivots - Include enough context for someone unfamiliar - Tailor depth to the audience