Loading...
Loading...
Found 116 Skills
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".
Use when reviewing code, pull requests, branches, diffs, or changed files for quality, correctness, security, performance, and style issues.
Write clean, readable, and maintainable code following principles from Robert C. Martin's "Clean Code" and Object Calisthenics. Use when writing, reviewing, or refactoring code to improve naming, function design, formatting, error handling, and class structure. Includes code smell detection and refactoring guidance.
Object and class design patterns following Clean Code JavaScript.
Improve code readability without altering functionality using idiomatic best practices
Module and file-structure patterns for clean JavaScript architecture.
Use when writing, fixing, editing, or refactoring TypeScript, React, or CSS code. Not for PR or diff reviews — use clean-code-reviewer for those.
Improve existing code through safe, behavior-preserving Clean Code refactoring. Use when the user asks to refactor code, clean up messy code, improve readability, simplify structure, reduce duplication, improve naming, review maintainability, or apply Clean Code principles. Do not use for broad architecture redesign unless the user asks for redesign.
Use when writing, fixing, editing, or refactoring Python tests. Enforces Clean Code principles—fast tests, boundary coverage, one assert per test.
Use when writing, fixing, or editing TypeScript with duplicated logic, magic values, unclear one-liners, mixed responsibilities, clutter, arbitrary code, or inconsistent abstraction levels.
Use when writing, fixing, or editing TypeScript comments or TSDoc, especially commented-out code, stale docs, metadata comments, redundant comments, TODO banners, or unclear comment value.
Use when naming or renaming TypeScript identifiers, especially cryptic names, ambiguous parameters, I-prefixed interfaces, Hungarian notation, misleading side effects, or requests for clearer names.