Appearance
Anti-slop
Anti-slop is a reference book, not a tool. It installs no hook and no command, nothing behind it ever runs, it is pure material an agent reads when a piece of work feels generic and it cannot say why. It is the first module ever built against the reference-book type that frameworks/MODULE.md specced, so it is also the thing that proved the type out. The book is built on one claim: slop is what you get when nobody chose, so most of it is decision menus rather than rules, an entry names a failure, says why you land there by default, and hands over three to six real options with what each one costs. It holds no doctrine and enforces nothing; where a project has its own written taste, that wins, and this book is the menu it picked from.
In Practice
You are not sure why something looks off. Open the symptom index rather than guessing at a category:
.claude/references/anti-slop/SLOP.md the symptom index, "the feeling" to "where to look"The index is written by feeling, "it looks like every other ai thing", "there are exactly five of everything", "the svg looks wrong once it is actually rendered", because that is how you actually arrive at the book, not by chapter number. Each row points at one leaf, and every leaf is self-contained, so opening one is the whole cost.
You want to check something before you hand it over. Run the eight-step self check:
.claude/references/anti-slop/CHECK.mdIt stops the moment a step says stop. Step 2 branches on whether there is an artifact to look at yet: if there is, you render it, run it, and read it back cold, at the size and on the ground it actually ships at; if there is not, because the work is still a spec or a plan, the step becomes writing down exactly what you will look at once something exists, so the check still leaves something behind rather than getting skipped. Steps 2 and 4 (look at the real output, then list what you never chose) are the two the book says matter most if you only remember two.
You cannot name the failure. VOCAB.md is the one owner of every antipattern handle across the whole group, "card soup", "the round five", "the indigo default", each one a pointer to the leaf that carries its full entry. A name you can say in passing is a problem you have actually recognised, one you cannot name usually just gets shipped.
You want the doorbell instead of reading by hand. The module ships one skill, so /anti-slop, or just describing what feels off, routes you to the right leaf and stops there.
Severity, Three Tiers
Every entry in every leaf is tagged one of three severities, and the fix order runs in this sequence: load bearing, then costly, then cosmetic.
| severity | what it means |
|---|---|
| cosmetic | it looks worse than it could, nothing fails, a reader notices and moves on |
| costly | it works and nobody keeps using it, nothing is broken or unreadable, the thing just quietly stops being worth the friction, a window that fans the laptop at idle, a motion tax paid on every interaction |
| load bearing | the work does not do its job, text that cannot be read, a state that traps the user, a claim that is wrong |
The costly tier was added specifically because the two-tier version kept swallowing it: a cost that only shows up after a week of use is not cosmetic (nobody notices it and stops using the thing), and it is not load bearing either (every individual run still succeeds). Calling it either one lost the reason it mattered, that the work was finished and the feature died anyway.
The Two Rules That Bind You, Not the Book
Everything else in the book is material you draw from. These two are not optional the way the entries are.
- You cannot skip the look. Render it, run it, read it back cold, at the size and on the ground it ships at, because most of what the book calls load bearing is invisible in the source. "Nothing built yet" is the one branch, and it is not a skip,
CHECK.mdstep 2. - Fix load bearing first, then costly, then cosmetic. Every entry carries one of the three tags, and spending the budget on trivia while a real failure sits there is its own named failure.
When Not to Use It
Most work does not deserve this book, and applying it everywhere burns budget on things nobody will ever look at. SLOP.md lists the cases to skip outright: output thrown away in the next hour, internal work where the only reader asked for it fast, a fixture or stub where being obviously fake is the feature, and anything where speed genuinely beat quality and someone said so out loud. The shape to watch for is caring about the wrong artifact, a beautiful throwaway costs more than an ugly one because the time came out of the thing that mattered.
The Three Parts
| part | label | what it ships |
|---|---|---|
| anti-slop-core | core | the base, the mechanisms, the over-correction counterweight, the shared vocabulary, the self check, and the cross-cutting craft leaves (type, colour, layout, motion, icons, and the nine states nobody designs). ships one doorbell skill that routes and holds no material itself |
| anti-slop-svg | svg | the SVG book, the format features worth knowing plus the eleven things that render wrong rather than look wrong |
| anti-slop-apps | apps | the desktop app book, the web-page-in-a-wrapper tell, what a window adds to each of the nine states, and the one state that is desktop only |
The two domain books declare needs: anti-slop-core, so picking either one pulls the core in with it, and a project that only ever writes SVG never installs the desktop material. Everything lands at .claude/references/anti-slop/, and the doorbell skill lands separately at .claude/skills/anti-slop/. The core part was renamed from anti-slop to anti-slop-core once the three parts folded into a books picker bucket, since a subgroup cannot share a name with a part; the label field is what keeps the picker showing the short names core / svg / apps even though nothing moved on disk, the module directory, the reference dest, and the skill still all read anti-slop.
The Doorbell Skill
The skill holds no material of its own, it reads the ask, names the likely leaf, opens it, and stops. It exists because a book nothing routes to is a book nothing reads. Without it, the reference material would sit under .claude/references/ with nothing pointing an agent at it, indistinguishable from any other file nobody opens. The skill also carries two rules that bind harder than anything in the book itself (look at the real output, fix load bearing before cosmetic) plus a short do-not list: don't treat the book as a checklist, don't read a menu as ranked, don't run it on throwaway work, and don't use it as finn's personal taste.
The Entry Template
Every entry in every leaf, across all three parts, carries the same eight fields in the same order, so a partial read still parses:
is what the thing is, a line or two
why the mechanism, why you land here by default
tell how you spot it from outside, before you know the cause
severity cosmetic, costly, or load bearing
show the artifact, never a description of a picture
instead the menu, three to six real options with what each costs
overdone what going too far the other way looks like
source sourced <where>, or invented, plus a date where it has a shelf lifeinstead is the field the whole book is for, an entry that names a problem and gives one answer has just moved the default one step along, which is how a book like this turns into the next thing everyone does. Every menu in that field is unordered on purpose, position carries no meaning and the first option is not the recommendation; where an option genuinely is the usual pick, it says so in its own words rather than by sitting first. That rule exists because the book's own audit found several menus leading with a favourite, which is the book's own antipattern (the tasteful uniform) landing on its own author. Two entries carry a stated shelf life on top of the usual source field, the tailwind hex list in craft/COLOUR.md and the rasteriser support table in svg/GOTCHAS.md, both need re-checking before you lean on them rather than trusted as written.
The Unchosen Main Loop
craft/STATES.md names nine states, not eight. The leaf used to frame itself as the happy path plus eight other states, but the happy path (working) is now inside the set as the ninth, and the reframing is the more interesting claim than the count. Eight of the nine go missing for one shared reason, you build with the data already there, so the fixture is loaded, the network is up, nothing has failed yet, and those eight are reached by accident, in production, by someone else. working goes missing for the opposite reason: you see it from the first hour and every hour after, so it stops being a thing you look at and becomes the background you look through. It was written early, usually as a debug print, and it shipped because it was never wrong.
The consequence the leaf draws out is that frequency is not what gets a state designed, attention is, and the two come apart at both ends, a state nobody ever visits and a state nobody ever stops visiting both arrive undesigned. The handle for it is the unchosen main loop, severity costly, and the entry's show field walks the same reimport line four ways, a raw debug print, a tidied version, one with the outcome moved to the last word, and one that waits for the consuming system to acknowledge rather than printing when its own call returned, which is the only version that cannot quietly claim success. The entry is sourced to a real audit finding: a subagent given the book and a background-tool brief reported that the only genuine design decision in its tool lived in the line the book had no material for, and that it had to leave the book entirely to design it. This entry is that gap closed.
The checklist at the bottom of the leaf is now nine boxes, and its "if you only do two" advice splits by shape of tool: first run and long running for anything a person sits in front of, working and idle for anything that runs in the background.
The idle entry itself was rewritten in the same pass, because its menu offered its own named failure as one of the options: "a heartbeat on a human timescale" is chatty, named four lines above in the same entry. It now carries five options that each state what they cost (a status line updated in place, saying nothing and letting the last event be the status, answering on demand, a heartbeat only on a transition, dropping to a slower poll when quiet) plus an explicit note on what is deliberately not on the menu and why it looks right anyway. It is a concrete case of the book's own doctrine catching a defect in the book.
The Audit
The book was checked by being used rather than by being re-read. Three subagents were handed one shared brief, a tool called ember, and told to produce a real artifact drawing on the book: an SVG mark and icon set (ember-mark), a desktop status window spec (ember-window), and a CLI tool's readme and sample output (ember-words, run as the control case, since there is no prose leaf to draw on). Their artifacts and working notes sit in harness/tests/anti-slop/.
That audit caught real defects in the book, four of which were verified and fixed:
- The book gave advice that was wrong on the harness's own bundled rasteriser. The hardcoded-ink entry in
svg/SVG.mdrecommended CSSvar(--ink, #fallback)as the standalone-safe option. Measured against the bundled resvg on 2026-08-25,var()does not resolve, does not honour its own in-function fallback, does not fall back to a presentation attribute sitting beside it, and paints black, warningfailed to parse fill value, fallback to blackrather than failing silently.currentColorrenders correctly in the same run, socurrentColoris now the portable option andvar()the browser-only one, the reverse of the usual ranking, and the entry is corrected. - The hard rule shipped with a broken invocation.
nu scripts/check.nu ...was quoted in six places across three files, a path that resolves from nowhere a reader actually stands. Every one now readsnu .claude/skills/diagram/scripts/check.nu. apps/STATES.mdsaid seven states, listed seven, and had eight checklist boxes. Theember-windowrun foundfiltered emptybroken out only at the checklist, never promoted to its own entry.- The rasteriser support table read green for
var(), which fails. Corrected alongside the hardcoded-ink fix, since both draw on the same measurement.
The same audit pass drove the states leaf moving into craft/ on 2026-08-26: the eight states (at the time) were the same eight in every medium, so routing a CLI or a web page into apps/ to find them was a mis-route, and apps/STATES.md is now only the desktop layer over them, what a window adds plus the one state that only a window has (multi monitor and odd geometry).
A second audit run, 2026-09-02, went after the medium the states move was made for: a background tool. One subagent, walled off from the harness's own planning and test-log files and from the three prior audit runs, was briefed to build a tray asset watcher for a 2D game engine. The artifact sits at harness/tests/anti-slop/hotplate/. It found nine defects, the top four re-verified by hand before being acted on. The two that mattered are the ones this page covers above, the missing working entry and the idle menu offering its own named failure. The rest landed as: chatty and the unchosen main loop added to VOCAB.md, both symptom-index and route-table listings corrected from six or eight states to nine, the umbrella missing state entry's unused fields marked n/a, and the offline n degraded entry's source field split, the resolve-from-bin/-then-PATH half really is sourced to frameworks/MODULE.md, but the "say which one you used" half was invented and had been tagged sourced regardless, a small honesty fix the book's own audit doctrine caught in its own author.
apps/STATES.md also picked up a working row in its what-a-window-adds table, naming the tray tooltip as the hard case, 127 usable characters on Windows and the entire surface a hidden app has. That number sat unverified for a fortnight as a bare "roughly 128" off the audit agent's memory; it was checked against the Win32 NOTIFYICONDATAW reference on 2026-09-11 and corrected. szTip is WCHAR[128] including the terminating null, so 128 was the array length and never the budget, and the legacy struct is half that. The same pass added the default that makes the budget moot: on NOTIFYICON_VERSION_4 the standard tooltip is suppressed unless the app sets NIF_SHOWTIP, so an app can have no tooltip at all rather than a truncated one, failing silently because nothing errors. Its multi-monitor entry is now labelled the tenth state rather than the ninth, following from the states leaf growing by one. Separately, apps/APPS.md's fake controls entry was narrowed from "hand-built where the platform ships a real one" to "a control missing its invisible half", with an explicit carve-out for imgui, egui, canvas, and game UI, where there is no platform control to reach for and the entry reads as a budget rather than a diff.
harness/tests/TESTS.md carries the dated log of both runs and what neither covered, including that only the bundled resvg was tested (no browser, no other rasteriser) and that the second run's tray-surface gap in apps/APPS.md is still open and unfixed.
Key Files
SLOP.md
The base doc – the position (slop is what you get when nobody chose), the symptom index, the three-tier severity split, the eight-field entry template, the when-slop-is-fine list, and the escape hatch: you may deviate from anything in the book, on the condition the reason gets said out loud.
VOCAB.md
The shared handle store – one owner for every antipattern name across the whole book group, so two leaves never invent different words for the same failure. A row here is a pointer, the full entry lives in the leaf named in its last column. Its ownership reaches outside the book group too, plan/findings-logo-design-tooling.md names VOCAB.md as the ban-list owner other parts of the harness (the diagram module's dealer, among them) should reference rather than carrying their own copy.
CHECK.md
The self check – eight steps, run in order, stop as soon as one says stop. The one part of the book that is procedure rather than material, kept deliberately short so it is a pass an agent actually runs.
WHY.md
The mechanisms – the named failure modes (the unchanged default, median collapse, forced symmetry, the hedge, the list reflex, and more), each with a before/after pair on an identical brief.
OVER.md
The other direction – over-correction and scope discipline, scope creep, the abstraction reflex, knob spam, the polish trap, because a book that only pushes one way just trades one failure for another. This is also where the tasteful uniform entry lives, the book's own admission that its unordered menus still tended to lead with a favourite.
LINEAGE.md
Provenance – the traditions this book draws from and the material it was actually built out of, not a bibliography, a name earns its place here because reading it changes how you work, not because it was cited. It traces the word itself back to 2024-era usage and sharpens it to the harness's own framing (slop is what you get when nobody chose), lists the three harness passes and four external sources every sourced field in the book traces back to, groups the wider traditions worth drawing from (restraint as a discipline, the counterweight to restraint, making the constraint visible, the specific over the general), and closes with a table of the 2026 tooling landscape and the honest gap in it: the taste layer is well covered, the visual layer is not, which is why CHECK.md step 2 is the one you cannot skip.
Craft
Cross-cutting leaves that live inside the core part rather than as their own book, because typography, colour, layout, motion, icons, and the nine states get drawn on by nearly every domain book, and a separate installable part for each would mean every domain book needing more than one dependency.
craft/TYPE.md
Type and hierarchy – the default face, one-size type, and the ramp options for making one thing actually lead.
craft/COLOUR.md
Palette and accent – the indigo default, the timid palette, the rainbow, gradient text, and the tailwind hex list the indigo-default entry carries with a stated shelf life. A separate section past the entries covers contrast as the one load bearing colour concern, the wcag AA floor of 4.5:1 body text against its ground, that no static tool catches it, and that an accent needs checking as text as well as as a fill.
craft/LAYOUT.md
Structure and containers – card soup, the three-up, the left rail, radius sameness, the uniform shadow, glass everywhere, the fake dashboard, vague labels.
craft/MOTION.md
Animation and easing – motion tax, the linear ease, the ignored reduce-motion preference, the unanchored transition.
craft/ICONS.md
Icon sets – emoji as icons, mixed sets, the off-grid set, the unlabelled icon-only control.
craft/STATES.md
The nine states nobody designs – first run, empty, filtered empty, idle, working, loading, long running, error and offline, each with the full eight-field entry. Moved here from apps/ on 2026-08-26 because the states are the same ones in every medium, a CLI, a web page, a desktop window, and a background service all get them wrong the same way. working, the happy path, was added as the ninth on 2026-09-02, see The Unchosen Main Loop above.
SVG
svg/SVG.md
The format book – eighteen entries on SVG features that are more powerful than the hand-done thing they usually replace, framed the same way the diagram module frames its own routes.
svg/GOTCHAS.md
Things that render wrong, not just look wrong – eleven entries, including the rasteriser support table measured against the bundled resvg and corrected by the audit above.
Apps
apps/APPS.md
The desktop tell – a web page in a wrapper, and the six places it shows: web density, the mouse-only path, fake controls, chrome mismatch, DPI rot. The fake controls entry carves out imgui, egui, canvas, and game UI, stacks with no platform control to reach for in the first place, where the entry reads as a budget rather than a diff.
apps/STATES.md
The desktop layer over the nine – not the states themselves, those live in craft/STATES.md. This leaf covers only what a window adds to each of the nine (idle means repaint-at-idle fanning the laptop, empty means keep the chrome or it reads as a crash, working means the tray tooltip's 127-character budget and the NIF_SHOWTIP default that can suppress the tooltip entirely, error means an inline bar over a modal that steals the window) plus the tenth, desktop-only state: multi monitor and odd geometry, a window saved on a monitor that later gets unplugged and comes back unreachable.
apps/STACKS.md
Per-toolkit tells – a table of which tell each desktop stack walks into first.
Connects to
- Diagram, whose
check.nurasterises every authored example in the book before it ships, per the diagram module's own hard rule that nothing goes out unlooked-at, and whose dealer referencesVOCAB.mdas its ban-list rather than carrying its own copy. - Installer, which ships the three parts (
anti-slop-coreplus the two domain books as hard dependents) and resolves theneedsedge so a domain book always pulls the core with it. - The condensed, end-user version of this page is the module's own
USAGE.md, atharness/modules/anti-slop/USAGE.md– that one is the thin parts table and the two rules that actually bind, this page is the fuller depth of the same module.