code-story · git:20260818.e84c8b8 · 2026-08-18 · sha256 8745139b318111e1
code-story git:20260818.e84c8b8A
Immutable. This exact content never changes and is served at /api/v1/blob/8745139b318111e1.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_4owtaszuykp2zuw6/8745139b318111e1e7c5dc9fbd39111244e3883382f0e96bbdf7cf1ef4a9d84e.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, one chapter at a time. 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. ## 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. 3. Copy [`references/template.html`](references/template.html) to the output path and write the chapters into `<main>`. 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. Without it, write to the scratchpad and `open` the file.