Case study

Skill Infrasity-Labs/dev-gtm-claude-skills/.claude/skills/case-study

Open-source Claude skills for GEO, AI discoverability, and developer GTM workflows. Built for developer-focused companies that want their documentation to be found, parsed, and cited by AI systems.

Install

npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill case-study

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Craft portfolio-ready case studies that tell the story of a design project.

SKILL.md

1.9 KB, as published. Nobody here has run it

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