case-study-writing
Skill1 starsChanged 4 months agoMITView on GitHub
Draft, edit, and finish concise design case-study copy from an evidence ledger or structured outline. Use when a portfolio case study is verbose, vague, generic, overly chronological, full of UX process theater, missing scannable headings and captions, inconsistent in voice, or needs publication-ready structure without inventing research, metrics, outcomes, or quotes.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- AngelescuCiprian/claude-skillstheir own version, first seen Aug 22, 2026
- nikunj812/claude-skilltheir own version, first seen Jul 1, 2026
- CAPP-Financials/Consulting_Braintheir own version, first seen Apr 24, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- AngelescuCiprian/claude-skills★ 0same name
- CAPP-Financials/Consulting_Brain★ 0same name
- nikunj812/claude-skill★ 0same name
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
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Treat writing as part of the design.
- Distinctive: line 21
Use headings that carry the argument.
- Distinctive: line 22
Prefer concrete nouns and verbs over design adjectives.
- Distinctive: line 24
Keep captions analytical: explain what the reader should notice and why it mattered.
- Distinctive: line 27
Do not invent participant quotes or compress several people into a fake quote.
- Very specific: line 28
Use [evidence needed: …] rather than generic filler.
“Common” is measured: kept by at least 6 in 10 of the 3 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 Writing
Treat writing as part of the design. Read references/editorial-loop.md.
Workflow
- Prepare — define reader, purpose, evidence, terminology, voice, constraints, and structure.
- Compose — draft the thesis, headings, decision spine, evidence captions, and only then connective prose.
- Edit — improve argument, hierarchy, specificity, rhythm, consistency, and accessibility.
- Finish — verify facts, links, captions, alt text, credits, redactions, formatting, and unresolved placeholders.
Writing rules
- Lead with the outcome and defining constraint.
- Give each paragraph one job.
- Use headings that carry the argument.
- Prefer concrete nouns and verbs over design adjectives.
- Replace “we conducted” chronology with what the evidence changed.
- Keep captions analytical: explain what the reader should notice and why it mattered.
- State ownership precisely.
- Preserve uncertainty and missing evidence.
- Do not invent participant quotes or compress several people into a fake quote.
- Use
[evidence needed: …]rather than generic filler.
Output
Return the revised case study, a short evidence-gap list, and an edit note naming any claims removed or softened because they were unsupported.
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.

