reskinlisted

# reskin — redesign the interface Design the thing **again, from a blank canvas**; **render it**; **score it**; **fight it** against the current design; repeat until a fresh attempt stops winning. Third sibling of **rewrite** (rewrite the code) and **refactor** (improve it in place). This one judges *what it looks like and how it reads*, and it is ruthless about the boring things — edges that line up, one spacing scale, sizes that mean something, contrast you can actually read. **Load the matching design skill first**, if one is available: `frontend-design` for web UI, `dataviz` for anything with a chart in it, `artifact-design` for a published page. This skill is the tournament harness; those carry the craft. --- ## 0. Pick the target and pin the content If the user passed an argument, that is the target (`/reskin the settings panel`). If not, ask **one question**: which screen, panel or component. Then pin down three things — all frozen for the whole run: 1. **The job.** What the user is trying to do on this surface, and what must be seen first, second, third. Design without a stated reading order is just decoration. 2. **The content set.** Real strings, real numbers, real counts — *plus a stress case*: the longest label, the empty state, the biggest number, the 40-item list. Every round is judged on the same content, stress case included. A design that only works on "Lorem ipsum" is not a design. 3. **The constraints.** Viewport(s) or window size, existing