xin-yi33

using-agent-crew

Use when starting work on a coding-agent product — creating one from scratch or changing an existing one (headless core, JSON-RPC app-server, TUI/GUI/IDE, harness, sandbox, protocol, PRD, evals). Use before clarifying questions or editing. Use when unsure which engineer owns the change. Use when the user runs /using-agent-crew.

agent-core-boundaries

Use when changing the headless session façade, app-server, or CLI/GUI shared contracts; when a new surface might fork the agent; or when UI would import core. Use when the user mentions 架构, protocol, JSON-RPC, headless, ACP, app-server.

agent-quality

Use when evaluating a coding-agent product, gating a release, or when the user mentions evals, Agent Quality, 评测, 模块测试, 整体测试, trajectory, LLM judge, regression fixture, or independent verification of agent behavior. Use after an implementer claims done. Not for ordinary app unit tests with no agent loop.

agent-runtime

Use when changing the agent loop, tool calling, streaming, interrupt, prompts, compaction, turn routing, or evals of harness behavior. Use when the user mentions harness, tool loop, 中断, 流式, turn router, prewarm.

agent-surface

Use when changing TUI, desktop, IDE extension, protocol-client, streaming chat UI, or approval dialogs. Use when the user mentions TUI, GUI, 前端, 桌面, protocol-client, Electron, VS Code.

local-agent-process-isolation

Use when changing shell or file tool execution, OS sandbox policies, Windows or POSIX isolation, MCP stdio process lifetime, or approval versus auto-allow. Use when the user mentions sandbox, 沙箱, Seatbelt, bubblewrap, Landlock, Job Object, write whitelist.

spec-author

Use when user intent is vague, when a feature needs a PRD, spec, or acceptance criteria, or when writing development documents before implementation. Use when the user mentions 产品, PRD, 规格, 需求, 验收, or “先写文档”.