bullpen

Hand a task directly to Bastion, a Security Engineer.

Hand a task directly to Compass, a SEO Specialist.

Hand a task directly to Comet, a Data Intern.

Hand a task directly to Riot, a Social Media Manager.

Hand a task directly to Sentinel, a SRE.

Use this agent when the user types /ae or asks for account executive work — e.g., qualify this inbound deal with MEDDIC. The agent covers sales process, MEDDIC, discovery, negotiation, forecasting. Examples — <example>user "qualify this inbound deal with MEDDIC" → Bishop produces a recommendation in the standard 5-options + ⭐ pick format and references project conventions surfaced from bullpen-memory.</example> <example>user "/ae <task>" → direct invocation; Bishop works in their lane and hands off if the task is out of scope.</example>

Use this agent when the user types /ai or asks for ai/llm engineer work — e.g., build a RAG pipeline over our docs. The agent covers OpenAI, Anthropic, LangChain, LlamaIndex, Pinecone, and more. Examples — <example>user "build a RAG pipeline over our docs" → Helios produces a recommendation in the standard 5-options + ⭐ pick format and references project conventions surfaced from bullpen-memory.</example> <example>user "/ai <task>" → direct invocation; Helios works in their lane and hands off if the task is out of scope.</example>

Use this agent when the user types /api or asks for api engineer work — e.g., design the /payments REST contract. The agent covers REST, GraphQL, tRPC, OpenAPI, Postman, and more. Examples — <example>user "design the /payments REST contract" → Conduit produces a recommendation in the standard 5-options + ⭐ pick format and references project conventions surfaced from bullpen-memory.</example> <example>user "/api <task>" → direct invocation; Conduit works in their lane and hands off if the task is out of scope.</example>

Use this agent when the user types /arvr or asks for ar/vr engineer work — e.g., build a Quest passthrough demo. The agent covers Unity XR, WebXR, ARKit, ARCore, Meta SDK, and more. Examples — <example>user "build a Quest passthrough demo" → Mirage produces a recommendation in the standard 5-options + ⭐ pick format and references project conventions surfaced from bullpen-memory.</example> <example>user "/arvr <task>" → direct invocation; Mirage works in their lane and hands off if the task is out of scope.</example>

Use this agent when the user types /ash or asks for backend intern work — e.g., log learnings from the BE work just shipped. The agent covers observation, summarization, pattern extraction. Examples — <example>user "log learnings from the BE work just shipped" → Pebble produces a recommendation in the standard 5-options + ⭐ pick format and references project conventions surfaced from bullpen-memory.</example> <example>user "/ash <task>" → direct invocation; Pebble works in their lane and hands off if the task is out of scope.</example>

Use this skill after a bullpen agent completes a task to extract 0-3 durable learnings (decisions, patterns, preferences, failures, or code snippets) and write them to the project's local memory store (`<project>/.bullpen/memory.json`) under that agent's namespace. The matching Intern agent runs this. Keep each learning self-contained and project-scoped.

Use this skill before any bullpen agent runs to retrieve relevant past learnings from the project's local memory store. Trigger when an agent activates and needs context from prior sessions — preferences, decisions, patterns, failures, or code snippets stored in their namespace. Memory lives in `<project>/.bullpen/memory.json` — per-project, plain JSON, no daemons.

Use when designing or reviewing any state-changing HTTP endpoint (POST, PUT, PATCH, DELETE) — covers idempotency keys, request deduplication, retry safety, exactly-once semantics over at-least-once delivery, and the Stripe/standard idempotency-key pattern. Use anytime an endpoint creates resources, charges money, sends notifications, or has any non-reversible side effect.

Use when working with React Server Components — choosing between Server and Client components, designing the server/client boundary, debugging hydration mismatches, fetching data on the server, using Server Actions, optimizing initial load, or migrating from a Pages Router or pure client-side React app to App Router + RSC.

5 hooks across 5 events