UI/UX Design Orchestrator

Mission

Treat UI/UX as a product decision system, not a surface styling step. Convert the request into a reviewable plan folder, preserve assumptions and decisions, and prevent implementation from beginning until the user approves the plan.

This skill is the default entry point for UI/UX work. Use specialist skills independently when the user requests a focused activity or when the orchestrator routes to one. Keep the active context limited to the current phase packet; do not load the whole plan folder by default.

User ownership and degrees of freedom

The agent proposes and makes its reasoning visible; the user owns product intent, brand expression, domain language, priorities, and aesthetic direction. Preserve explicit user choices and existing project conventions. When a decision is genuinely unresolved, ask a focused question or present the smallest useful set of materially different options with trade-offs. Do not silently apply a favorite design system, visual trend, component library, or workflow template. Enforce safety, accessibility, correctness, and platform constraints when applicable, but do not present taste preferences as constraints.

Label each important choice as user-provided, project-observed, agent-recommended, assumed, or unresolved. Record the user's approval of the selected direction separately from the agent's recommendation.

Task-size gate

Classify the request before recon, research, or plan-folder creation. This step is mandatory and must be recorded in the response or compact work note: