taste-skill-redesign-skill

Audit the design for common fingerprints like Inter font everywhere, purple-blue gradients, three equal card columns, and missing hover states. Then apply targeted fixes: swap fonts, clean the color palette, add interaction states, and restructure layouts with asymmetry and proper spacing.

Work with the existing tech stack instead of migrating frameworks, and make small targeted improvements rather than rewrites. Test after every change, check the dependency file before importing libraries, and follow a fix priority order starting with low-risk font and color changes.

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, since configuration syntax differs between versions.

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

Avoid incremental upgrades when the project has fundamental structural problems, an unmaintainable codebase, or requires a complete brand overhaul. In those cases a full rewrite or a new design system may be more appropriate than targeted fixes.