Loading...
Loading...
Found 47 Skills
Simplify existing code without changing behavior. Focus on local complexity reduction such as flattening nesting, extracting readable helpers, removing dead code, consolidating obvious duplication, and improving names. Use when the user explicitly asks to simplify, clean up, or reduce complexity in existing code.
Expert TypeScript refactoring patterns for cleaner, type-safe code
Audit a codebase for dead code, unreachable branches, duplicated logic, and vestigial abstractions, then remove them safely with proof. Use to reduce sprawl, pay down tech debt, or clean up after a feature is retired or migrated.
Comprehensive toolkit for detecting and eliminating "AI slop" - generic, low-quality AI-generated patterns in natural language, code, and design. Use when reviewing or improving content quality, preventing generic AI patterns, cleaning up existing content, or enforcing quality standards in writing, code, or design work.
Remove Rust-defined C symbols that are either unused or only used in C/C++ unit tests.
Detects and safely removes unused code (imports, functions, classes) across multiple languages. Use after refactoring, when removing features, or before production deployment. Includes safety checks and validation.
Review changed code for reuse, quality, and efficiency, then fix any issues found.
Stop AI coding agents from shipping sloppy code — over-abstraction, drive-by refactors, obvious comments, extra files, unrequested deps, giant unreadable files, or fishing outside the workspace for “inspiration”. Use when writing or editing code, implementing features, fixing bugs, splitting or organizing files, or when the user mentions slop, cleanup, keep it simple, minimal diff, file too big, hard to navigate, or stay in the repo.
Prepare branch for code review by building context, identifying issues, and suggesting improvements
Knip finds unused files, dependencies, exports, and types in JavaScript/TypeScript projects. Plugin system for frameworks (React, Next.js, Vite), test runners (Vitest, Jest), and build tools. Use when cleaning up codebases, optimizing bundle size, or enforcing strict dependency hygiene in CI.
Before declaring work complete, checks for loose ends: unused imports, TODO comments created, missing tests, stale references, incomplete error handling. Activates after implementing features or fixes. The cleanup that always gets skipped.
Use this when the user asks to refactor, clean up, optimize, or improve code quality.