agentleFS
Sign inStart free
kuker24kuker24/OpenCodeBestFriend/skills/install-anti-slop/SKILL.md

install-anti-slop

Skill0 starsChanged 2 months agoMITView on GitHub

Install, audit, configure, or remove opinionated Anti-Slop Oxlint rules in local TypeScript or JavaScript repositories. Use ONLY when explicitly requested to add anti-slop rules, audit TS/JS anti-patterns, configure anti-slop profiles, or migrate/remove an anti-slop setup. Skip for Python/Go/Rust, prose editing (use /unslop), and ordinary coding tasks.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No OCBF Core Coupling: Never add Oxlint or Anti-Slop to OCBF's core Python codebase or dependencies.

    line 17
  2. Very specific:

    Exact Version Coupling: Keep oxlint and @oxlint/plugins on the exact same version.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

install-anti-slop

OpenCodeBestFriend adapter for installing, auditing, configuring, or removing Anti-Slop Oxlint rules. Vendored from dmmulroy/anti-slop (MIT, Dillon Mulroy, commit e8c4880471b23ab7f216fba7b27d173a6ef07d4c, v0.1.2).

Core Boundaries

  1. Opt-In Only: Load this skill ONLY when the user explicitly requests Anti-Slop (e.g. "pasang anti-slop", "audit anti-slop", "hapus anti-slop"). Never auto-load during ordinary coding or non-TS/JS tasks.
  2. Distinct from /unslop and UI Craft: /unslop and rules/03-prose-discipline.md handle prose cleanup. UI template anti-patterns (e.g. default purple gradient mesh, Inter-on-white-card slop, fake testimonials) live in skills/impeccable/reference/taste-guard.md. install-anti-slop is strictly for static Oxlint linting of TypeScript/JavaScript code.
  3. No OCBF Core Coupling: Never add Oxlint or Anti-Slop to OCBF's core Python codebase or dependencies.
  4. Exact Version Coupling: Keep oxlint and @oxlint/plugins on the exact same version.
  5. No Blind Global Rewrites: Linter findings identify patterns; resolve root causes with inference, satisfies, and boundary validation rather than casts or fake comments.

The 4 Modes

ModeBehavior
auditEvaluates rules against source/test/tooling; reports findings without modifying files or dependencies.
recommendedInstalls curated OCBF profile (high-signal type safety assertions) after baseline review.
strictEnables all 15 generic upstream rules (requires explicit user confirmation).
customEnables user-selected rule set.

Effect Rule Group: Opt-in separately (--with-effect) only if effect is a direct project dependency.

Usage

From the target project repository root:

# 1. Audit without project modifications
node <skill-base-dir>/scripts/manage.mjs audit

# 2. Install recommended profile (default)
node <skill-base-dir>/scripts/manage.mjs install --profile recommended

# 3. Install strict profile (when requested)
node <skill-base-dir>/scripts/manage.mjs install --profile strict

# 4. Install with Effect rules (when project uses Effect)
node <skill-base-dir>/scripts/manage.mjs install --profile recommended --with-effect

# 5. Safe removal
node <skill-base-dir>/scripts/manage.mjs remove

References

  • Detailed profile definitions: references/profiles.md
  • Complete rule documentation & fixes: references/rules.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free