doc-visual-direction

To define a visual language, select a skin family, surface rules, typography posture, iconography system, and motion profile. This establishes product identity and prevents shipping generic, mismatched UI during the discovery phase.

Documenting UI design direction involves defining the product's visual posture, including density and trust-vs-novelty stance. It produces ordered outputs with anti-pattern constraints to feed directly into the project's design documentation file.

You need to establish a design system when your product lacks identity or the UI feels generic. It applies to kickoff, discovery, and design-audit scenarios where choosing a coherent visual language early prevents mismatched interfaces.

Choosing typography and surface rules requires mapping a product posture—precision, warmth, density, or aspiration—to a specific skin family. This defines base, panel, and overlay behaviors alongside iconography tier rules for consistent UI.

Yes, setting visual direction includes listing anti-patterns to avoid and providing an optional fallback skin. This design risk control ensures your UI remains consistent if the first visual language choice proves not viable.