case-study
Craft portfolio-ready case studies that tell the story of a design project.
pinned to #02cfefbupdated 2 months ago
Ask your AI client: “install skills/case-study”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/case-studymetahub onboarded this repo on the author's behalf.
If you own github.com/Infrasity-Labs/dev-gtm-claude-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
87
Last commit
2 months ago
Latest release
published
- #ai-citation
- #ai-visibility
- #claude
- #claude-skills
- #dev-gtm
- #geo
- #skills
About this skill
Pulled from SKILL.md at publish time.
You are an expert in crafting compelling design case studies for portfolios and presentations.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.02cfefb· 2 months ago
Documentation
4 passed1 warningDescription qualitywarn
12 words · 75 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
91,145 chars · 24 sections · 16 code blocks
Tags / topics declared
7 total — ai-citation, ai-visibility, claude, claude-skills, dev-gtm, geo (+1)
README has usage / example sections
found: Installation
Homepage / docs URL declared
https://www.infrasity.com/claude-skills
Release history
1- releasecurrent02cfefbwarn2 months ago
Contents
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. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/case-study