Loading...
Loading...
Found 77 Skills
Enforces the project's core TypeScript standards including explicit typing, import organization, class member ordering, and code safety rules. ALWAYS apply when creating, modifying, or reviewing any TypeScript (.ts/.tsx) file.
Remove AI-generated code slop from the current branch. Use when the user says "deslop" or asks to clean up AI slop, remove AI code patterns, or clean the branch before committing.
Remove AI-generated code slop from a branch. Use when cleaning up AI-generated code, removing unnecessary comments, defensive checks, or type casts. Checks diff against main and fixes style inconsistencies.
Go naming conventions for packages, functions, methods, variables, constants, and receivers from Google and Uber style guides. Use when naming any identifier in Go code—choosing names for types, functions, methods, variables, constants, or packages—to ensure clarity, consistency, and idiomatic style.
Creates, updates, and manages Agent Skills following the Claude Code style. Use this skill when the user wants to add a new capability, create a new skill, or modify an existing skill.
Remove AI-generated code slop and clean up code style
Senior Python developer. Use when writing, reviewing, or refactoring Python code. Enforces idiomatic Python, type hints, and modern patterns.
Convenciones de formato: framework Diátaxis, español/LATAM, estilos de código, Conventional Commits.
Apply the "How I Made Your Machine" coding style guide to implementation, refactoring, and code review tasks across TypeScript, Rust, and Python. Use when a request asks for this style guide, when improving maintainability and type safety, when modeling domain concepts with explicit variants/types, or when enforcing behavior-first testing.
Style, review, and refactoring standards for Python codebases with strong typing, explicit error handling, and maintainable module boundaries. Use when Python artifacts are created, changed, or reviewed and Python-specific quality rules must be enforced.
Unify EliteForge Java coding specifications, covering code style, comment specifications, POJO/enum/util classes, control statements, logging, concurrency, MyBatis-Plus, transactions, Spring, inter-service calls, Maven, databases, gateways, interface management, project structure, etc. Use this when users mention terms like "Java specification", "coding specification", "code style", "enum writing", "POJO specification", "logging specification", "transaction processing", "inter-service calls", "interface prefix", "domain model", "Maven version", "internationalization".
Apply Spatie's Laravel and PHP coding standards for any task that creates, edits, reviews, refactors, or formats Laravel/PHP code or Blade templates; use for controllers, Eloquent models, routes, config, validation, migrations, tests, and related files to align with Laravel conventions and PSR-12.