redesign-existing-projects

Follow a scan-diagnose-fix sequence: read the codebase to identify the framework and styling method, audit for generic patterns, then apply targeted upgrades to the existing stack. Test after every change and keep improvements small and reviewable rather than rewriting from scratch.

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

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

Start with a font swap for the biggest instant improvement, then clean up the color palette, add hover and active states, fix layout and spacing, replace generic components, add loading and error states, and finish with typography scale polish.

Incremental redesign is not suitable when the project needs a full framework migration or a complete rebrand with new information architecture. This approach deliberately avoids rewrites and works within the existing tech stack.