Skip to content
Marketplace

case-study

by owl-listener

Craft a portfolio case study with narrative arc, process evidence, and outcomes. Use when telling a project's story to an external audience. For an internal stakeholder deck, use `presentation-deck`.

Overview

SKILL.mdRead at 9a6930c

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

Files 1 file

Install it by hand

Deska runs this for you, for every agent you pick. To run it yourself in a terminal:

npx skills add owl-listener/designer-skills --skill case-study

More from owl-listener

  • presentation-deckowl-listenerStructure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.2,800 installs on skills.sh0
  • typography-scaleowl-listenerCreate a modular type scale with size, weight, and line-height relationships. Use when establishing typographic structure. For line length only use `readable-measure`; for judging type on an existing screen use `critique-typography` (visual-critique).2,300 installs on skills.sh0
  • visual-hierarchyowl-listenerEstablish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).2,300 installs on skills.sh0
  • color-systemowl-listenerBuild a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use `dark-mode-design`; for chart palettes use `data-visualization`; for multi-brand token architecture use `theming-system` (design-systems).2,200 installs on skills.sh0
  • dark-mode-designowl-listenerAdapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use `color-system`.2,200 installs on skills.sh0
All skills by owl-listener