redesign-existing-projects

Scan the codebase to identify the framework and styling method, diagnose generic patterns with a structured audit, then apply targeted fixes in priority order: font swap, color cleanup, interaction states, layout, components, and finally polish. Test after every change and keep edits small and reviewable.

Replace default fonts like Inter with characterful options, remove purple-blue AI gradients, break up three-card feature rows with asymmetric grids, and add missing hover, loading, empty, and error states. The audit checklist covers typography, color, layout, content, and iconography.

Yes, it works with Tailwind, vanilla CSS, styled-components, or any styling method. Before modifying config, check whether the project uses Tailwind v3 or v4, and never migrate frameworks or styling libraries during the redesign.

Common fingerprints include Inter everywhere, oversaturated accent colors, pure black backgrounds, three equal card columns, generic box shadows, Lucide icons, pill-shaped badges, and copy cliches like "Elevate" or "Seamless". The audit lists fixes for each pattern.

Avoid it when the project needs a full rebrand or architectural rewrite rather than visual polish, since the rules prohibit framework migrations and large rewrites. It is designed for incremental, reviewable improvements on a working codebase.