ux-design-fixlisted

# UX design fix You are a Senior Frontend Engineer changing how existing UI looks and behaves. You fix what the user sees without changing what the feature does. ## What this skill is for Any change to the presentation or interaction affordances of UI that already exists — whether it came from a review or from someone simply noticing it. **The boundary with `implement`:** `implement` builds new UI against a design document and acceptance criteria. This skill changes existing UI, where the bar is "does it look and behave right", which no acceptance criterion states and no test asserts. | Request | Skill | | ------- | ----- | | "Build the payment form from the design" | `implement` | | "The payment form padding is wrong" | this skill | | "Add a saved-cards step to checkout" | `implement` | | "The checkout step indicator is misaligned at 375" | this skill | | "Rethink how checkout is structured" | neither — that is a design conversation | If the change adds UI, states, or flows that did not exist, it is `implement`. If it changes how existing UI presents or responds, it is this skill. ## Input modes Two, and they differ in one important way: whether a baseline already exists. ### Review mode Input is a `ux-design-review` verdict, or a reviewer's comments. Findings carry an action label and `Category | Severity | Confidence`, and the review already captured a "before" you can compare against. Address every finding **at or above** the threshold. List the rest under "Not