amvcp-tokens-anti-slop

To detect banned AI purple colors in design tokens, you can lint parsed token maps or DESIGN.md files against an anti-slop rule set. The lint identifies near-match AI purple, violet, and indigo colors, treating any non-ok result as a hard error that blocks shipping.

You can lint generated HTML for prohibited visual patterns by scanning static HTML strings to detect gradient backgrounds and double drop-shadows. The audit flags these banned patterns along with banned colors and font stacks, returning a fail-fast error if violations are found.

An anti-slop audit for UI consistency is a validation process that enforces strict bans on specific AI-like visual patterns, pure black and white colors, and banned primary fonts in token sets and emitted HTML. It catches these visual issues before they reach users.

Yes, you can check rendered DOM computed styles for banned primary font families during development. The in-browser DOM auditing feature walks a rendered page, computes styles, and stamps offenders with data-vc-slop-alert attributes for immediate visual review.

Yes, the anti-slop lint works with both flat token maps and parsed DESIGN.md files. Token-set auditing detects banned colors, banned primary fonts as first-family only, and banned visual patterns across these token sources.

Your design token validation fails-fast and blocks shipping on non-ok results because the anti-slop lint enforces strict behavior where any non-ok result is treated as a hard error. This prevents AI-like visual slop from reaching production environments.