MCAF: UI/UX
Read root/local AGENTS.md, supplied designs, existing components/tokens, target devices, and the user flows involved.
Workflow
- Preserve the requested design and accepted product behavior. Use the established stack and design system; new architecture or dependencies need approval.
- Make interactions, loading/empty/error states, keyboard navigation, semantics, labels, contrast, and responsive behavior explicit where the flow needs them.
- Connect design choices to implementable components and acceptance criteria. Avoid ad hoc variants or speculative navigation/product changes.
- Review the complete affected UI and tests before verification. For visible changes, inspect rendered behavior at the relevant viewports; source/CSS checks do not prove layout.
- Report the UI or policy changes, rendered evidence where applicable, and remaining usability/accessibility gaps.
References
- For design handoff and component consistency: UI engineering.
- Only when choosing technology: selection criteria; verify current support from official sources.