What's new
- Positioning: it's a filter, not a style guide. ANTISLOP.md now explicitly does not impose any aesthetic. No prescribed colors, fonts, or layouts. Design preferences and brand direction belong to each user. The document only (1) lists generic AI patterns to avoid and (2) holds results to a craftsmanship bar.
- Craftsmanship Standard (C-1..C-5): five preference-agnostic quality criteria: Intentionality, Functional Completeness, Content-Driven Composition, Resilience, Evidence Over Claims.
New rules (R-33 to R-36)
- R-33 No File/CSS Patching via Scripts: features must be written in source, not patched in by external string-replacement scripts.
- R-34 Every Theme You Ship Must Work: a shipped theme toggle must work correctly in both light and dark modes.
- R-35 Verify Before You Deliver: run/build the app, check the console, exercise every interactive element, check every theme and breakpoint.
- R-36 No Fabricated Claims: no invented security, compliance, performance, or customer claims.
Rewritten rules
- R-21 Dark Mode: "give the user a choice" now means building a working light/dark toggle, not deferring the work. No rule may be used as an excuse to skip requested work.
- R-26 Interactive Elements: every interactive element must have a real behavior or be removed. Placeholders need a
// TODOin code AND a visible label.
New slop patterns
- File/CSS Patching via Script
- Fabricated Trust Claims
New sections
- Functional Patterns: concrete definitions of "a working button" for static landing pages (anchor, modal, toggle, mailto, form submit).
- Delivery Gate (Mandatory): the pre-ship checklist is now a mandatory gate with 41 checks (5 Craftsmanship + 36 rules), run and reported before delivery.
Also
- R-05 and R-20 now reference the Craftsmanship Standard.
- Full Indonesian mirror:
ANTISLOP-ID.mdandREADME-ID.md(identical content). .gitignoreadded (localdocs/audit artifacts stay private).