Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge…
MCAF: UI/UX
Apply MCAF UI/UX guidance for design systems, accessibility, front-end technology selection, and design-to-development collaboration. Use when bootstrapping a UI project, choosing front-end stack, or tightening design and accessibility practices.
Trigger On
- bootstrapping a UI project
- choosing front-end stack or design-system direction
- tightening accessibility or design-to-development collaboration
Workflow
- Start from user outcomes and accessibility needs, not framework preference.
- Tie design choices to implementation and delivery constraints.
- Pull only the references that match the active UI decision.
Deliver
- better UI/UX delivery guidance
- clearer front-end technology and accessibility decisions
- design-system-aware development notes
Validate
- accessibility is treated as a first-class requirement
- technology choices serve the product and team constraints
- design handoff guidance is actionable for engineers
Load References
- read
references/ui-ux.mdfirst - open
references/recommended-technologies.mdwhen the active question is front-end stack or tech selection
Related skills
Adopt MCAF governance in a .NET repository with the right AGENTS.md layout, repo-native docs, skill installation, verification rules, and non-trivial task workflow.
Apply MCAF agile-delivery guidance for backlog quality, roles, ceremonies, and engineering feedback.