Refactor UI

Make an existing screen easier to understand and work through. Optimize for the user's next decision, then refine the visual details. Use the app's established design language and carry accepted decisions forward across iterations.

Enter at the current stage

Read the recent conversation before starting a new design process.

• Critique or discussion: inspect the screen and relevant behavior, explain the problem, and propose concrete changes. Keep this stage read-only when requested.
• Approved direction: “approved,” “do it,” or “implement it” continues the agreed work. Do not restart the questionnaire or ask for the same approval again.
• Specific correction: implement a clear, authorized annotation such as “move this next to the name” or “remove this label.” Scale explanation and checks to the change.
• Broad improvement: infer the job, roles, constraints, and reference from the conversation and code. Ask only about unresolved decisions that materially change scope or behavior. Continue independent investigation while waiting.

If invoked without a fresh target, use the active screen and current task when they identify the target. If neither does, ask which screen to work on. Do not infer permission for a new refactor solely from an open browser tab.

Establish the job and the evidence

Privately formulate: This person needs to use these inputs to make this decision and reach this outcome. Establish who owns the next step when the workflow involves several people or AI.