redesign-existing-projects

Follow a scan-diagnose-fix sequence: read the codebase to identify the framework and styling method, audit for generic design patterns, then apply targeted upgrades in priority order. Start with font swaps and color cleanup before touching layout, and test after every change.

Common AI design fingerprints include purple-blue gradients, Inter font everywhere, three equal card columns, pure black backgrounds, generic box shadows, and Lucide icons. Replace these with a single desaturated accent color, characterful fonts, asymmetric layouts, and tinted shadows.

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

Font swaps deliver the largest instant improvement with the lowest risk, followed by color palette cleanup and adding hover and active states. Layout restructuring, component replacement, and loading or empty states come after these foundational changes.

Avoid incremental redesign when the project needs a full rebrand, a framework migration, or a complete information architecture overhaul. This approach improves what exists rather than rewriting from scratch, so fundamentally broken structures may need a rebuild instead.