Routing
- For a new interface, redesign, or meaningful flow change, inspect the existing experience and use $interview for material product or design
decisions that evidence cannot resolve.
- For a review, audit, or small scoped change, inspect the existing interface and proceed directly.
- Use $workshop when abstract product framing or strategic options remain unresolved.
Design workflow
- Inspect the user's job, complete journey, platform conventions, design system, realistic content, and relevant states.
- When options are requested, make them meaningfully different in workflow, hierarchy, density, states, responsiveness, or interaction; cosmetic
variations do not count. Keep content and states consistent so the experience is comparable, then recommend one direction with its trade-offs.
- Settle the UX before refining UI styling and polish unless new evidence changes an earlier decision. Implement the requested or selected direction
only when an editable site, artifact, or code environment is available; otherwise deliver the requested review, design direction, mockup, or
implementation brief without claiming the product changed.
- After each material revision, summarize the change and any remaining decision.
Design-system boundary
- Follow the established design system. Before adding a component, token, pattern, or visual language, explain the unmet need and get approval.
- When the system cannot support needed behavior, propose a system-level extension instead of a poor interaction or one-off substitute.
Review protocol
Report concrete issues in descending user impact:
- Blocked, unsafe, destructive, or unrecoverable flows
- Missing states, broken responsiveness, or inaccessible interaction
- Unclear hierarchy, navigation, wording, or action priority
- Missing, delayed, misleading, or excessive feedback
- Inconsistent visual or interaction language
- Polish opportunities that improve trust, personality, or delight
For each issue, identify the affected user goal, current behavior, recommended behavior, and reason. Distinguish evidence, inference, and aesthetic
preference.
Completion standard
After implementation, inspect the rendered UX and UI and improve it until optimal. Do not call implemented work complete until the primary task,
relevant failure and recovery paths, accessibility behavior, realistic content, and relevant viewport and input modes work as one coherent experience.
For advisory work, complete the requested review, option set, mockup, or implementation brief and identify any behavior that still needs validation in
a rendered product.
User preferences
- Begin with the user's job and complete journey. Prefer one clear primary path, immediate common actions, and progressively disclosed capability.
- Favor calm, rich, professional, distinctive minimalism: hierarchy, balanced spacing, restrained color, and subtle depth instead of visual excess.
- Keep controls contextual and interactions consistent; make motion smooth, symmetric, and purposeful. Iterate from rendered evidence and finish an
approved direction faithfully.
- Prefer icons paired with text labels.
1---2name: ux-ui3description: UX/UI discovery, implementation, options, and review.4---56## Routing78- For a new interface, redesign, or meaningful flow change, inspect the existing experience and use $interview for material product or design9 decisions that evidence cannot resolve.10- For a review, audit, or small scoped change, inspect the existing interface and proceed directly.11- Use $workshop when abstract product framing or strategic options remain unresolved.1213## Design workflow14151. Inspect the user's job, complete journey, platform conventions, design system, realistic content, and relevant states.162. When options are requested, make them meaningfully different in workflow, hierarchy, density, states, responsiveness, or interaction; cosmetic17 variations do not count. Keep content and states consistent so the experience is comparable, then recommend one direction with its trade-offs.183. Settle the UX before refining UI styling and polish unless new evidence changes an earlier decision. Implement the requested or selected direction19 only when an editable site, artifact, or code environment is available; otherwise deliver the requested review, design direction, mockup, or20 implementation brief without claiming the product changed.214. After each material revision, summarize the change and any remaining decision.2223## Design-system boundary2425- Follow the established design system. Before adding a component, token, pattern, or visual language, explain the unmet need and get approval.26- When the system cannot support needed behavior, propose a system-level extension instead of a poor interaction or one-off substitute.2728## Review protocol2930Report concrete issues in descending user impact:31321. Blocked, unsafe, destructive, or unrecoverable flows332. Missing states, broken responsiveness, or inaccessible interaction343. Unclear hierarchy, navigation, wording, or action priority354. Missing, delayed, misleading, or excessive feedback365. Inconsistent visual or interaction language376. Polish opportunities that improve trust, personality, or delight3839For each issue, identify the affected user goal, current behavior, recommended behavior, and reason. Distinguish evidence, inference, and aesthetic40preference.4142## Completion standard4344After implementation, inspect the rendered UX and UI and improve it until optimal. Do not call implemented work complete until the primary task,45relevant failure and recovery paths, accessibility behavior, realistic content, and relevant viewport and input modes work as one coherent experience.46For advisory work, complete the requested review, option set, mockup, or implementation brief and identify any behavior that still needs validation in47a rendered product.4849## User preferences5051- Begin with the user's job and complete journey. Prefer one clear primary path, immediate common actions, and progressively disclosed capability.52- Favor calm, rich, professional, distinctive minimalism: hierarchy, balanced spacing, restrained color, and subtle depth instead of visual excess.53- Keep controls contextual and interactions consistent; make motion smooth, symmetric, and purposeful. Iterate from rendered evidence and finish an54 approved direction faithfully.55- Prefer icons paired with text labels.
MuhammedAlkhudiry