Skip to content
Flows
Make UI Less Generic
Debugging60-90 minutes
0/5 steps0%

Step 1 of 5

Audit the generic tells

Name exactly what makes the app look AI-default.

Prompt capsule

Audit the UI and list every 'AI slop' tell with its location: default system/Inter-only fonts, purple/pink or rainbow gradients, emoji used as icons, identical rounded-card grids, default shadcn/bootstrap look, placeholder copy, inconsistent spacing, missing hover/focus states. Rate the overall genericness 1-10 with justification and screenshot references.

Paste into Claude · Complete implementation prompt with explicit requirements

Expected after this step

A specific inventory of generic patterns with locations.

Should not happen

  • Restyling one page while others keep the old look
  • Swapping one gradient for another equally generic one
  • Inconsistent spacing that keeps the cheap feel
  • Breaking layouts while changing styles

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Do not continue if…

  • !Restyling one page while others keep the old look
  • !Swapping one gradient for another equally generic one
  • !Inconsistent spacing that keeps the cheap feel
  • !Breaking layouts while changing styles

If the AI messes this up

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

The audit is vague ('looks generic'). Re-audit tell by tell: name the exact fonts in use, list every gradient, and locate each emoji-icon and placeholder string.

Your notes for this step