Phase Driven UI Refinement

Phase-Driven UI Refinement

Follow a strict phase workflow for UI improvement work.

Use This Skill When

• The user wants work split into phases.
• The user wants checklist-driven execution.
• The user explicitly wants items handled in order.
• The user wants a whole phase finished before moving on.

Core Rule

Within a phase:

1. Take the next checklist item only.
2. Implement it.
3. Verify it yourself.
4. Refine if needed.
5. Mark checklist status.
6. Move to the next item.

Only after all items in the phase are done:

• report the phase complete
• then ask whether to move to the next phase

Execution Rules

• Never jump ahead to another phase.
• Never mix unfinished items across phases.
• Keep the checklist updated as part of the work, not afterward.
• If the user changes priorities, reorder the checklist first, then continue.
• If the user says to stop at a phase boundary, stop cleanly and record the current state.

Recommended Checklist Statuses

• 미시작
• 진행중
• 완료
• 보류

Verification Standard

After each item:

• run the most relevant local verification
• inspect the result directly when possible
• do not claim completion without checking the changed behavior

For UI work, verification can include:

• lint
• local run
• Playwright checks
• route inspection
• screenshot or DOM confirmation