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 upgrades in priority order. Test after every change and keep improvements small and reviewable rather than rewriting from scratch.

Common AI design fingerprints include Inter font everywhere, purple-blue gradients, three equal card columns, pure black backgrounds, generic box-shadows, Lucide icons, and cliche copy like "Elevate" or "Seamless". The audit checklist covers each category with specific replacements.

Yes, it works with Tailwind, vanilla CSS, styled-components, and other styling methods. Before modifying Tailwind config, check whether the project uses v3 or v4, since configuration syntax differs between versions.

Apply fixes in this priority order: font swap first, then color palette cleanup, hover and active states, layout and spacing, generic component replacement, loading/empty/error states, and finally typography scale polish. This sequence delivers the biggest visual improvement with the lowest risk.

Avoid it when a project needs a full framework migration or ground-up rebuild, since the skill explicitly works within the existing tech stack. It is designed for targeted visual upgrades, not architectural changes or new feature development.