Skip to content
cccskills
FreePublished on GitHub

case-study

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`.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

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).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

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).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

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).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

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`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

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`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill