talismanlisted

# Talisman Turn a codebase into a beautiful, accurate, brand-styled PDF book. The output is a `docs/guide/` LaTeX project (`main.tex` + `preamble.tex` + `chapters/*` + `figures/*` + `Makefile`) that builds to `main.pdf`. Two things make or break the result, in order: **accuracy** (describe what the code actually does, not what a marketing README claims) and **brand fidelity** (the real colors, logo, and font character of the product). Everything else is craft on top. ## Workflow Do these in order. Phases 1–2 can overlap. ### 1. Extract the brand identity from the codebase The document should look like it came from the product. Find: - **Colors** — grep the web app's CSS/theme for the palette: `globals.css`, `tailwind.config.*`, `theme.*`, shadcn `:root` blocks, `--primary`, `--brand-*`. Modern apps define these in `oklch()` — LaTeX can't use that, so run `scripts/oklch_to_hex.py` to convert. Capture: a signature/brand color, the darkest shade (body ink), 1–2 accents, a muted gray. - **Logo** — find it (`public/*logo*`, `*.webp`, `favicon`, a `BrandLogo` component pointing at a default asset). pdflatex can't read webp/svg; run `scripts/prepare_logo.py` to get a PNG and its background color. - **Fonts** — note the app's font (e.g. Outfit, Inter, Geist) so you can match its *character* with an installed LaTeX family. See `references/environment.md` — you almost never get the exact font; pick the closest one that's installed and note the substitution hone