ワンクリックで
daemon-development
Use when implementing daemon route, service, storage, worker, or injector changes with a test-first workflow
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when implementing daemon route, service, storage, worker, or injector changes with a test-first workflow
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | daemon-development |
| description | Use when implementing daemon route, service, storage, worker, or injector changes with a test-first workflow |
Use this skill while adding or refactoring daemon behavior.
packages/daemon/test/*.app, storage, worker, notification-service, adapters).ack then local processing).command, ack, commandResult).npm run --workspace @pigeon/daemon test
npm run --workspace @pigeon/daemon typecheck
npm run test
npm run typecheck
CommandDeliveryAdapter interface lives in adapters/. New delivery transports implement it.createAdapter factory for routing tests; inject exec for nvim subprocess tests (avoid real nvim in CI).Expected:
Use when deploying pigeon code changes across all machines after merging to main
Use when you need to understand worker architecture, endpoint flow, and command routing behavior before making changes
Use when you need to understand daemon route flow, storage model, worker connectivity, and command injection architecture before making changes
Use when you need to understand the OpenCode plugin event lifecycle, session state transitions, and daemon API contracts
Use when developing or refactoring OpenCode plugin handlers, tests, and daemon integration payloads
Use when you need to understand the swarm IPC subsystem — tables, routes, the per-target arbiter, the session→directory registry, and the wire envelope — before changing it