Explain Visually

The goal: the reader quickly understands what changes, how it works and why, and can decide, without reading every line of code. Show rather than tell, concise first, details on demand. One page, ~1,000–1,500 words: short story steps, and the detail a decision needs in the option rows and toggles.

Say exactly what the facts say, above all in the headline:

• "Migrated" is not "kept" or "working"; "honoured" is not "unchanged". Name exceptions in the same sentence: "263 rules migrate; 1 must be switched off".
• A number measured under changed conditions is not "the same": "5.3 s, after switching that rule off".
• What holds for some members doesn't hold for the group: name them ("react-x and react-jsx load as plugins").
• Write for a reader new to the tools: gloss each tool or term the first time it appears, in a few words in the same sentence ("tsgolint, Oxc's type-checking helper"), in the story and in option rows alike.

The look comes from the explainer-kit skill; each chapter follows its explain-with-* skill.

Use this skill when