Operate

• Make the current location, primary task, and next action obvious.
• Match information density to the work. Dense tables and compact controls are appropriate when users need them; decorative containers are not.
• Prefer standard navigation, forms, tables, tabs, menus, and dialogs over novel replacements.
• Use spacing and alignment for grouping before adding borders, cards, or backgrounds.
• Keep one component vocabulary across the surface.

States and behavior

• Cover the states the product can reach: loading, empty, error, success, disabled, selected, expanded, and recovery where relevant.
• Keep focus visible, controls labelled, contrast readable, and targets usable.
• Prevent overlays and menus from being clipped by scroll or overflow containers.
• Use quick motion only for state changes and feedback. Do not choreograph routine page loads.
• Make responsive changes structural: collapse navigation, reflow groups, and preserve access to important actions.

Finish

Use the interface at representative sizes. Fix the few observable issues that obstruct the task or break consistency. Do not redesign working areas outside the requested scope.