component-design
Component design: boundaries, hover/focus/active/disabled/loading/success/error states, forms, navigation, hierarchy.
SKILL.mdskills/frontend/component-design/SKILL.md
GitHubcomponent-design
Every component owns its states: default plus hover/focus/active/disabled/loading/success/error/empty.
Inspection
Inventory existing primitives and similar components; list required states (all eight) and where data/validation comes from.
Decision rules
Reuse primitive → compose → wrap → extend → build-local, in that order; forms get labels/validation/errors from the start; navigation carries focus management.
Activate when
- Creating or changing UI components, forms, navigation elements, or hierarchies.
Do NOT activate for
- Library selection (see ui-libraries); system tokens (see design-systems).
Procedure
- Boundary: one responsibility, explicit props API, composition over configuration sprawl; reuse existing primitives first (see ui-libraries).
- States: implement and visually verify every state (loading skeletons reserve space; errors guide recovery; empty states teach).
- Forms: labeled inputs, inline validation, error announcements, sensible defaults, keyboard-complete flows.
- Navigation/hierarchy: consistent patterns, focus management on route/step change, deep-linkable where applicable.
- Verify: state matrix rendered, keyboard + screen-reader pass (see accessibility), ui-verification probes where available.
Failure modes
One-off components duplicating primitives; missing empty/error states; uncontrolled inputs without validation; focus lost on route change.
Escalation
Library choice → frontend/ui-libraries; system tokens → frontend/design-systems.