Use this agent when analyzing metrics, generating insights from data, creating performance reports, or making data-driven recommendations. This agent excels at transforming raw analytics into actionable intelligence that drives studio growth and optimization. Examples:\n\n \nContext: Monthly performance review needed.
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.
PROACTIVELY use this agent when approaching B2B launch milestones, enterprise release deadlines, or B2B go-to-market activities. This agent specializes in coordinating business launches, managing enterprise release processes, and executing B2B go-to-market strategies within the 6-day development cycle. Should be…
A truly conversational, adaptive, and agentic subagent that partners with humans to co-create rigorous, multi-perspective technical specs using dynamic memory graphs, adaptive workflows, and explicit multi-role analysis.
Use proactively before a consequential plan, architecture choice, migration, launch, or strategy is committed. Adversarially review the reasoning, hidden assumptions, and cheaper alternatives. Read-only; use Claude Code's built-in /code-review for routine code diffs.
Use proactively before implementing a visual or UI change that needs a clear specification. Produce layout and hierarchy, color and type systems, motion choreography, brand treatment, image-generation prompts, or a design brief that a builder can execute without guessing.
Use proactively when the target behavior and scope are clear enough to implement a bounded change, run the smallest relevant verification, and return the completed working-tree diff without reopening product or architecture strategy.
Specialist for optimizing Notion workspaces using information architecture best practices, second-brain methodologies, and database design patterns. Use proactively for Notion workspace analysis, database schema design, PARA/GTD/Zettelkasten implementation, and template creation.
Proactively use for comprehensive Linear project management, release planning, dependency analysis, and project reorganization. Specialist for managing complex issue hierarchies, multi-release roadmaps, and cross-team dependencies.
Use proactively for designing, creating, reviewing, and improving Claude Code slash commands. Specialist for developing and validating robust, reusable slash commands that extend Claude Code's capabilities.
VPS maintenance agent. Use when the user asks about server status, wants to check their deployments, apply OS updates, or run maintenance on Pulse, Curia, or any registered server. Handles status checks (read-only) and updates/reboots (write) based on intent.
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Gemini CLI integration agent for development guidance, code reviews, and best practices analysis. Use PROACTIVELY when you need a second AI perspective on code quality, architecture decisions, or development patterns.
Orchestrates Gemini CLI and Copilot CLI agents for comprehensive research, development, and analysis tasks. Coordinates multiple AI perspectives, consolidates findings, and provides consensus-based recommendations. Use PROACTIVELY for complex tasks requiring multi-agent collaboration.
Use after staging changes with git add, before running git commit. Reads the staged diff and drafts a Conventional Commits message that describes what actually changed. Use proactively whenever the user is about to commit.
Use proactively before merging code that touches database queries, cloud resources, background jobs, third-party API calls, or hot paths. Flags patterns that look fine in dev but become expensive at production scale. Also use on demand for cost reviews of a codebase or infrastructure-as-code.
Use proactively when a dependency file changes (package.json, requirements.txt, Pipfile, pyproject.toml, Cargo.toml, go.mod, Gemfile, pom.xml, build.gradle), or on demand for a periodic audit. Identifies outdated, vulnerable, unused, duplicated, and license-incompatible dependencies.