Loading...
Loading...
Found 707 Skills
Applicable to code-centric tasks such as coding, debug/debugging, bug fixing, refactor/refactoring, code review, scripting, automation, and implementation planning.
Implement the minimal code needed to make failing tests pass in the TDD green phase.
This skill should be used when making design decisions, evaluating trade-offs, assessing code quality, or when "engineering judgment" or "code quality" are mentioned.
Use when working with tdd workflows tdd refactor
Refactor code to improve clarity and maintainability without changing behavior. Use when improving readability, reducing complexity, or eliminating duplication.
This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability. Use this for identifying code smells, architectural issues, dependency problems, missing documentation, security vulnerabilities, and creating comprehensive technical debt documentation.
Diagnoses what makes code complex and why, using the three-symptom two-root-cause framework. Use when code feels harder to work with than it should but the specific problem is unclear. This skill identifies WHETHER complexity exists and WHERE it comes from. Not for scanning a checklist of known design smells (use red-flags) or evaluating a specific module's depth (use deep-modules).
Map a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the ideal path," unify duplicated systems, or audit architecture before a refactor. Emits a proposed unified flowchart plus per-system /make-plan prompts.
Find dead code and cleanup candidates such as unused exports, unreachable branches, orphaned files, stale feature flags, dead registrations, and compatibility layers with no live callers. Use when auditing refactors, bundle-size cleanup, architecture simplification, pre-release cleanup, reviewing requests to find unused code or decide what can be deleted, or when deciding whether code can be safely removed or auto-fixed.
Test-Driven Development enforcement skill - write tests first, always
Dead Code Cleanup and Consolidation Expert. Used to remove unused code, duplicate code, and refactor. Execute analysis tools (knip, depcheck, ts-prune) to identify and safely remove dead code.
Core engineering principles for sustainable, maintainable code. No shortcuts, no hacks. Quality gates before completion.