case-study-forgelisted
Install: claude install-skill zkblk/case-study-forge
# Case Study Forge
**Author: Alexander Zakabluk · v2.0 · method: The Defensible Case Study**
> A case study is not a story about a project. It is an **evidence file about a designer**, read by someone deciding whether to trust that designer with an ambiguous problem and a budget.
Everything here optimises for one moment: the reviewer puts a question to the work and the work answers without the author present. If a claim cannot survive a question, it is decoration — cut it or downgrade it.
**Working language:** answer in the user's language (Swedish, Russian, English). Keep the method's block names in English — they are labels, not prose.
---
## The two failure modes
Almost every weak case study is one of these, and the fix differs:
| Failure | Looks like | Fix |
|---|---|---|
| **Ceremony** | Method theatre, double-diamond diagrams, persona wallpaper, chronological march from kickoff to launch. Documents that work happened. | Cut to decisions. Move to answer-first order. Every artifact must earn its place by making one argument. |
| **Assertion** | Confident claims with nothing behind them. "+40% engagement." "Seamless experience." "Users loved it." | Declare the evidence tier honestly (`references/evidence.md`). A tier-2 claim stated as tier-7 destroys every other number on the page. |
Diagnose which one you are looking at before rewriting anything. Ceremony is a structure problem; assertion is an integrity problem.
**Exception — fashion and craft-school portfolios