Loading...
Loading...
Found 873 Skills
Keep cyclomatic complexity low; flatten control flow, extract helpers, and prefer table-driven/strategy patterns over large switches
Modularizes existing Angular components and projects following official angular.dev best practices, SOLID principles, and the Smart/Presentational pattern. Use when the user asks to "modularize", "refactor component", "split component", "extract component", "decompose component", "organize Angular project", "apply Angular best practices", "split into feature modules", "restructure project", or "improve project structure".
Single Responsibility Principle, ensuring that code files, functions, and modules have clear and single responsibilities. Applicable to all code files.
Use when writing similar code in multiple places. Use when copy-pasting code. Use when making the same change in multiple locations.
Review changes for test gaps, simplification, naming consistency, reuse opportunities, and TODO quality
Remove dead code and duplication pragmatically with a 5-phase systematic approach
Analyze Python code for style improvements including naming, structure, nesting, and cognitive load reduction
Improve code readability without altering functionality using idiomatic best practices
Replaces custom modules with OSS packages using ln-645 migration plans, atomic keep/discard
Simplify and refine TYPO3 extension code for clarity, consistency, and maintainability while preserving functionality. Reviews PHP classes, Fluid templates, TCA, Services.yaml, and ext_localconf/ext_tables for TYPO3 v14 best practices. Run after implementing a feature or before merging a PR. Use when working with simplify, clean up, refine, code quality, reduce complexity, readability, maintainability, review code, polish, TYPO3 code review.
Run a multi-agent review of changed files for reuse, quality, efficiency, and clarity issues followed by automated fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".
Use when you need to review, improve, or refactor Java code for type design quality — including establishing clear type hierarchies, applying consistent naming conventions, eliminating primitive obsession with domain-specific value objects, leveraging generic type parameters, creating type-safe wrappers, designing fluent interfaces, ensuring precision-appropriate numeric types (BigDecimal for financial calculations), and improving type contrast through interfaces and method signature alignment. Part of the skills-for-java project