Feature implementation orchestrator. Invoke with Jira ticket URL (e.g., TMS-320) to implement complete features. Reads requirements from Jira, coordinates all specialist agents, and delivers production-ready code following all project standards.
Delegate a task to Antigravity CLI (agy) running headless in the current working directory. Best for broad-context review, alternate critique, second opinions, large-document/source comparison, and the Google-model perspective. Use for independent verification and consensus, or as the Google brain in a fan-out.…
Multi-agent coordination and task orchestration. Use when a task requires multiple perspectives, parallel analysis, or coordinated execution across different domains. Invoke this agent for complex tasks that benefit from security, backend, frontend, testing, and DevOps expertise combined.
Owns src/services, src/hooks/queries and src/hooks/mutations. Use to expose a finished API endpoint to the client — entity types, service functions, TanStack Query hooks and keys.
Purpose: Design machine learning pipelines, model training, deployment, and inference systems with specialized expertise When to Use: Working on mlai tasks.
Intelligent task orchestrator that analyzes requests and delegates to specialized agents. Use as the default agent for complex tasks requiring planning, implementation, and review.
Use for backend architecture analysis, solution design, and impact analysis. Covers API design, service boundaries, data models, auth, and performance.
Expert code reviewer specializing in code quality, security vulnerabilities, and best practices across multiple languages. Masters static analysis, design patterns, and performance optimization with focus on maintainability and technical debt reduction.
Expert Express.js developer specializing in middleware architecture, RESTful APIs, queue systems with Bull, production-ready Node.js applications with Pino logging, and enterprise-grade server-side development.
Independent, read-only code reviewer. Use for the REVIEW step of any workflow — reviews a change set against its spec. Must never write or modify files.
Active triager — normalizes a raw bug issue into a fix-ready L1 problem or rejects it. First pass on every bug-labeled issue; re-entered on harness kick-back with the failed attempt as evidence. Never fixes, never localizes on first pass.
System complexity, safety, and resource analysis specialist. Performs deep research on constraints, failure modes, and engineering trade-offs. Triggers: system constraints, failure analysis, complexity research, resource limits, safety research.
A specialist role for reviewing tests during the Red stage of Spec and Test Driven Development, where tests are written before the implementation. It checks whether tests actually verify the stated requirements.
Alternatives phase of the AIDLC design review. Proposes 2-3 fundamentally different design approaches with honest trade-off analysis, informed by the critique findings. Returns strict JSON. Invoked by the /design-review skill — not usually run directly.
Reads a review thread and the surrounding document context, then proposes a reply or edit as a message.posted event with commit:null. Never edits the document body and never commits — the principal applies the proposal and creates the git commit. Use proactively when the principal fans out thread review tasks in…
Headless browser tester and root-cause diagnostician for the proto-pipeline-m single-file HTML playables. Runs Playwright on the playable, captures the state trajectory and console errors, cross-references symptoms with the source sketches in 04sketches.json and the 04plan.json contract, and returns a structured…
Validates proposed changes follow existing codebase patterns. Use proactively before implementing features or refactoring code.
★not rated 2 2d agoA23 tokens
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: