Loading...
Loading...
Found 83 Skills
Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Identifies code smells and provides step-by-step refactoring recipes. Use when improving legacy code maintainability or teaching students how to apply Clean Code and SOLID principles.
Modernize and improve legacy codebases while maintaining functionality. Use when you need to refactor old code, reduce technical debt, modernize deprecated patterns, or improve code maintainability without breaking existing behavior.
This skill should be used when the user asks to "simplify code", "clean up code", "refactor for clarity", "reduce complexity", "improve readability", "make this easier to maintain", or asks to simplify recently modified code.
Code style rules for readable, maintainable implementation. Load this skill always when writing or editing code, and whenever the user asks about code style, refactoring shape, function/file size, object-oriented structure, helper ordering, or comments. For Frappe-specific work, prefer frappe-app-dev.
Review the C#/.NET code for design pattern implementation and suggest improvements.
Simplify and refine recently changed code for clarity, reuse, quality, and efficiency while preserving behavior.
Suggest refactoring opportunities to improve code structure and maintainability. Use when improving code design or reducing complexity.
Split a large ***plain module into smaller modules grouped by logical domain. The resulting modules are connected via a requires chain so that functionality is 100% preserved. Use when a module has grown too large and its functional specs span multiple distinct concerns that would be clearer as separate modules.
Relentlessly critiques code against classic software engineering principles (SOLID, separation of concerns) to prevent "clever process shenanigans" and spaghetti code. Use before finalizing a feature or opening a PR.
Review and refactor code in your project according to defined instructions