UI implementation with explicit state coverage and accessibility as a first-class gate.

Propose Before Building

When frontend scope is ambiguous: propose an ASCII sketch or block diagram showing layout, key interactions, and UI states before implementation. Ask one clarifying question if critical UX intent is unclear.

For distinctive visual craft (typography, color, motion, composition), use the frontend-design skill.

State Coverage

Every UI component MUST account for these states where applicable:

Loading — skeleton or spinner, not blank screen
Error — actionable message, not raw error
Empty — guidance or call-to-action, not blank
Responsive — functional across viewport sizes