frontend-implementation

name	frontend-implementation
description	Use to implement approved UI, UX, pages, components, dashboards or frontend flows. Requires an approved DESIGN.md or explicit design direction. Do not use to invent the product design during implementation.

Frontend Implementation

Mandatory authority:

docs/standards/design-intelligence.md
→ approved DESIGN.md
→ project brand and component system

1. Preserve approved behaviour and existing stack.
2. Implement semantic structure, hierarchy, navigation and action priority.
3. Cover loading, empty, no-results, partial, stale, error, permission, success, destructive confirmation and degraded states.
4. Use accessible labels, keyboard behaviour, visible focus and reduced motion.
5. Use realistic data density, long text, zero values and large record counts.
6. Reuse maintained components before hand-rolling mature controls.
7. Keep motion purposeful and performant.
8. Verify responsiveness, accessibility, interaction and browser behaviour.

Do not let an external design specialist override the design constitution.