Design direction

Decide how the interface should look and feel before anyone writes components, and write it down so every screen comes out consistent. Direction comes from the brief and the users, never from the agent's defaults.

Phase 1: Read the constraints

• Existing system first. Look for tokens, a component library, a brand guide, a DESIGN.md or shipped screens. If one exists, extend it; this skill then only fills gaps.
• Established systems. Government, regulated, enterprise or platform-native products usually have an official system (for example a national government design system, or a platform's own guidelines). Use the official package over imitation. One system per project.
• Audience and context: who uses it, on which devices, how often, and what they need to trust. Accessibility-first, public-sector and children's audiences override aesthetic preference.
• Content: what the screens actually show. Dense data and long-form reading want different systems.

Phase 2: Choose a direction