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, which carry the lowest risk, and test after every change.

Common 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, a single desaturated accent, 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 workflow explicitly forbids framework migrations and rewrites from scratch. It improves what exists by working within the current stack, keeping changes small, focused, and reviewable.

Apply fixes in this priority order: font swap first, then color palette cleanup, hover and active states, layout and spacing, generic component replacement, loading and error states, and finally typography scale polish.