code-story · git:20260819.75b2f19 · 2026-08-19 · sha256 676361efe0a8ec88
code-story git:20260819.75b2f19A
Immutable. This exact content never changes and is served at /api/v1/blob/676361efe0a8ec88.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_4owtaszuykp2zuw6/676361efe0a8ec88c8fba0c6e782b2955fe03080e7931c1ee75d978d72a1bb06.json
Then /plugin install code-story@markdownregistry-4owtaszuykp2zuw6 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: code-story description: Build a wizard-style HTML page that teaches how and why a change works. disable-model-invocation: true --- `/code-story <request>` — a PR, a diff, a branch, one commit — plus whatever the human says they do not understand. A **code story** cuts a change into **chapters** and walks the reader through one at a time. A chapter answers one question, and its title *is* that question. It pulls hunks from whichever files hold that mechanism, so one chapter often spans several. A code story explains **why** the code changed the way it did. Write it for a day-one contributor — someone who knows nothing yet about this domain, this codebase, or its architecture. Tell it around code: each chapter is built from the lines it is about — changed, unchanged, or from a dependency — with a note pinning each claim to a line. Prose sets up the question and diagrams show shape; both are there to make those lines mean something. One chapter per mechanism, not per file and not per commit — a two-file change with three ideas in it gets three chapters. Write in short, plain sentences: the reader is new here, so shorter beats fuller. ## Build it 1. **Read [`references/example.html`](references/example.html)** — a finished six-chapter story about a real 25-file PR. It is the specification: chapter size, how much diff one chapter shows, the voice of the notes, which changes earn a diagram, and how the files that earn no chapter get named and dismissed in a line each. 2. Read the change, and what explains it: the PR body, the linked issue, the review comments, the code before it, and the unchanged or third-party code the change leans on. Where the reasoning is nowhere to be found, the story says so rather than inventing one — and says so again at the end, in its own closing section naming where each *why* came from. Say plainly where you think the change is wrong; a reader who trusts a story that was quietly covering for the code loses the story too. 3. Copy [`references/template.html`](references/template.html) into the scratchpad and write the chapters into `<main>`, deleting its leading comment. The rail, chapter numbering, progress, note numbering, and the note↔code link all compute themselves — write `<article>` blocks and nothing else. 4. Publish with the Artifact tool, then hand over the link. Without that tool, write to the scratchpad and `open` the file. `template.html` already is the design, so publish it as it stands.