complexity
Analyzes code for complexity issues. Use when code feels hard to understand, reviewing maintainability, or planning refactoring.
Explorez les skills IA publiés de bchapuis et consultez leurs instructions source.
Skills indexés
7Étoiles des dépôts des skills indexés
7Forks du dépôt
0Moyenne des étoiles par skill indexé
1Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Analyzes code for complexity issues. Use when code feels hard to understand, reviewing maintainability, or planning refactoring.
Core software design principles from 'A Philosophy of Software Design'. Use when asking about decomposition, deep modules, information hiding, complexity management, or John Ousterhout's design principles.
Reviews API designs for simplicity and error handling. Use when designing APIs, evaluating interface complexity, or eliminating error conditions.
Reviews code comments for quality. Use when reviewing documentation or evaluating if code is self-documenting.
Reviews modules for depth vs shallowness. Use when designing APIs, reviewing class interfaces, or evaluating abstraction value.
This skill should be used when the user asks to "write specifications", "specify an abstraction", "create contract tests", "property-based testing", "design by contract", "specification tests", or discusses how...
This skill should be used when the user asks to "write requirements", "define requirements", "create user stories", "formalize use cases", "functional requirements", "non-functional requirements", or discusses...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.