case-study
Skill1 starsChanged 4 months agoMITView on GitHub
Route and produce evidence-backed product or design case studies from raw notes, research, screenshots, specifications, decision logs, architecture, metrics, and project artifacts. Use when the user invokes /case-study, asks to write, critique, structure, or polish a portfolio case study, needs to explain a complex design project, or needs an AI-agent case study covering autonomy, human oversight, telemetry, trust, latency, failures, and recovery.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- matteotitta/genesys-skillstheir own version, first seen Nov 15, 2026
- BeautifulEngine/case-studytheir own version, first seen Nov 15, 2026
- tidycatc132/claude-skillstheir own version, first seen Nov 8, 2026
- Jakeschincariol/whale-skilltheir own version, first seen Nov 8, 2026
- lucasmaher-hash/claude-skillstheir own version, first seen Nov 1, 2026
- MakiDevelop/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use audit.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillaudit
Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- duncan-buildroom/freeskills★ 65same name
- darkroomengineering/cc-settings★ 53same name
- matteotitta/genesys-skills★ 53same name
- launchapp-dev/animus-cli★ 39same name
- ommakes/Skills★ 21same name
- SonwaneyY/portfolio-case-study-generator★ 17same name
- Jakeschincariol/whale-skill★ 15same name
- calven-ai/marketing-as-code★ 10same name
- scoobynko/case-study-skill★ 9same name
- kronus-tech/kronus★ 4same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 49
Never convert a proposal into an outcome.
- Distinctive: line 60
Run the accuracy, clarity, and brevity edit.
- Very specific: line 62
Run the quality gate in references/quality-gate.md.
- Very specific: line 65
Use assets/case-study-template.md when creating a new Markdown artifact.
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Case Study Dispatcher
Resolve the project, intended reader, available evidence, and requested format. Mark missing facts; never fill them with plausible fiction.
Route
| Need | Load |
| Flat timeline or missing story | narrative-arc-builder |
| Screens without rationale | extract-design-rationale |
| Architecture shapes the experience | system-architecture-translator |
| Imprecise or inflated technical copy | technical-microcopy-editor |
| Dense, repetitive, slow-to-scan draft | enforce-scannable-density |
| AI agent or probabilistic system | ai-agent-case-study plus the applicable skills above |
| Complex multichannel or branching journey | case-study-storytelling and case-study-story-map |
| Deep stakeholder decision narrative | case-study-design-decisions |
| General long-form drafting and finishing | case-study-writing |
Load the smallest set that covers the evidence and requested deliverable. When the user asks for a complete build from raw artifacts, apply the automated pipeline below as one workflow, not as separate reports.
Automated pipeline
Raw logs / notes / code / research
→ narrative-arc-builder
→ system-architecture-translator (when architecture affects the experience)
→ extract-design-rationale
→ technical-microcopy-editor
→ enforce-scannable-density
→ quality gateFor an AI-agent case study, apply ai-agent-case-study across every stage. It governs autonomy, permission, observability, uncertainty, intervention, and recovery; it is not an extra standalone report.
Evidence contract
Label every substantive claim:
- Executed — supported by a test, trace, artifact, or measured output.
- Observed — supported by research notes, usability observations, or recorded behavior.
- Reported — attributed to a stakeholder, participant, or project record.
- Proposed — a recommendation, hypothesis, future metric, or unverified narrative bridge.
Never convert a proposal into an outcome. Never invent research, metrics, quotes, responsibilities, constraints, alternatives, or impact. Use [evidence needed: …] where the story has a material gap.
Workflow
- Inventory source artifacts and create an evidence ledger.
- State the protagonist, goal, inciting problem, constraints, pivotal decisions, delivered change, and measured result.
- Select the smallest route above.
- Build the narrative arc before drafting sections.
- Translate consequential system behavior into visible states, controls, and recovery.
- Extract the decision rationale and rejected alternatives.
- For AI systems, document supervision and uncertainty before visual polish.
- Run the accuracy, clarity, and brevity edit.
- Enforce scannable density without deleting evidence.
- Run the quality gate in
references/quality-gate.md. - Deliver one clean case study plus a short unresolved-evidence list.
Use assets/case-study-template.md when creating a new Markdown artifact.
Done
A case study is ready only when a skeptical reader can answer:
- What changed, for whom, and under what constraints?
- What did the designer actually own?
- Which decisions were difficult, what alternatives existed, and why were they chosen?
- What evidence supports the outcome?
- What remains unknown, limited, or confidential?
- For AI agents: where does autonomy stop, how does a human intervene, what is observable, and how does failure recover?
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

