brand-book-htmllisted

Build a full brand guidelines document ("brand book") as a self-contained HTML file — open it anywhere, print it to PDF, or publish it as a Claude Artifact — and ship it with a matching agent-usable brand skill. No design app required. The brand can be your own or a client's. Use when the user wants to create brand guidelines, a brand book, a brand / identity system, a style guide, or a logo/mascot spec, or asks to "turn these assets into guidelines" or "make a brand book for <brand>". For an editable Paper canvas instead, use `brand-book-paper`. Two deliverables every time: (1) the HTML book, (2) a `<brand>-brand` skill that keeps that brand's product on-brand during agentic coding.
ordinarynerds/brand-book · ★ 1 · Web & Frontend · score 77

Install: claude install-skill ordinarynerds/brand-book

# Brand Book Builder — HTML Turn a brand's raw assets (a logo, maybe a mascot, colours, fonts, a bit of voice) into two things: 1. **The brand book** — an 11-spread, Swiss-editorial guidelines document rendered as a **single self-contained HTML file**: open it in any browser, print it to PDF, or publish it as a Claude **Artifact**. Fonts and SVGs are inlined, so it travels with no external requests. 2. **The companion brand skill** — a self-contained `<brand>-brand/` skill (SKILL.md + tokens + logo rules + voice + the actual asset files) that any coding agent loads to apply and update the brand in that brand's codebase. The brand is whoever's you're documenting — your own product, or a client's. Nothing here assumes a client relationship. Deliverable #2 is not optional. A brand book nobody can operationalize is a PDF that rots. The skill is how the brand stays alive in the product. **Both deliverables derive from one file: `brand.json`** — a machine-readable spec of the whole brand (colours as semantic roles + oklch, type, logo/mascot, voice, layout). Author it once at intake; generate the book, the companion skill, and the token files from it so they can't drift. Schema: `references/brand-json.md`. > **HTML vs Paper.** This skill outputs a portable HTML file — the right default for almost > everyone (a browser is all it takes; it prints to PDF and publishes as an Artifact). If > the user specifically wants to hand-edit on a design canvas and has Paper, u