case-study
This Claude Code skill structures compelling design case studies for portfolios by organizing projects into six sections: overview, challenge, process, solution, impact, and reflection. Use it when documenting design work for job applications, presentations, or portfolio websites, as it guides designers to demonstrate their problem-solving approach, decision-making rationale, and measurable outcomes while balancing process transparency with concise storytelling.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/case-study && cp -r /tmp/case-study/designer-toolkit/skills/case-study ~/.claude/skills/case-studySKILL.md
# 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
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).