What problem does it solve? Teams often struggle to turn UI/UX goals into concrete engineering decisions, leading to inconsistent design systems, weak accessibility, and front-end stacks chosen by preference rather than product constraints. ## Core Features & Use Cases - Front-end technology selection: Evaluates stacks against accessibility support, design-system maturity, testability, SSR/SPA needs, and deployment constraints. - Accessibility-first guidance: Treats accessibility as a baseline quality attribute with explicit tokens, spacing, and interaction rules. - Design-to-development handoff: Produces actionable engineering notes that keep design-system rules consistent during implementation. - Use Case: When bootstrapping a new product UI, use this Skill to choose a front-end direction, document accessibility requirements, and define design handoff rules engineers can follow. ## Quick Start Ask the assistant to apply the MCAF UI/UX workflow to choose a front-end stack and document accessibility and design handoff guidance for your repository.