Interface design

Build a functional interface whose visual system, information architecture, states, and motion follow from the product's job. Preserve an effective existing system; do not replace it with a personal preset.

Establish the design problem

Recover available context before asking questions:

• product, audience, primary task, and success condition;
• route or component scope and implementation stack;
• existing design tokens, components, assets, typography, and brand rules;
• content shape, density, hierarchy, and likely extremes;
• supported viewports, input methods, themes, and accessibility requirements;
• required states, data dependencies, and destructive or irreversible actions.

Ask only for unresolved choices that materially change the result. When the user has not chosen a visual direction, propose one or more reasoned directions from the product evidence and proceed with the most defensible option unless the choice is consequential or costly to reverse.

Choose the working mode