Redesign

Use this skill when the user points at a piece of UI and wants a better redesign conversation before code. The job is to turn a vague "make this better" into:

1. what the surface appears to be trying to help someone do
2. what the current design is making harder than it should be
3. which questions actually change the redesign direction
4. a concrete redesign brief or implementation handoff

Default behavior is critique, questions, and direction. Do not edit code, emit patches, or produce implementation unless the user explicitly approves a follow-up implementation step.

Relationship to adjacent UI skills

• redesign owns the first pass: pointed-at UI, diagnosis, targeted questions, and redesign direction.
• product-design owns deeper product critique plus an approved implementation plan for an existing product experience.
• calm-ui owns React, Next.js, TypeScript, and shadcn visual/interface execution after direction is clear.
• ui-principles owns framework-agnostic visual/interface execution after direction is clear.
• design-loop owns full product redesign systems with /design.md, surface briefs, screenshots, critiques, and human gates.