jotbook-templatelisted

# Design a jotbook HTML template The `html` output mode needs a real template before it works. The two gates differ, and this skill is the deliberate, named artifact both point at: - `jotbook-ink` hard-stops when `output_format: html` is set but `template_path` is empty or points at a missing file. - `jotbook-pencil` hard-stops when `--html` is passed but `template_path` is empty or missing — independent of `output_format`. This skill produces a stylesheet, a tokenized template, a populated preview, and token-conventions documentation tailored to *this* project, verifies them mechanically, and — only after you sign off — wires the settings so the HTML path is armed. It offers **two design paths**, recommended from the project's visual richness (step 1) but always the user's choice: - **Full panel** — the judge-panel workflow below. Worth it when the project has a real visual language and tone to harmonize with, so distinct directions can actually separate. - **Quick path** — a single opinionated design pass (or a baseline preset). Right for greenfield/utilitarian projects, or when the user just wants a clean, blog-like template without the exercise. **The fork lives only in the design phase.** Both paths build the same fixed sample, write the same four artifacts, run the same mechanical verification, and hit the same sign-off gate. Quick is not lower-rigor output — it just skips exploring a design space that may have no room to be explored. **User-triggered only.** Thi