xagent

Guidelines for writing Go tests. Apply when creating or modifying test files.

Execute an already-agreed plan by delivering it as a stack of "layer cake" PRs — one xagent task per PR, strictly one at a time. Use when the design is settled (usually an accepted proposal) and the job is to build it. You delegate each layer to a task, review the PR it opens, and the human merges. A merge is the go signal to start the next layer. Feedback on a PR — yours or the user's — is relayed back to the task (which wakes on the PR event) rather than fixed by hand. Mute all channel notifications and unmute only the tasks you create. Track progress in a GitHub issue with a checkbox per layer so the work can be resumed after context loss.

Create a design proposal for a feature or change. Use when the user wants to plan or design something before implementing it.

Act as an engineering manager who delegates implementation to xagent tasks. Use for sessions where the user wants you to design, delegate, and review work rather than write production code yourself. You scope work, kick off xagent tasks, and review the proposals and PRs they produce — requesting changes by commenting on the PR and tagging the author.

Create xagent tasks using the MCP tools. Use when the user wants to create a task for the xagent system.

Guidelines for working with the Connect RPC (gRPC) API. Apply when modifying proto definitions, implementing server handlers, or creating API clients.

Web UI development guidelines for the v2 React UI in webui/. Apply when working on files in webui/, creating React components, or using TanStack Router/Query.