interface-redesign
Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished,…
它会碰到什么
这一栏是扫描器报的事实，不是结论。命中多不等于有毒（安全工具、规则库、示例脚本本来就会包含危险写法），命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系，需要你自己看。
技能内容
Interface redesign
Most interfaces do not need rebuilding. They need a dozen specific things fixed, in the right order.
Audit first
Go through the real product, on a real device, doing a real task. Record what you find in these
categories — the order is the priority order:
- Structural — unclear primary action, competing focal points, navigation that does not match
the mental model. These are the only ones worth a rebuild.
- Systemic — inconsistent spacing, more type sizes than a scale would allow, palette drift,
components that exist in variants. High impact, mechanical to fix.
- Craft — weak hierarchy, poor contrast, unfinished states, cramped density.
- Cosmetic — dated shadows, default border radii, stock illustration.
The generic-AI-product tells
These are the specific things that make a product read as unconsidered. They are worth naming
because they are all cheap to fix:
- Default framework styling left in place — the untouched button, the starter-template card.
- One accent color used for every emphasis, so nothing is emphasized.
- Uniform spacing everywhere, so nothing groups.
- Centered everything, including body copy.
- Emoji standing in for iconography.
- Gradients on surfaces that carry no meaning.
- Empty and error states that were never designed.
Sequencing
Fix in this order, because each makes the next easier to see:
- Tokens — spacing scale, type scale, palette. This alone resolves most systemic findings.
- Hierarchy on the two or three highest-traffic screens.
- States: empty, loading, error, overflow.
- Component consolidation.
- Cosmetic pass.
Restyle or rebuild
Rebuild only when the structure is wrong — when the information architecture does not match how
people work. Everything else is a restyle, and a restyle that ships beats a rebuild that stalls.
Never
- Restyle a screen whose problem is structural. New paint on a broken flow buys nothing.
- Change navigation and visual language in the same release. When something breaks you will not know which one did it.
- Remove a path because it looks unused without checking who uses it and what they do next.
- Ship a redesign with no way back. Keep the old path reachable until the new one is proven.
Return contract
Findings by category with severity, the sequenced plan, what you would do first if only one day were
available, and what you deliberately are not touching.
想直接用这个技能？
本站把开放许可（MIT / Apache 等）的技能按仓库打包整理到网盘，点一下转存到你自己的网盘，不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接，不打包。