Keep AI generated interfaces consistent.
An individually plausible screen can still drift from the rest of a Project. Consistency comes from durable Project level direction that every agent can inspect and apply.
Why drift happens
Plausible choices do not add up to one coherent product.
An agent works from the current request, the files it can see, and the patterns it happens to notice. That can produce a credible screen without preserving the decisions made elsewhere.
When spacing, hierarchy, states, responsive behavior, and component choices are inferred again for each task, each answer can be locally reasonable while the Project gradually loses a shared visual and behavioral language.
What solves which part
Choose complete direction, not another temporary input.
Repeated prompts
A repeated request can remind one agent about a preference, but it must be reconstructed in every session. Small wording and context changes make it temporary direction, not a complete shared source of truth.
Themes
A theme usually supplies colors, type, or surface treatment. It does not tell an agent how layouts, components, states, responsive behavior, motion, accessibility, and product surfaces should work together.
Component libraries
A component library gives agents reusable parts. It rarely decides which parts fit the product, how to compose them, what hierarchy to establish, or how complete journeys should behave.
Automatic redesign
Automatic redesign changes an existing interface. Durable direction instead governs future agent work while leaving the Builder in control of whether and when existing screens change.
Complete Design System
A complete Design System connects principles, tokens, typography, layout, components, states, motion, accessibility, responsive behavior, examples, and validation. Its Design Contract is the inspectable root DESIGN.md artifact that gives this complete direction to agents in the Project.
Inspect before choosing
Evaluate the direction, evidence, and complete artifact.
Start by comparing every Design System Preview. The path below follows Foundation from its Preview through evidence and exact direction so the final command stays qualified.
- 01 / Direction
Open the Foundation Design System Preview
Inspect its intended fit, visual direction, foundations, component behavior, and representative product surfaces.
- 02 / Evidence
Review Foundation public evidence
Check its release metadata, validation, responsive coverage, color schemes, reduced motion, and accessibility evidence for the reference implementation.
- 03 / Complete direction
Inspect the Foundation Design Contract
Read the exact Foundation 1.0 Design Contract to judge the actual agent direction rather than relying on the visual specimen alone.
Qualified Installation
Install only after the fit is clear.
Installation places the complete selected release at the Project root and makes it discoverable through Project instructions. It does not redesign an existing interface, install dependencies, or replace the Builder's approval of file changes.
This command keeps the Foundation direction inspected above. Run it from the Project root after confirming the fit.