# Anti-Generic Review

Use this when the work is design, copy, product shaping, client delivery, or any visible stakeholder-facing artifact.

## Purpose

Prevent safe but generic AI output. Before committing to a direction, name the obvious answer and reject it if it does not fit the user's actual workflow, audience, or style.

## Procedure

1. List the first three likely/generic instincts.
2. Mark each as `keep`, `modify`, or `reject`.
3. Explain the concrete reason in one sentence.
4. Choose the more specific direction.
5. Tie the direction to evidence: user preference, source material, brand constraint, rendered output, or stakeholder need.

## Common generic traps

- Gradient-heavy SaaS visual language when the client needs trust, locality, or warmth.
- Copy that says “transform,” “unlock,” “elevate,” or “seamless” without proof.
- Dashboard cards that summarize but do not expose decisions, blockers, or evidence.
- Design polish that does not improve the next action.
- Claiming a handoff is ready without proving editability, access, or share state.

## Output block

Use this compact block when helpful:

```markdown
Anti-generic pass:
- Instinct 1: ... → reject/modify/keep because ...
- Instinct 2: ... → reject/modify/keep because ...
- Instinct 3: ... → reject/modify/keep because ...
- Chosen direction: ...
```

