ProveNotPreventAiSlop [principle] v1.0.0

The goal of anti-slop guidelines is to prove distinctive quality — not merely to prevent the worst defaults. A design that avoids all slop signals but makes no positive aesthetic statement has still failed. The bar is not 'does not look AI-generated' but 'looks unmistakably intentional.'

Implications

• Anti-slop checklists are necessary but not sufficient — pass them and then ask the brand distinctiveness question.
• A design with one genuinely bold, memorable decision is better than a design that merely avoids all 10 slop signals.
• The test is not the absence of slop signals but the presence of something worth remembering.

ProveNotPreventAiSlop [principle] v1.0.0

The goal of anti-slop guidelines is to prove distinctive quality — not merely to prevent the worst defaults. A design that avoids all slop signals but makes no positive aesthetic statement has still failed. The bar is not 'does not look AI-generated' but 'looks unmistakably intentional.'

Implications

• Anti-slop checklists are necessary but not sufficient — pass them and then ask the brand distinctiveness question.
• A design with one genuinely bold, memorable decision is better than a design that merely avoids all 10 slop signals.
• The test is not the absence of slop signals but the presence of something worth remembering.

Rationale

Framing anti-slop work as prevention leads to checklist compliance without genuine quality: the designer avoids Inter and purple but produces a different kind of generic. Framing it as proof-of-quality shifts the question from 'did we avoid the bad list?' to 'does this design make a clear, confident statement about who this brand is?' The second question is harder and more valuable.