UI Design

Overview

Turn product facts, existing UI evidence, and explicitly scoped references into a versioned UI design package. Own design decisions and task-local assets only; route source edits to implement-frontend, runtime evidence to ops-browser or ops-client, and read-only implementation audits to audit-frontend.

Workflow

1. Read effective repository guidance and run git status --short before planning artifacts.
2. Identify product, audience, platform, primary user job, target surface, current component system, available states, data facts, and forbidden inventions.
3. Inspect the smallest useful set of current screenshots, routes, components, tokens, DTOs, and analogous surfaces. Say Not found or Not verified for missing evidence.
4. Select one primary mode: profile, task, reference, or evaluation. Supporting outputs may be included only when needed by that mode.
5. Assign each reference an explicit use and ignore list plus source and rights status. Never treat a reference as authorization to copy brand, content, or functionality.
6. Create one coherent visual direction: named palette, typography roles, layout concept, density, material, interaction tone, and one justified signature element. Preserve product truth over decoration.
7. Treat assets/ui-package.schema.json as the package contract, then produce or update the project profile, task brief, reference registry, design tokens, component map, evaluation, and manifest from assets/templates/.
8. Separate deterministic acceptance checks from visual or experience judgment. Apply hard blockers before weighted scoring.
9. Version every input and output in the manifest. Never overwrite the last accepted revision without preserving rollback.
10. Validate the package with scripts/validate_ui_artifacts.py, then hand off source work and runtime proof to their owning skills.