redesign-existing-projects

Scan the codebase to identify the framework and styling method, run a structured design audit covering typography, color, layout, and states, then apply targeted fixes in priority order. Start with a font swap and palette cleanup for the highest impact at the lowest risk.

Replace default fonts like Inter with distinctive options such as Geist or Outfit, remove purple-blue gradients, avoid three equal card columns, and add hover, loading, empty, and error states. Use one desaturated accent color and consistent gray tints.

Yes, it works with Tailwind, vanilla CSS, styled-components, and other styling methods. Check the Tailwind version (v3 vs v4) before modifying config, and keep all changes within the project's existing styling system.

This approach does not cover framework migrations, information-architecture changes, or product-scope expansion. It preserves existing behavior, routing, and data flows, so structural UX problems requiring new architecture need a different effort.

Using height: 100vh causes layout jumping on iOS Safari because the viewport height changes with the browser chrome. Replace it with min-height: 100dvh, which accounts for dynamic viewport sizing on mobile browsers.