redesign-existing-projects

Audit the design for common AI fingerprints like Inter font, purple-blue gradients, three equal card columns, and missing hover states. Then apply targeted fixes: swap fonts, clean up the color palette, add interaction states, and restructure generic layouts.

Work with the existing tech stack instead of rewriting from scratch. Apply small, reviewable changes in priority order—fonts first, then colors, states, and layout—and test after every change to confirm nothing breaks.

Yes, it works with Tailwind, vanilla CSS, styled-components, and other styling methods. For Tailwind projects, check whether the project uses v3 or v4 before modifying the config, since configuration formats differ.

The most common patterns are Inter or browser-default fonts, purple-blue AI gradients, three equal feature cards, pure black backgrounds, Lucide icons, generic box shadows, and missing hover, loading, empty, and error states.

Avoid it when a project needs a full rebrand or architectural migration rather than visual polish, since the method explicitly avoids framework migrations and large rewrites. It is designed for incremental upgrades to working projects.