miqdadbadjuber/anti-slop v3.2.7

v3.2.7: OpenCode door & Three more slop patterns get names

on GitHub

Three patterns named

This round is mostly naming: three slop patterns that were slipping between the rules now have a name, a why, and a fix.

• Two-State Layout (antislop-layoutmobile). A layout with exactly two states: a phone stack below one breakpoint and a wide grid above it, with nothing defined between. Tablet and small-laptop widths then inherit whichever state is nearest, so the page is designed at two sample points and broken everywhere in between. R-03 asks for the whole range, not two of them. The fix is to define real states at the widths where the content stops working, which is usually three, not two.

• The Over-Explained Comment (antislop-code). One comment that runs on for several lines, stacking reasons, context, and history around a fact that fits in one line. Every sentence can be true and the length is still the tell. The "not a ban" list in antislop-code used to protect a workaround note without ever limiting its length, which is exactly how these survived review. The fix is one line, two at most, never three.

• Decorative Status Dot (antislop-ui). A small colored dot beside a heading, eyebrow, or nav item, usually glowing and pulsing on a loop, that marks nothing. It borrows the vocabulary of a live indicator for a page where nothing is live. This one fell in the gap between three rules: the glow cap allows a single dot, the pulse rule only covers the animation, and neither asked what the dot was for. A dot has to mark a real state; if it marks nothing, it goes.

OpenCode door

OpenCode has no plugin marketplace, so the door is the skills folder plus an AGENTS.md pointer. Verified end to end against opencode 1.18.30: the picker writes .opencode/skills/, and opencode debug skill returns those skills from that path. README and GUIDE carry the row.

Also in this release

• R-37 states what to do when DESIGN.md conflicts. R-37 already said style direction is the owner's identity and the filter applies on top of it, which read as an exemption for a direction that is itself sloppy. It now says: name the element, name the rule it collides with, and ask the owner to keep it or drop it. Never silently follow, never silently override. Only a named pattern gets questioned; a bold palette or an unusual typeface is identity, not slop.
• antislop-layoutmobile no longer reads as phone-only. Its description and body now cover reflowing across screen widths, phone to desktop, because the two-state problem shows up above the phone, not on it.
• Gemini CLI is marked as legacy support: sunset 18 June 2026, superseded by Antigravity. The picker still installs into .gemini/skills/ for existing setups.
• Every comment in this repository was audited against antislop-code and cut to one or two lines, plus a fix so Python bytecode can no longer reach the npm tarball.

Full detail in the roadmap.