iconslisted

# /icons Icons are a common failure point: mixed libraries, mismatched stroke weights, decorative-only icons, hallucinated SVG shapes. This skill enforces **one library, one style, verified geometry**. ## When to use - After `/media` — media assets are in place, now icons are the last visual asset. - Before `/build` — build references the icon set from `site/media/icons/`. - Rerun anytime a new concept is added to the copy. ## Requirements - `DESIGN-LOCK.md` LOCKED (need §2 type, §3 color, §5 motion, §7 imagery for style spec). - `brief/copy-analysis.md` exists (concepts are extracted from here). - `inbox/texts/` populated (backup source for concept extraction). ## Process ### Step 1. Extract concepts from context Read: - `brief/01-business.md` — niche, product, services. - `brief/copy-analysis.md` — recommended section structure and key claims. - `brief/03-goals.md` — CTA labels and offer names. - `inbox/texts/*` — surface-level scan for repeating nouns. Extract **5-15 icon concepts**. Each concept is a short label + intent: ``` - consulting → conversation, expertise - roadmap → path, planning - reporting → chart, transparency - fast-turnaround → clock, speed - privacy → lock, safety - multi-region → globe, coverage ``` Present the extracted list to the user. Ask: "add, remove, or rename any concepts before we map to icons?" ### Step 2. Compute style spec from DESIGN-LOCK Read DESIGN-LOCK and deri