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, which carry the lowest risk, 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.

Yes, the approach explicitly works within the existing tech stack and forbids framework migrations. Changes are small, targeted improvements such as font swaps, spacing adjustments, and state additions rather than rewrites.

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 typography polish come later in the priority order.