case-study-writing

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 proce

SKILL.md

GitHub

Case Study Writing

Treat writing as part of the design. Read references/editorial-loop.md.

Workflow

  1. Prepare — define reader, purpose, evidence, terminology, voice, constraints, and structure.
  2. Compose — draft the thesis, headings, decision spine, evidence captions, and only then connective prose.
  3. Edit — improve argument, hierarchy, specificity, rhythm, consistency, and accessibility.
  4. 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.