redesign-existing-projects

Scan the codebase to identify the framework and styling method, diagnose generic design patterns against an audit checklist, then apply targeted fixes in priority order. Start with font swaps and color cleanup, then interaction states, layout, and components, testing after each change.

Replace default fonts like Inter with characterful alternatives, remove purple-blue AI gradients, break up three-card layouts, and add missing hover, loading, empty, and error states. Also fix pure black backgrounds, oversaturated accents, and AI copywriting cliches like "Elevate" and "Seamless".

Yes, it works with Tailwind, vanilla CSS, styled-components, and other styling methods. When the project uses Tailwind, check whether it is v3 or v4 before modifying the config, and always work within the existing stack rather than migrating frameworks.

The most common patterns are Inter font everywhere, purple-blue gradients, three equal card columns, pure #000000 backgrounds, Lucide icons, generic box-shadows, and centered symmetrical layouts. Content cliches include "John Doe" names, Lorem Ipsum, and words like "Unleash" and "Next-Gen".

Avoid it when the project needs a full rebrand or architectural rebuild rather than visual polish, since the rules explicitly prohibit framework migrations and large rewrites. It is designed for incremental, reviewable improvements to a functioning product.