meisijiya-redesign-ui
version: 0.1.0
meisijiya-redesign-ui
Attribution. This skill is a meisijiya adaptation of Leonxlnx/taste-skill's
redesign-skill(install nameredesign-existing-projects), originally written by Leon Linnx and released under MIT License. The audit structure and fix-priority ladder are preserved; the skill has been rewritten to fit the meisijiya 6-section skill-anatomy format and the OMO collaboration model.
Overview
UI redesigns that work are not rewrites — they are targeted upgrades on top of what already ships. This skill enforces the scan → diagnose → fix sequence: identify the framework + styling system + current patterns, run a layered audit against a checklist of common AI-default and cheap-default tells, then apply fixes in a priority order that maximizes visual impact with minimum risk. The codebase stays in its existing framework and styling system; functionality does not break.
For brand-new designs with no existing UI to honor, use meisijiya-frontend-taste instead. This skill is built for code that already ships.
When to Use
Use when:
- The project already has UI (web / mobile / desktop) that ships or is about to ship
- The user wants the UI to look "premium", "expensive", "not obviously AI", "more like [Linear/Vercel/Apple/Notion]", "less generic"
- The codebase already has framework choices (React/Vue/Svelte) and styling choices (Tailwind/Styled Components/CSS modules) — we respect them
- The user describes symptoms ("looks templated", "AI purple gradient shows up", "honest about pricing needs work", "the FAQ accordion is awful") without asking for a full rewrite
- Major refactors that touch the styling system (token rename, theme change) — this is a redesign-without-feature-change