design-ui

UI design tasks are orchestrated by routing surface, motion, layout, typography, color, and accessibility briefs through a classification layer. This enforces workflow guardrails and delegates the actual design move to impeccable subcommands, preventing mix-ups with logic or copy tasks.

Long-running UI polish workflows support stateful recovery by persisting checkpoints. This allows the design orchestration process to resume after an interruption without losing progress, ensuring the staged validation and audit loops complete successfully.

Design intents are classified before execution by detecting whether a task brief belongs to design, development, or copy. This intent classification ensures design briefs are processed through a disciplined orchestration layer before any actual writing or design moves begin.

Lane misrouting is handled through workflow guardrails that enforce parent-directory checks and register conflict handling. If a UI typography or color change is misrouted, the orchestration layer applies audit-driven loops with capped retries to correct the path.

Multi-step accessibility audits are supported through staged validation and controlled invocation of impeccable subcommands. The orchestration layer applies audit loops to ensure accessibility changes meet required standards before completing the workflow phase.

A UI design brief returns a structured design report instead of a direct code edit because the orchestration layer separates design moves from implementation. This ensures design intents are validated and audited through impeccable subcommands before any final action is taken.