Use when the user asks to research, investigate, look up, or understand something — orchestrates MCP servers (perplexity/exa/deepwiki/context7), agy-agent, and OMO agents (explore/librarian/oracle/multimodal-looker) with optional Max Mode for parallel multi-lane synthesis

Use when the user reports a bug, error, test failure, or unexpected behavior — routes through investigation, hypothesis testing, and verified fix with structured evidence collection

Implements a use case's backend: FastAPI router, Pydantic request/response schemas, service/domain layer, and SQLAlchemy models/queries. Use when the user asks to "implement the backend for UC-xxx", "build the API endpoint", "add a FastAPI route", "write the service layer", or mentions FastAPI implementation, Pydantic schemas, or SQLAlchemy queries for a specific use case.

Writes pytest unit and integration tests for a use case's backend, against an ephemeral Postgres container, and updates the use-case-to-test traceability matrix. Use when the user asks to "write tests for UC-xxx", "add pytest coverage", "test the backend", or mentions unit tests, integration tests, or pytest for a specific use case.

Implements a use case's frontend: a React view, form, or grid wired to the backend API, covering the main flow and every alternative/failure flow. Use when the user asks to "implement the frontend for UC-xxx", "build the React view", "wire up the form", "add the page for", or mentions React implementation for a specific use case.

Scaffolds or extends a Terraform module for this project's AWS infrastructure, wired to input.yaml, tagged per the cost-allocation strategy, and following least-privilege IAM. Use when the user asks to "create a Terraform module", "provision the VPC/Aurora/Lambda/Cognito", "add infrastructure for", or mentions Terraform, IaC, or AWS resource provisioning for this project.

Writes Playwright end-to-end functional tests and visual regression baselines for a use case, and updates the use-case-to-test traceability matrix. Use when the user asks to "write E2E tests for UC-xxx", "add Playwright coverage", "add a visual regression test", or mentions end-to-end testing or screenshot testing for a specific use case.

Creates versioned Alembic migration scripts with tables, columns, primary keys, foreign keys, unique and functional constraints (e.g. case-insensitive uniqueness), and reference-data seeds, all derived from the entity model. Use when the user asks to "create a migration", "add a database migration", "write an Alembic migration", "add a column", "add a foreign key", "seed reference data", or mentions Alembic, schema migration, or database schema changes.

Interactive developer experience plan review. (gstack)

Use when the user gives a short, rough, or one-line idea for an app, tool, script, or feature and wants it built end-to-end without being asked clarifying questions. Triggers - "build me...", "create an app that...", "I want a tool for...", "quick app for...", minimal specs, seed ideas.

Use when the user has an idea for an app, tool, or feature and wants to be interviewed in depth first — answering structured clarifying questions until the requirements are fully pinned down — before it gets built end-to-end. Triggers - "ask me questions then build", "interview me about my idea", "help me spec this out and build it", vague ideas the user wants to shape interactively.

Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set up monitoring", "show me the catalog", "what can I provision", "browse providers", "add an LLM provider", "configure model provider", "add email sending", "set up search", "add a message queue", "set up object storage", "add feature flags". Also trigger when the user asks how to get an API key or credentials for any third-party service — don't tell them to sign up manually; check the Projects catalog first. Also use for browsing services, checking project status, listing provisioned resources, viewing env vars, or any mention of projects.dev or adding/provisioning/connecting a cloud service.

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.

Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.

PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.

Spring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services.

Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.

Keep gbrain current with this repo's code and refresh agent search guidance in CLAUDE.md. Wraps the gstack-gbrain-sync orchestrator with state (gstack)