Menú
Remove AI slop from every file in the repository while preserving behavior and genuine information.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Structured design critique across usability, hierarchy, consistency, and accessibility. Use when the user shares a Figma link, screenshot, mockup, or asks for design feedback ("review this design", "critique this screen", "what do you think of this UI?"). Use after design-router when a theme has been selected and applied.
Runs a disciplined ablation workflow for MixJam Electron (MJE) bugs to prove which changed files or layers are actually required for a fix. Use when an MJE import, playback, or UI bug has a known pass/fail check but several edits may be involved, or when the user asks which change actually fixed it, what can be removed, or for the smallest proven fix.
Creates or updates repository specs, acceptance criteria, durable decisions, and documentation for new work. Use when adding a feature or defining an ambiguous slice, when making architectural decisions or changing contracts (API, persistence, import, playback), or when recording durable context (glossary, conventions, trade-offs) for future engineers and agents.
Audits the MixJam Electron (MJE) codebase for dead TypeScript code, orphan files, and unused symbols across main and renderer processes, triages findings into live dead code or false positives, and optionally removes provably dead code with focused validation. Use for a dead-code audit, or for cleanup explicitly requested from analyzer findings.
Routes a requested UI visual direction to one bundled design theme. Use when building or restyling an interface that needs an explicit aesthetic.
Diagnoses hard bugs and performance regressions with a controlled feedback loop, and implements the fix only when requested. Use when the failure is flaky, not yet reproducible, still lacks a root cause, or needs measurement.
| name | deslop |
| description | Remove AI slop from every file in the repository while preserving behavior and genuine information. |
| disable-model-invocation | true |
Strip slop: content that clashes with the evidence supplied by the file, its siblings, or the repository's established conventions. This is a full-repository pass, not a diff review.
Load the rule set that matches each file before judging it:
Apply more than one rule set when a file mixes concerns. A listed smell is a prompt to compare context, not automatic permission to delete.
dead-code-audit when reachability is the question.The pass is complete when every scoped file is recorded as unchanged or edited, every edit has a sibling or repository-convention justification, behavioral validation passes for affected code and config, a second complete read yields no further evidence-backed slop, and the report names edited file counts plus any excluded generated or binary paths.