Design Composition Check

Use this before a second feature starts building against a new or unfamiliar design system — after the system exists (tokens, components, or an extracted style guide), before it becomes a shared dependency.

Trigger

Run this when all of the following hold:

• The design system or token set is new or unfamiliar: freshly researched, extracted from a reference, or ingested from a non-technical source — not something already proven across features in this project.
• More than one feature is about to depend on it.
• No prior screen in this project has exercised it yet.

Skip conditions

• An established, framework-driven UI (Material, Ant, shadcn/ui, or similar) already proven elsewhere in this project or organization.
• A routine styling change to an existing, already-validated system.
• No candidate screen in scope scores on any of the three hardness signals (information density, state variety, or primary/critical flow) — state which signal each candidate screen failed before skipping on this ground.

State the skip condition in one line and stop. Do not select screens or render a verdict.