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
Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.
Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.
Communicate design's contribution to business and user outcomes in terms that resonate with stakeholders.
Create QA checklists for verifying design implementation accuracy.
Establish design review gates with criteria, checklists, and approval workflows.
Plan and facilitate design sprints from challenge framing through prototype testing.
Create developer handoff specifications with measurements, behaviors, assets, and edge cases.
Design team workflows covering task management, collaboration rituals, and tooling.