What problem does it solve? Frontend work drifts when an AI invents its own stack, ignores the design system, or hardcodes API shapes that disagree with the backend. This Skill constrains UI implementation to the project's declared stack, design system vocabulary, and API contract so frontend and backend stay aligned. ## Core Features & Use Cases - Stack-Adaptive UI Implementation: Reads stack from .archflow/project-settings.yaml and builds web, mobile, or DSL-converted interfaces in exactly the frameworks the project declares, asking rather than guessing when fields are unset. - Design System Enforcement: Maps every component to the vocabulary in .archflow/design-system.yaml, staying on its scales and rules and logging genuine gaps instead of inventing components. - API Contract Compliance: Types every API integration against the contract's response schemas, treats the contract as the single source of truth, and stops to report missing endpoints rather than fabricating shapes. - Use Case: During Archflow Phase 3, delegate a user story to this role to implement screens with loading, empty, error, and success states, then hand the story to qa-engineer by setting its status to review. ## Quick Start Ask the agent to implement the next ready story's UI for the current release, following the project design system and API contract.
