bencium-controlled-ux-designer

Accessible UI decisions aligned with brand guidelines require a deliberate protocol evaluating color systems, typography, and layouts against WCAG AA standards. This skill enforces that protocol by asking for explicit confirmation before applying visual changes and presenting alternatives with trade-offs.

Avoiding generic SaaS aesthetics involves presenting multiple distinct design directions with clear rationale. This skill provides a decision protocol that proposes alternative visual options with trade-offs, ensuring web components and dashboards maintain standout, brand-coherent interfaces.

Yes, you can get UI design guidance requiring approval through an ask-first protocol. This skill mandates explicit user confirmation before applying styling, layout, or typography changes, ensuring collaborative and deliberate design decisions across web applications.

Yes, this design approach supports WCAG AA accessibility standards for web apps. It encodes foundational principles enforcing accessibility compliance, clear typographic hierarchy, and coherent design language across landing pages, dashboards, and component design tasks.

Choosing typography and color system options for a dashboard requires comparing distinct visual directions with explicit trade-offs. This skill presents multiple design alternatives with rationale, allowing evaluation of accessibility and brand alignment before confirming a decision.

You should not use an ask-first UI design protocol when you need rapid, autonomous styling generation without collaborative review. This skill is built for deliberate, accessibility-conscious workflows requiring explicit confirmation, making it unsuitable for fully automated UI generation tasks.