菜单
Use when adding a built-in main-process canvas plugin (the channel / dynamic-app / webview-page-control shape) — especially one gated by an experimental flag. Covers the registration points and the flag-timing landmine that has been copy-pasted three times instead of documented.
用 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-builtin-main-plugin |
| description | Use when adding a built-in main-process canvas plugin (the channel / dynamic-app / webview-page-control shape) — especially one gated by an experimental flag. Covers the registration points and the flag-timing landmine that has been copy-pasted three times instead of documented. |
An ordered procedure. Sequence + landmines only; read the three existing plugins for working precedent (src/plugins/main/channel/, dynamic-app/, webview-page-control/).
Implement MainCanvasPlugin (src/plugins/types.ts) in a new src/plugins/main/<name>/index.ts. If the plugin registers node capabilities, that contract is harness/knowledge/plugin-node-mf2.md; this skill is about the PLUGIN shell, not the node contract.
Register in BUILT_IN_MAIN_PLUGINS (src/plugins/main/built-in.ts) — the array is the activation list; not being in it means the plugin never runs.
THE flag-timing landmine (the reason this skill exists). If the plugin is gated by an experimental flag via enabledWhen, that predicate runs at plugin REGISTRATION time in the main process — before the renderer exists, so it cannot round-trip through IPC. It must read the persisted flags file synchronously from disk. All three existing plugins carry the identical hand-copied warning comment about this (channel/index.ts, dynamic-app/index.ts, webview-page-control/index.ts — the same lesson was re-learned three times, which is why it now lives here). Copy the sync-read helper pattern from any of them; do NOT invent an async/IPC-based gate — it will race the registration.
Add the flag to the registry in src/shared/experimental-features.ts — that file's own header JSDoc is the complete runbook for the flag side (registry entry, persisted path, reload-to-apply). Do not duplicate its content anywhere.
Inert-by-default posture. Follow the channel plugin's precedent (AGENTS.md Local Constraints): a built-in plugin that talks to external services should be inert unless its flag AND its config are both present. Credentials live in local settings/env, never in source — and note the secrets landmine: channel/config.ts and settings/built-in-tools-config.ts currently each carry their own encrypt/decrypt with the same Electron-safeStorage/Keychain workaround; if you need secret storage, reuse one of those rather than writing a third copy (extract a shared helper if you're the third consumer — rule of three).
Verify. pnpm --filter canvas-workspace typecheck && pnpm --filter canvas-workspace test; if the plugin registers agent-visible tools, also re-run describe-canvas.mjs (registry + name collisions).
Plugin in the array; flag in the registry; enabledWhen reads flags synchronously (no IPC); inert without flag+config; secrets (if any) reuse an existing helper; checks green.
