Loading...
Loading...
Found 134 Skills
Standards for Angular 17+ Enterprise Architecture. Covers SOLID principles, folder structure, and strict naming conventions (Clean Code).
Kotlin development guidelines with best practices for clean code, naming conventions, function design, and data handling
Guidelines that help developers design maintainable, scalable, reusable, and loosely coupled software systems. Use when the user asks about design principles, clean code, refactoring, code structure, SOLID, DRY, dependencies, or maintaining software systems.
Design systems using Martin Fowler's principles of refactoring, continuous integration, and patterns of enterprise application architecture. Emphasizes clean code, evolution over revolution, and writing code for humans first. Use when designing enterprise systems, planning refactors, or establishing engineering culture.
Backend code quality for clean, production-ready, maintainable code. Adapts to the existing language, framework, and style. Covers functions, reusability, modern syntax, error prevention, readability, and security awareness. Use when writing, reviewing, or refactoring backend code for quality, maintainability, or production readiness.
Use when simplifying, refactoring, or reviewing code changes. A mindset that eliminates unnecessary lines, variables, dependencies, and noise.
Code refactoring expert for improving code quality, readability, maintainability, and performance. Specializes in Java and Python refactoring patterns, eliminating code smells, and applying clean code principles. Use when refactoring code, improving existing implementations, or cleaning up technical debt.
Use when writing similar code in multiple places. Use when copy-pasting code. Use when making the same change in multiple locations.
Expert in implementation and coding. Implements high-quality code while complying with project conventions and structure based on design documents. Acts as a specialist in the corresponding programming language according to the language being used.
Code refactoring best practices based on Martin Fowler's catalog and Clean Code principles (formerly refactoring). This skill should be used when refactoring existing code, improving code structure, reducing complexity, eliminating code smells, or reviewing code for maintainability. Triggers on tasks involving extract method, rename, decompose conditional, reduce coupling, or improve readability.
Use when tempted to write clever code. Use when solution feels complex. Use when showing off skills instead of solving problems.
Guide discovery through questioning techniques and pattern recognition for Clean Code, GoF design patterns, and architectural decisions. Use when coaching developers, facilitating design discussions, or helping teams discover solutions.