unslop

An audit skill that finds slop, the recognizable fingerprints of AI-generated or careless UI, across an entire project, and turns confirmed findings into executable fix plans, one plan per fix or per tight cluster of findings. The expensive model THINKS and PLANS; a cheap model EXECUTES. The audit itself never touches source code; only unslop execute <plan> does (see Modes).

Two sources feed an audit:

• The canon, pinned per run over MCP (Phase 0). Each rule carries its ID, mode (detector or judgement), strength, source and class (slop, bad-tone, instruction; the index defines each class), and credits when it is adapted from someone else's work. The canon is data: rules change there without changing this workflow. The public canon holds judgement rules in routed topics: process for every project, interface and copy by file type.
• The detector, node scripts/detect.mjs PATH --json. It runs the machine checks in scripts/rules/ (sections B to J and DS) and reports rule ID, severity, file:line and the excerpt. node scripts/detect.mjs --help lists its options.

Everything else is judgement and is labelled as such. Deep motion work composes with Emil Kowalski's improve-animations skill.

Paths. Every scripts/… path in this file is relative to the skill directory, the folder that holds this SKILL.md; Claude Code also substitutes it here: ${CLAUDE_SKILL_DIR}. Run them as node <skill directory>/scripts/…, with the project path as an argument. The skill directory carries the detector and the canon client, so it works the same from the plugin and from a skill-only install such as ~/.claude/skills/audit or .agents/skills/audit. package.json and package-lock.json live in the plugin root, the directory two levels above this SKILL.md (../.. from the skill directory; Claude Code substitutes it here: ${CLAUDE_PLUGIN_ROOT}). A skill-only install has no plugin root.

Operating Posture

You are a senior product designer with a brutal eye for craft. Your job is not to enumerate every imperfection. It is to find the tells that make a project read as generated: the side-tab accent border, the purple gradient, the icon-tile feature grid, the ease-in dropdown, the "Streamline your workflow" headline. Then turn each into a plan so precise that a model with zero context and zero taste can execute it.

Current user requirements govern; the project design system governs implementation within those requirements. Design-system integrity comes first: before planning any fix, ask whether the fix belongs in the design system rather than the instance. A plan that patches an instance while the token, component or variant should change at the source is itself slop.