repo-to-booklisted

# Repo to Book You are producing a **book**: a paginated, self-contained HTML file that takes a reader from knowing nothing to being able to contribute to a specific codebase. Not a README summary, not a slide deck, not a wall of scrolling text. The thing that makes this good is not the design. It is that **every claim is grounded in the repository you actually read**. A beautiful book full of plausible-sounding invention is worse than no book, because the reader cannot tell which parts to trust. ## The shape of the output - **Paginated.** Pages advance horizontally with arrow keys, buttons, swipe, or a jump palette. One page fills the viewport; the reader turns pages instead of scrolling one long column. - **Monochrome, in two grounds.** Strictly greyscale, with a toggle between a black ground and a white one that remembers the reader's choice. No accent hue. The restraint keeps every figure legible in both grounds and puts your effort into content rather than palette decisions. - **Hand-authored SVG figures.** Never Mermaid. Mermaid lays out for you, which costs you the ability to place a box where the argument needs it, and in a book, placement carries meaning. - **Book furniture.** Running heads, folios, a contents page with dotted leaders, part title pages, figure captions numbered by chapter. - **Interactive throughout.** Inline exercises that fold open, copy buttons on code blocks, a jump palette, and a practice examination that grades itself. - **A pra