菜单
Use when handling mediated WebSocket chat events, token streaming, handoffs, tool events, or workflow questions in `packages/web` while keeping chat views dumb and state logic unit tested.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when creating, restructuring, or refining agent files, skill files, prompt files, or repository instruction files.
Use when working on agent chat behavior, system prompt construction, handoffs, context injection, or runtime behavior across packages/core and packages/service.
Shape or review ai-team agents from a hiring brief into a clear final portfolio. Use when Emily Davis or another agent needs to turn a role idea into a strong agent with the right personality, reporting line, handoffs, runtime metadata, and supporting skills.
Use when working on AST analysis, tree-sitter parsing, symbol or complexity inspection, diff generation, structured edit proposals, or code-aware backend editing workflows.
Use when an agent needs to run commands reliably across PowerShell, pwsh, cmd, bash, or sh; choose between exec, spawn, and execFile; debug shell-specific failures; or normalize cwd, env, quoting, and output handling for cross-platform command execution.
Use when Adrian or another research-oriented teammate needs to extract content from PDFs or long documents, convert it to Markdown, collect supporting URLs, and produce a source-backed briefing the team can learn from.
| name | mediated-chat-runtime-store |
| description | Use when handling mediated WebSocket chat events, token streaming, handoffs, tool events, or workflow questions in `packages/web` while keeping chat views dumb and state logic unit tested. |
Use this skill when chat state is driven by mediator events rather than simple request/response fetching.
This includes:
ARCHITECTURE.mdCOPILOT-CONTEXT.mdpackages/service/src/contracts.tspackages/api-server/src/server.tspackages/api-server/src/index.tspackages/web/src/components/ChatPanel.tsx.ai-team/instructions/frontend-state-architecture.instructions.md.ai-team/skills/agent-runtime-behavior/SKILL.md.ai-team/skills/service-orchestration-runtime/SKILL.md.ai-team/skills/zustand-presenter-split/SKILL.mdClassify incoming chat flow as mediated runtime events, not as plain fetched records.
Typical events include:
statustokentoolquestionhandoffdoneerrorDo not let presentational chat components own:
Keep those concerns in controller hooks and runtime stores.
Use Query or snapshot loading for persisted session data. Use Zustand or a small runtime state machine for the active stream.
A good split is:
Whenever practical, model the runtime update path with pure helpers such as:
applyMediatorEvent(state, event)appendToken(state, text)startPendingQuestion(state, question)transitionHandoff(state, event)This makes chat runtime logic far easier to unit test.
Unit test at least: