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 fixes 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, Lucide icons, and generic box shadows. Replacing these with considered typography, a single accent color, and asymmetric layouts removes the generic look.

Yes, it works with Tailwind, vanilla CSS, styled-components, and other styling methods. For Tailwind projects, check whether the project uses v3 or v4 before modifying the config, and keep all changes within the existing styling system.

Yes, the approach explicitly works with the existing tech stack and forbids framework migrations or rewrites. Changes are small, targeted, and reviewable, improving typography, color, layout, and states within the current architecture.

Font swaps deliver the biggest instant improvement at the lowest risk, followed by color palette cleanup and adding hover and active states. Layout restructuring, component replacement, and loading or empty states come later in the priority order.