Anti-slop is a linting ruleset for Oxlint that enforces opinionated patterns in TypeScript and JavaScript code.
The tool addresses the problem of low-evidence and low-signal coding patterns by providing a curated set of Oxlint rules designed to catch patterns the maintainer considers problematic. It works by integrating into Oxlint's plugin system, allowing developers to apply these rules to their codebases either through an agent skill that handles installation and configuration, or through manual setup by copying the source into a repository and registering the entry point in an Oxlint configuration file.
Adoption suits teams that want to adopt the maintainer's specific coding preferences rather than seeking a universal standard. The project explicitly positions itself as opinionated and meant to be vendored into repositories rather than consumed as a fixed dependency, allowing teams to copy the rules, review them, and modify them to match their own standards. The tool includes generic rules applicable to any TypeScript or JavaScript project, plus optional Effect-specific rules for repositories using the Effect library. The agent skill automates initial installation, dependency matching, and configuration merging, while also supporting updates that preserve local customizations through three-way merging when possible.
The project maintains clear separation between generic and Effect-specific rules so teams not using Effect do not inherit unrelated architectural policies. Installation can proceed either through the agent skill, which handles dependency resolution and configuration integration automatically, or manually by copying source files and registering entry points. The update mechanism is designed to respect local modifications, staging incoming changes separately and asking about conflicts rather than forcing replacements.
Development activity shows active maintenance of the vendoring workflow, with the agent skill regularly updated to handle installation, configuration merging, and preservation of local customizations. The project includes tooling for three-way merging of updates when upstream snapshots are recoverable, and conservative porting of changes when they are not. Documentation covers both agent-driven and manual installation paths, and the codebase includes infrastructure for managing version alignment between Oxlint and its plugins across different repository states.
