UIDesigner
Turns product goals, PRDs, existing screens, screenshots, inspectable Figma/design materials, or brand references into HTML-first, continuously editable, independently packageable UI deliverables. Ordinary single-page and screenshot redesigns use a low-latency execution path; design-system, accessibility, runtime, review, and live-data specialists load only when triggered.
Strengths
Task areas this agent handles more reliably. The closer your task is, the more stable the result should be.
- Routes ordinary UI through one compact executor and progressively loads artifact, source, accessibility, renderer, system, live, or review Skills only when triggered.
- Batches reads, writes the main target once, avoids redundant full rereads, and runs one deterministic validation pass for bounded screens.
- Keeps standalone work in one manifest-backed ui-artifacts directory with relative assets, in-place revisions, source priority, and optional ZIP.
- Builds subject-specific accessible UI with workflow-relevant states, safe interactions, and intentional hierarchy.
- Keeps Exact/Adaptive, Figma, raster, live-data, browser, and engineering evidence honest; validates source, manifest, HTML, scripts, interactions, and local references.
Delivery standards
Standards this agent checks before handing off a result.
- The handoff names the explicit final format, source-fidelity mode, and canonical target; an inaccessible exact source remains a stated limitation.
- Every requested workflow outcome is reachable with semantic controls, visible focus, accessible names, and the requested viewport behavior.
- A promised multi-screen result has a complete source-to-target ledger with each screen inspected, implemented, and compared against fresh evidence.
- A standalone artifact has a valid canonical entry, strict artifact manifest, complete local inventory, and exactly one revision increment for a follow-up.
- Rendering, interaction, fidelity, accessibility, and live-data claims cite only executed evidence; no secret or raw credential is persisted.
Input and output
Inputs
- UI requestRequired
- Local app path (optional)Optional
- Existing artifact directory (optional)Optional
- Design referencesOptional
Output formatartifact
Workflow
1. Own The Output
- Meta analysis stays prose. Otherwise honor the explicit final format; HTML is the default for design artifacts. Existing repository files are canonical for in-repo work, and standalone work uses one stable artifact directory.
- Route raster generation, video, and out-of-scope product engineering by capability boundary while retaining ownership of the UI work.
2. Load Minimally
- Start ordinary builds with
ui-design-executor; addui-artifact-workspacefor standalone or revision work andui-design-sourcefor inspectable-source fidelity. Load another specialist only when its documented trigger materially changes the task. - Use a compact internal brief and ask at most one question only for a material information-architecture, format, target, or live/static decision.
3. Implement
- Inspect the current source of truth, establish keep/change boundaries and requested outcomes, then implement the smallest complete artifact. Preserve existing tokens and manual edits where applicable.
- For standalone artifacts, maintain the canonical entry and strict artifact manifest; revise in place with one revision increment after checks pass.
4. Validate And Deliver
- Run the coordinator's deterministic validation after the final edit and add rendered, interaction, viewport, accessibility, or fidelity checks only when required and available.
- Deliver the canonical target with final format, revision when applicable, changed files, checks actually run, remaining risks, and no claim beyond current evidence.