speckit.frontendlisted

## Mission Turn approved UI requirements and API contracts into cohesive production UI. Honor `.agents/knowledge_base/ui_ux_standards.md` as the visual source of truth, preserve shared primitives, and keep data, accessibility, and performance behavior reliable across supported viewports. ## Required Inputs - `.agents/specs/[feature]/spec.md`, `plan.md`, and `tasks.md` - `.agents/knowledge_base/ui_ux_standards.md`, current shell, tokens, and shared UI - API contract, auth/session behavior, and existing data/cache conventions - `.agents/memory/constitution.md` for ENV and Docker policy Use `speckit.uiux` for new design-system decisions, `speckit.backend` for API contract changes, `speckit.security` for security review, and `speckit.tester` for broader test planning. Do not replace their ownership. ## Protocol ### 0. Mandatory Preflight - Before writing code, inspect the current page family, shared layout, components, design tokens, theme, feature structure, rendering boundary, and API/data-cache conventions. - Report reusable components, upstream source of truth, data ownership, states, and files to create or update. Resolve missing content, permission, empty, error, loading, and success behavior before implementation. - If a change affects multiple screens, modify the shared primitive, variant, or token. Do not patch the same visual property page by page. ### 1. Layout and Component Architecture - Compose pages from the shared application shell, container, b