bencium-controlled-ux-designer

Enforce an Always Ask protocol for UI/UX design decisions.

383|53|Updated Oct 18, 2025

Search Tags:#typography #ui #accessibility #layout #ux #design-decision

Ready to run

npx skills add https://github.com/bencium/bencium-marketplace --skill bencium-controlled-ux-designer-bencium

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bencium-controlled-ux-designer
Source: https://github.com/bencium/bencium-marketplace/tree/main/bencium-controlled-ux-designer/skills/bencium-controlled-ux-designer
Command: npx skills add https://github.com/bencium/bencium-marketplace --skill bencium-controlled-ux-designer-bencium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers often face ambiguous briefs and inconsistent UI decisions; this skill enforces a proactive decision protocol to align teams on UX direction.

Core Features & Use Cases

Always Ask before proposing colors, typography, layout, or interactions to ensure alignment and accessibility.
Offers structured guidance for crafting unique, accessible interfaces that avoid generic SaaS aesthetics.
Use cases include web components, pages, or full applications, with emphasis on trade-offs and documentation.

Quick Start

Use this skill to guide a design decision by requesting input and presenting two viable alternatives before implementation.

Frequently Asked Questions about bencium-controlled-ux-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I make informed UX design decisions for ambiguous UI briefs?▼

To make informed UX design decisions for ambiguous briefs, use an Always Ask protocol that proactively requests input on typography, color, and layout before proposing solutions to ensure team alignment and accessibility.

What is the best way to document UI design trade-offs and alternatives?▼

Documenting UI design trade-offs requires presenting two viable alternatives with structured guidance that outlines accessible, human-centered options and guardrails before implementation to align team direction.

How do I avoid generic SaaS aesthetics when designing web components?▼

Avoid generic SaaS aesthetics when designing web components by enforcing a proactive design decision protocol that asks targeted questions to craft unique, accessible interfaces tailored to your specific application requirements.

Can I apply structured UX guidance to full web applications and pages?▼

Structured UX guidance applies to web components, pages, and full applications by enforcing an Always Ask protocol across typography, color, layout, and accessibility to satisfy decision documentation requirements.

Why should I ask questions before proposing UI typography and layout choices?▼

Asking questions before proposing UI typography and layout choices enforces a proactive decision protocol that prevents inconsistent design decisions, ensures accessibility, and aligns teams on the overall UX direction.