ui-slop-score

> ***If your UI screams AI, your app is dead.*** # Score UI Slop Before It Ships Use UIZZE to turn a vague "this looks generated" reaction into a specific finish review. This free workflow is for rendered web or iOS UI—not source-code linting and not a claim about who made it.  ## Review Workflow 1. Inspect the real screen first: use a screenshot, running app, or rendered component. Do not score an imagined result from a prompt alone. 2. Name the screen's job, primary user action, and product-specific objects. If the nouns could be swapped into any SaaS app, call that out. 3. Check for the common tells: generic dashboard/card-grid structure, fake metrics, vague labels, decorative gradient/glass treatment, filler content, inert controls, missing loading/empty/error states, or a layout that ignores the local product system. 4. Give a **UI Slop Score** from 0–100, where 100 means the highest risk of looking interchangeable. Explain the two or three observed reasons—not a made-up precision score. 5. Give the smallest concrete repair plan. Prefer a clearer workflow, product-specific content, real control outcomes, and reachable states over adding more visual decoration. ## Score Bands - **0–29:** specific enough to ship; keep checking real states and responsive behavior. - **30–59:** recognizable defaults are leaking in; repair the highest-impact structural choice before polishing. - *...