redesign-existing-projects

Scan the codebase to identify the framework and styling method, diagnose design issues with a structured audit, then apply targeted fixes in priority order: font swap, color cleanup, hover states, layout, components, states, and polish. Test after every change and keep improvements small and reviewable.

Replace default fonts like Inter with characterful options such as Geist or Outfit, remove purple-blue AI gradients, break up three-column card layouts, and add missing hover, loading, empty, and error states. The audit checklist covers typography, color, layout, and component cliches.

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, and always verify dependencies exist in package.json before importing anything new.

The most common mistakes are Inter everywhere, pure black backgrounds, oversaturated accents, three equal card columns, missing hover and focus states, Lucide icons, lorem ipsum, and cliche copy like "Elevate" or "Seamless". Each has a specific replacement technique in the audit.

Avoid in-place upgrades when the project requires a full framework migration or a ground-up rebrand with new information architecture. This approach intentionally works within the existing stack and favors small, targeted improvements over big rewrites.