Agent skill · Yu-369
visual-redesign
Surgical aesthetic upgrade pipeline for existing React codebases. Takes ugly, functional code (Bootstrap defaults, generic Tailwind, amateur CSS) and transforms it to Awwwards-tier quality WITHOUT touching or breaking the underlying JavaScript logic - states, effects, API calls, event handlers, routing, and data flow are sacred and untouchable. Audits the existing code across 7 layers (tokens, typography, spacing, color, components, atmosphere, motion), classifies every element as Sacred (JS logic - do not touch) or Slop (visual cruft - upgrade), then executes precise CSS-only surgery layer by layer. The skill that turns a developer's "make this look better" into a controlled, non-destructive visual transformation.
What it needs
About 12k tokens when loaded.
What this skill does
Visual Redesign: Surgical Aesthetic Upgrade This skill fires when the user provides existing React/HTML/CSS code and asks to make it look better, upgrade the design, improve the aesthetics, make it premium, give it an Awwwards feel, or any variation of "this works but looks terrible." The user's code is FUNCTIONAL - it has working state, API calls, event handlers, and business logic. Your job is to upgrade the visual layer without breaking any of it. You are a surgeon, not a demolition crew. Cut precisely. Leave the patient alive. --- The Sacred Rule - Read First JavaScript logic is sacred. You do not touch it. Ever. This is the non-negotiable, unbreakable rule that governs every line of this skill: ⚠ Drift Warning: The #1 way AI "breaks the app" is by restructuring JSX to look cleaner and accidentally removing a conditional wrapper, moving a key prop, changing a ref assignment, or reordering children that depend on DOM position. NEVER restructure JSX for aesthetic reasons if the existing structure works. Add CSS to the existing structure. Do not reshape the structure to fit your CSS preferences. → The Gray Zone Some elements are both logic and style. Handle them with extreme care: Element Sacred or Slop? Rule --- --- --- className={isActive ? 'active' : ''} Both - logic is sacred, class names are slop Keep the ternary. Change only the class name values: className={isActive ? 'nav-link--active' : 'nav-link'} style={{ display: isOpen ? 'block' : 'none' }} Sacred - this is conditional visibility logic Do NOT replace with CSS classes. The inline style is driven by state. Leave it. Add your styles alongside it {items.map((item) => <Card key={item.id} ... />)} Sacred - the map, key, and data flow are logic Style the Card component's internals. Do not change the map structure or key assignment ref={containerRef} Sacred - ref assignments drive JS behavior Never remove, move, or rename refs aria- attributes Sacred - accessibility attributes are functional Never remove. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills Yu-369/visual-redesign