Loading...
Loading...
Found 90 Skills
Guide for code refactoring, use this skill to guide you when user asked to refactor a components or functions and when an implementation of a plan requiring a code refactoring.
This rule enforces the Don't Repeat Yourself principle to avoid code duplication and improve maintainability.
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
Review code for quality, maintainability, and correctness. Use when reviewing pull requests, evaluating code changes, or providing feedback on implementations. Focuses on API design, patterns, and actionable feedback.
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
Simplify and refine code for clarity, consistency, and maintainability
Replace hardcoded values with constants, enums, and configuration for maintainability; use PHP 8.1+ enums and config files
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when refining recently modified code unless instructed otherwise.
Improve existing code through safe, behavior-preserving Clean Code refactoring. Use when the user asks to refactor code, clean up messy code, improve readability, simplify structure, reduce duplication, improve naming, review maintainability, or apply Clean Code principles. Do not use for broad architecture redesign unless the user asks for redesign.
Use when reviewing code changes, pull requests, branches, or work-in-progress diffs for correctness, intent fit, repo-local architecture, surrounding-code pattern mismatches, maintainability, naming, tests, and over-engineering. Runs a git-heavy, subagent-oriented review that reads local AGENTS.md/docs/plans/conversation/PR context before judging the diff.
Use when tempted to write clever code. Use when solution feels complex. Use when showing off skills instead of solving problems.
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.