Loading...
Loading...
Found 93 Skills
Refactor code to simplify it without changing behavior.
Remove AI-generated slop introduced on this branch relative to main.
Reduction pass — cuts content, structure, visuals, and dead code that doesn't answer a user question or drive an action, respecting CRAFT_LEVEL. Use when the UI feels cluttered, has too many CTAs, walls of text, or decorative noise, or when the user says "simplify this" / "it feels too busy". Invoke when the user asks for distill on their UI, or mentions 'distill' alongside design / UI / frontend work.
Playbook for using lines-of-code (SLOC) as a north-star metric to genuinely simplify and improve an engineering solution — without gaming the number. Use when asked to "cut SLOC", "reduce/simplify the codebase", remove bloat/complexity/tech-debt, delete dead code or duplication, or hit a line-count target. Covers preflight (baseline + feedback loops + tooling), an honest reduction order, a self-audit against gaming, stop conditions, and a Flutter reference.
Two-pass audit and cleanup for a codebase that has started to congeal — spaghetti code, or "koshary code," where the layers have collapsed: business logic lives in the controller, the same validation sits in five files, and nobody wants to open the 800-line one. Pass 1 reports layer collapse, duplication that will drift, functions nobody reads, and dead code as a prioritized list and changes nothing; Pass 2 fixes in a safe order once the user approves. Security holes and vulnerable dependencies are covered too, as a later section rather than the headline. Use this whenever the user asks to audit, review, or clean up a codebase — and also when they say "this codebase is a mess," "spaghetti code," "technical debt," "this is unmaintainable," "duplicated logic," "dead code," "what's wrong with my code," or ask for a security review. Trigger it even when they never use the word "audit."
Use when symfony controller cleanup
Parallel 4-agent cleanup of recent code changes.
Remove code comments that explain or defend Remotion's own code, keeping only comments about external systems we cannot change (browser quirks, codec/FFmpeg behavior, third-party APIs, OS or platform bugs). Use when the user invokes /no-comments or asks to strip unnecessary comments from a diff or files.
Removes generated-looking code from a ui-sdk diff or files, like comments that restate the code, filler JSDoc, defensive checks for impossible cases, one-caller helpers and vague names, without changing behavior. Use as the last step of any change, or when asked to clean up, trim comments or remove slop.