hashgraph-online Uizze UI Design
Work from the product
Read the brief, existing UI, components, tokens, and constraints before designing. They always outrank this skill. Keep familiar interaction conventions and make the product's own objects, workflow, and priorities visually clear. Do not add novelty for its own sake.
Load one playbook
Choose at most one file for the current request:
- New interface or major redesign:
reference/new-work.md - Product or dashboard work:
reference/operate.md - Refinement and polish:
reference/polish.md - Simplification or distillation:
reference/distill.md - Explicit audit:
reference/audit.md - Native iOS work:
reference/ios.md
Do not load a second playbook. Apply judgment rather than treating its examples as a checklist.
Optional Uizze evidence
Read references/uizze-reference-policy.md before using the paid MCP. It exposes exactly find_ui_references and find_ui_materials. Use them only when a concrete unresolved visual or material question would benefit from evidence. If they return nothing, continue silently.
Finish
Complete the requested scope. When the environment supports it, render and inspect once. Fix observable breakage such as clipping, overlap, distorted media, inaccessible controls, or inert interactions. Keep the handoff concise.