Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data using Agent Zero's browser tool.
Implements CI/CD pipelines and automation. Use when setting up continuous integration, deployment pipelines, automated testing, infrastructure as code, or any automation that runs on code changes.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Manages agent context for effective AI-assisted development. Use when working on large codebases, when the agent seems to lack necessary context, when structuring CLAUDE.md or project guidance files, or when coordinating long multi-step development sessions.
Diagnoses and fixes bugs systematically. Use when encountering errors, unexpected behavior, or failing tests. Use when you need a structured approach to finding root causes rather than guessing at fixes.
Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
Git workflow and version control best practices. Use when committing code, creating branches, preparing pull requests, or managing release versioning. Use when structuring commit messages or planning a branching strategy.
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when starting from a vague idea, brainstorming a new feature, exploring design space, or stress-testing a plan before committing. Trigger phrases: "ideate", "refine this idea", "stress-test my plan", "ideate on".
Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
Reads official sources before implementing. Use when using a library, API, or framework that might have changed since training. Use when you're unsure about current API signatures, best practices, or when working with rapidly evolving tools.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
Meta-skill for selecting and applying the right skill for any task. Use when starting a task and unsure which skill to apply, or when coordinating multiple skills for a complex workflow. This is the routing brain for the entire skill set. WARNING: load this skill on-demand only — never pin it as always-active. Agent…
★not rated 5 1mo agoA95 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: