design-iconslisted

# Design icons One instance means the class: a report of one template glyph is a report of every icon of its kind. The job starts with the inventory, picks a family per kind with the owner, and lands the family in one change. `docs/icons.md` of the kit is the guide; `STANDARD.md` §4 names the site's families once they exist. ## Read first `STANDARD.md` §4 (the families the site already has, and the reference mark a family is drawn in the language of); `docs/icons.md`; where the icons render (`src/components/`, the `icon` fields of `content/pages/*.yaml`). ## Steps 1. **Inventory.** `pnpm build` then `pnpm kit icons audit` — every `<img>` up to 96 px and every inline `<svg>` on every page, with its rendered size, colour, section, heading and the copy beside it, as `.parity/icons/audit.json` and a sheet, one row per page. Group them by kind: the chrome's line icons, the marks beside copy, other companies' logos, illustrations. A file used on three pages is one decision. 2. **A family per kind**, chosen with the owner (`design-options`): - **Line icons** (navigation, the chrome, a card's glyph): Lucide, through `pnpm kit icons add lucide:<name>…` — the site installs `lucide-static`, the manifest `src/config/icons.json` lists the ids, the generated `src/config/icons.ts` carries the paths and the licence, and `<Icon {...ICONS["lucide:house"]} size={20} />` renders one in the current colour. One stroke width for the whole family. -