typelisted

# Type — typography router Routes typographic work to the smallest sufficient set of focused skills. Do not answer typography questions from memory when a skill below covers them: the skills carry the decision procedures, the ranges, and the source conflicts that "looks right" misses. ## Core principle **Books teach judgment. Current standards teach implementation.** Never emit a bare universal constant. Encode the decision and its inputs. > ❌ "Body text should always be 16px." > ✅ Determine body-text size from the typeface's apparent size, x-height, target > device, reading distance, content density, user needs, and available line length. > Treat 16px as a common browser-oriented starting point, not a universal optimum. > Validate readability, zoom behavior, line length, and hierarchy in the rendered > context. ## 1. When to invoke - The user types `/type` (or `$type`). - Any task that sets, chooses, scales, spaces, loads, tokenizes, audits, or critiques type. - A screen "looks off", "feels cheap", or "looks AI-generated" and the cause may be typographic. - You are about to answer a typography question from memory. **Do not** invoke for non-typographic layout — that belongs to the general design skills. Two topics are split rather than excluded: *type* that moves is `motion-typography` (general interface motion is not this pack's), and *type* that carries colour or is made of glyphs is `color-and-icon-fonts` (general colour systems and iconography are not). If th