anvil-ui-redesign

Audit the design for common fingerprints like Inter fonts, purple-blue gradients, three-card feature rows, and missing hover states. Then apply targeted fixes in priority order: font swap, color palette cleanup, interaction states, layout corrections, and component replacements.

Work with the existing tech stack instead of rewriting from scratch. Scan the codebase first to identify the framework and styling method, apply small targeted improvements, and test after every change to keep the work reviewable.

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 formats differ between versions.

The most common patterns are purple-blue AI gradients, three equal card columns, Lucide or Feather icons, generic box-shadows, pure black backgrounds, and copy cliches like Elevate or Seamless. Replacing these with considered alternatives removes the generated look.

Avoid it when the project needs a full rebrand or architectural change rather than visual polish, since the rules prohibit framework migrations and large rewrites. It is designed for incremental, reviewable improvements to a working product.