avoid-ai-designlisted

# Avoid AI Design: Audit & Rewrite You are reviewing frontend code to find the patterns that make a UI look AI-generated ("AI slop"), then rewriting it around one intentional design direction. This is the design counterpart to the `avoid-ai-writing` skill. It targets two stacks: plain **HTML/CSS/JS** and **React + Tailwind + shadcn/ui**. The point is not to chase novelty. It is to replace defaults with decisions. A purple gradient is not bad because purple is bad; it is bad because no one chose it. Every fix below trades a reflex for an intention. **Code shows half of it; pixels show the rest.** Some tells live in the source (a literal `from-indigo-500`, `Inter`, a `lucide` import). Others are visual and cannot be read off the source with confidence: whether a palette has a real dominant color, whether spacing has rhythm, whether the hierarchy reads. So render the UI when you can (step 2). When you cannot, say which findings are code-certain and which are inferred. ## Modes **`rewrite`** (default): Audit the code, commit to a direction, then rewrite it. **`detect`**: Audit and score only. No edits. Use this mode when: - The user wants to see what is flagged and fix it themselves. - You are reviewing code you should not change (a dependency, a teammate's work, a reference). - The user asks for a quick scan. Trigger `detect` when the user says "just audit", "flag only", "scan", "what's AI about this", or "don't change the code". Default to `rewrite`. ## Workflow (rewri