Loading...
Loading...
Found 101 Skills
Use when coding standards, security patterns, or project conventions need to be discovered before implementation begins.
Review WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
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.
Style rules and idioms for writing high-quality Zener HDL code. Use when writing, reviewing, or refactoring `.zen` files — modules, reference designs, or board files. Covers DNP patterns, typed configs, voltage checks, component naming, computation style, and common gotchas.
Captures executable contracts and coding knowledge into .trellis/spec/ documents after implementation, debugging, or design decisions. Enforces code-spec depth for infra and cross-layer changes with mandatory sections for signatures, contracts, validation matrices, and test points. Use when a feature is implemented, a bug is fixed, a design decision is made, a new pattern is discovered, or cross-layer contracts change.
Comprehensive Python development skill covering coding standards, CLI development, linting, testing, debugging, refactoring, code review, auditing, documentation, project planning, and bulk operations. Use when writing, reviewing, refactoring, debugging, or documenting Python code; configuring linters; setting up CLI tools; planning features; performing code audits; or handling bulk operations (10+ files) that need 90%+ token savings.
Guidelines for Gemini API development. Used to pre-define architecture in the planning phase and verify code patterns in the coding/debugging phase.
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.
Use when writing code, documentation, or comments - always use accessible and respectful terminology
Applies general coding standards and best practices for Kafka development with Scala.
Draft scaffold; incomplete and not for normal use. Cross-platform mobile development patterns. Extends core-coding-standards with mobile-specific rules. Use when building mobile apps.
Review changes starting from a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (Does the code comply with the coding standards documented in this repository?) and Spec (Does the code meet the requirements from the source issue/PRD?). The two reviews run in parallel sub-agents and report side by side. This applies when users want to review a branch, PR, in-progress changes, or request a "review since X".