メニュー
Use when adding a slash command to remote-server's chat-command router. Covers the ~6 parallel registries that must stay in sync, the COMMANDS_ALLOWED_WHILE_RUNNING active-run-race decision, and the describe-remote-server passthrough parity check.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Select and run proportionate validation for changes to apps/canvas-workspace. Use when iterating on Canvas Workspace code, finishing a feature or fix, preparing release evidence, or deciding whether a full performance report is necessary.
Deep-research a topic and build a structured Pulse Canvas workspace with approved research depth, source-backed findings, progressive or final canvas creation, spatially organized frames, content nodes, and connections. Use when the user asks to bootstrap, generate, research, organize, or build an AI-created canvas.
Extend an existing Pulse Canvas frame with local, source-backed research while preserving the surrounding canvas. Use when the user asks to research, enrich, expand, verify, update, or add sources/details inside a selected or named frame, rather than bootstrapping a whole new canvas.
Operate Pulse Canvas workspaces — read user-curated context, write results, create nodes
Add or change a Pulse Canvas capability that must be available through structured agent tools and the pulse-canvas CLI. Use for cross-workspace Capability Runtime changes spanning apps/canvas-workspace, packages/canvas-cli, or packages/cli, including new live read, operate, or unsafe application actions.
Run the canvas-workspace performance evaluation, publish the latest static dashboard through the local nginx/Cloudflare Tunnel route, capture a screenshot, and summarize the report. Use when the user asks to run Pulse Canvas/canvas-workspace perf checks, deploy the performance dashboard, refresh https://jasperhu.art/apps/canvas-perf/, or send a dashboard screenshot from Feishu/remote-server.
| name | add-chat-command |
| description | Use when adding a slash command to remote-server's chat-command router. Covers the ~6 parallel registries that must stay in sync, the COMMANDS_ALLOWED_WHILE_RUNNING active-run-race decision, and the describe-remote-server passthrough parity check. |
An ordered procedure. The one real hazard is that a command's definition is spread across ~6 parallel registries and nothing but this skill (plus one parity check) keeps them in sync. FACTS live in the cited files.
Snapshot parity first. node harness/tools/describe-remote-server.mjs — the "Chat commands (N server-side · M Discord passthrough)" line and any "missing from passthrough" hard error are your baseline.
Add the handler under src/core/chat-commands/handlers/ (9 exist) and wire the case '<cmd>': in the router switch (src/core/chat-commands.ts, ~22 cases).
Update every parallel registry it belongs to — this is the landmine; each is a separate file and a miss is silent:
COMMAND_ALIASES in command-defs.ts if the command has short forms.COMMANDS_ALLOWED_WHILE_RUNNING in command-defs.ts — see step 4, this is a correctness decision, not a formality.PASSTHROUGH_SLASH_COMMANDS (adapters/discord/adapter.ts:636) AND the registration in application-commands.ts — a command absent from passthrough is unreachable as a Discord slash command (describe-remote-server hard-errors on this).help.ts so /help lists it.COMMANDS_ALLOWED_WHILE_RUNNING is an active-run-race decision. Commands in that set bypass the per-platformKey active-run guard (chat-commands.ts → runs even while a turn is in flight). That is correct for read-only/control commands (/stop, /status) but DANGEROUS for anything that mutates shared session/worktree state: /fork and /wt are in the set and can orphan or redirect an in-flight run (harness/knowledge/known-defects.md §5). Read core-lifecycle.md invariant 1 before adding a state-mutating command here — default is NOT to add it to the allowed-while-running set.
Clarification interaction. If a run can be mid-clarification, remember the next inbound message is consumed as the clarification answer (known-defects.md §3) — a command typed then may be swallowed, not executed. Don't design a command whose only escape hatch is typing it during a clarification.
Verify. node harness/tools/describe-remote-server.mjs (no new missing-from-passthrough); build + test.
The switch case + handler exist; every registry it belongs to is updated (aliases, help, README, Discord passthrough + application-commands); the allowed-while-running decision is conscious and safe; describe-remote-server shows no passthrough drift; build + test green.