Loading...
Loading...
Found 973 Skills
State-machine driven orchestrator for structured software development. Invoke when user wants to develop features, fix bugs, or refactor code. Triggers: 'build a feature', 'fix this bug', 'implement', 'develop', 'refactor'.
This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability. Use this for identifying code smells, architectural issues, dependency problems, missing documentation, security vulnerabilities, and creating comprehensive technical debt documentation.
Use this skill whenever you are implementing a feature using TDD.
Analyze Python code for style improvements including naming, structure, nesting, and cognitive load reduction
Use when implementing features with test-driven development, writing tests before code, building domain-rich business logic, or following hexagonal architecture
Vertical-slice TDD for any production code. One test → one impl → repeat. Tests verify behavior through public interfaces, not internals. Use when implementing any feature, bugfix, or behavior change.
This skill embodies the principles of "Clean Code" by Robert C. Martin (Uncle Bob). Use it to transform "code that works" into "code that is clean."
Refactors specified code to improve clarity, reduce duplication, or align with the project's architectural patterns — without changing external behavior. Invoked when the user asks to refactor, clean up, simplify, or restructure code.
Automatically add or improve type annotations in legacy Python code. Use to improve code readability, IDE support, and catch type errors early.
Você é uma Arquiteta de Software Sênior especialista em Clean Code e engenharia de software. Use esta skill sempre que o usuário pedir para revisar, criticar, refatorar ou avaliar trechos de código, funções, classes, módulos ou arquiteturas inteiras. Ative também quando o usuário mencionar problemas como "código duplicado", "classe muito grande", "difícil de manter", "código espaguete", "muita dependência", "quero melhorar esse código", "está violando SOLID?", "como refatorar isso?", "esse código está limpo?", "tem code smell aqui?", "como aplicar injeção de dependência?", "preciso de um code review", ou qualquer variação dessas frases. Ative inclusive quando o usuário perguntar sobre boas práticas de design, padrões de código, ou pedir explicações sobre KISS, DRY, YAGNI, TDA, SOLID e seus subprincípios. Se estiver no SynkOS, chame `pane_set_identity` com skill="clean-code-architect" e role="architect".
Groups components into logical domains for service-based architecture. Use when creating component domains, grouping components by business functionality, planning domain services, analyzing component relationships, or when the user asks about domain grouping, component domains, or domain identification.
Prioritizes the use of new features available in Python 3.12 and later versions.