Loading...
Loading...
Found 83 Skills
Restructures existing code to improve readability, maintainability, and performance without changing external behavior. USE WHEN: Restructuring code without changing behavior, extracting methods/classes, removing duplication, applying design patterns, improving code organization, reducing technical debt. DO NOT USE: For bug fixes (use /debugging), for adding tests (use /testing), for new features (implement directly). TRIGGERS: refactor, restructure, rewrite, clean up, simplify, extract, inline, rename, move, split, merge, decompose, modularize, decouple, technical debt, code smell, DRY, SOLID, improve code, modernize, reorganize.
Practical guidance for writing, refactoring, and reviewing fast, reliable, and maintainable Rust code.
Code simplification for clarity and maintainability. Use PROACTIVELY after code is written or modified to refine recently changed files.
Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.
Simplify and refine code for clarity, consistency, and maintainability. Use after writing or modifying code to clean it up while preserving all functionality.
This rule enforces the Don't Repeat Yourself principle to avoid code duplication and improve maintainability.
Refactor, simplify, or clean up code for improved maintainability without changing business logic
Refactor overly large code units into smaller, more focused components. Use when code has grown too large or complex.
Used to audit codebases to ensure their naming complies with established terminology and specifications. This Skill should be used when you need to enforce a project's 'Ubiquitous Language', identify deviations in method/variable/parameter naming, and propose modification suggestions.
Executa refatoração segura e incremental para projetos Go, preservando comportamento e reduzindo complexidade. Use quando o usuário pede para refatorar, simplificar ou melhorar manutenibilidade. Não use para correção de bug (usar bugfix) nem para review/auditoria (usar reviewer).
Analyzes code comments for accuracy, completeness, and long-term maintainability. Identifies misleading comments, comment rot, and documentation gaps. Triggers: After adding documentation, before finalizing a PR, when reviewing comments. Examples: - "Check if the comments are accurate" -> verifies comments match code behavior - "Review the documentation I added" -> analyzes new comments for quality - "Analyze comments for technical debt" -> finds outdated or misleading comments - "Are my docstrings correct?" -> validates documentation accuracy
Audit code architecture for over-engineering and unnecessary abstractions. Use when user asks to "review architecture", "simplify code structure", "reduce over-engineering", "evaluate abstractions", or mentions premature abstraction, interface proliferation, factory patterns, YAGNI, or enterprise-grade complexity.