Open the book

A sample travel book, written with Claude the way I wrote mine: three invented days, one chapter each. Turn the pages; on the right, what is underneath the page you're on.

The method, as text

This page shows a sample book: an invented three-day trip (Kanazawa, Kyoto, Naoshima) in seven chapters and a cover, with three plates drawn as code (the cover and two drawings), each in two editions. Everything it shows is in the repo, and the README walks through it.

  1. The skeleton stays out of the book. Dates, bookings and who travels live in a private SKELETON.md (gitignored). Sessions read it to know which day is where; the book only takes the places and the order.
  2. A style file every session reads first. STYLE.md: the order inside a chapter, the tone, and the content rules. Rules said only in a chat are forgotten by the next session.
  3. One chapter per day, always built the same way. Five phrases for the day; the place and how people live with it, with one fact to tell at the table; what to look at; and the sources at the end.
  4. Every foreign word three ways: script · romanisation · meaning, so it can be read out loud and recognised on a sign.
  5. No times, prices or bookings. They change and belong in your tickets. The book holds what doesn't change.
  6. Plates drawn as code. A Python file writes an SVG; one drawing has two editions, grey for e-ink and colour for tablets, switched by one CSS class. Chrome renders it with LCD text off, so e-ink shows no colour fringes; the grey PNGs keep the EPUB small enough for Send to Kindle.
  7. The build. An EPUB is a zip: mimetype first and uncompressed, then everything else. scripts/build-epub.sh, about twenty lines.
  8. The companion. A Claude Project that has read the book answers on the street; edits happen in a Claude Code session on the repo, from a laptop or a tablet. COMPANION.md has the instructions template.

← All the pieces · Back to the README.