@prismer/runtime 2.0.8 → 2.2.55

package/built-in-skills/agent-coordination/SKILL.md

@@ -1,5 +1,6 @@
 ---
 name: agent-coordination
+scope: common
 description: Find other agents, list participants in a conversation, send routed messages, attach files, and recover earlier conversation context (history / resolve a fuzzy reference / read a quoted message / read compressed summaries). Use whenever you need to delegate to another agent, address a peer in a multi-agent conversation, send a message that carries a file, or pull context that scrolled out of your prompt window. Executes via `cloud discover`, `cloud im conversations`, `cloud send`, `cloud file send`, `cloud conversation history|resolve-identifier|summary`, and `cloud quote read` CLIs.
 ---
 
@@ -16,7 +17,16 @@ If you have an inline `Task` / `Subagent` / `ParallelAgents` / fan-out tool avai
 - never @-mention the supposed assignee in the conversation
 - finish in seconds, which to the user looks like you did the work yourself (because you did)
 
-For peer-agent delegation, the canonical paths are **`cloud task create --assignee-name <peer>`** (tracked deliverable; see the `tasks` skill) and **`cloud send <peer-username>`** (ad-hoc message; see below). Anything else — including inline subagents — is the wrong tool, and the user will notice (the supposed assignee was never @-mentioned in chat, and your response came back too fast).
+For peer-agent delegation, the canonical paths are **`cloud task create --assignee-name <peer>`** (tracked deliverable; see the `tasks` skill) and **`cloud send <peer-username> "<message>" --by-username --workspace-id "$PRISMER_WORKSPACE_ID"`** (ad-hoc message; see below). Anything else — including inline subagents — is the wrong tool, and the user will notice (the supposed assignee was never @-mentioned in chat, and your response came back too fast).
+
+### `cloud task create` vs `cloud send` — 选哪条 + 结果回流
+
+| 你想要的 | 用 | 结果怎么回来 |
+| --- | --- | --- |
+| **可追踪委派**（要交付物、要进度、要落看板） | `cloud task create --assignee-name <peer>` | **不自动回流**：peer 在独立 context 跑，产物落 task 卡；你须 `cloud task get <taskId>` 主动拉（`status=completed` 才算成）。详见 `tasks` skill 的「结果回流」段。 |
+| **即兴消息**（问一句、转一份、打个招呼） | `cloud send <peer-username> "<message>" --by-username --workspace-id "$PRISMER_WORKSPACE_ID"` | peer 若在**同一会话**，回复直接出现在这条会话里；不落看板、不可追踪。 |
+
+口诀：**要结果 / 要看板 → `cloud task create` 然后 `cloud task get` 取**；只是说句话 → `cloud send`。两者都不是 inline subagent。
 
 ## When to use
 
@@ -30,51 +40,62 @@ For peer-agent delegation, the canonical paths are **`cloud task create --assign
 ### Discover (workspace-wide directory)
 
 ```bash
-cloud discover                                    # all visible agents
-cloud discover --capability code-review           # filter by capability
-cloud discover --online-only                      # only online agents
+cloud discover --workspace-id "$PRISMER_WORKSPACE_ID"                                  # all agents in this workspace
+cloud discover --workspace-id "$PRISMER_WORKSPACE_ID" --capability code-review         # filter by capability
+cloud discover --workspace-id "$PRISMER_WORKSPACE_ID" --online-only                    # only online agents
 cloud im contacts                                 # your contact list
 ```
 
+`cloud discover` is a workspace-scoped Agent Registry contract: every result
+is backed by an AgentCard in the requested workspace and carries its routing
+`userId`. Human accounts and agents from other workspaces are contract
+violations. When the target is already in the current conversation, prefer the
+conversation members listing below instead of searching the wider workspace.
+
 ### List participants in a conversation (scoped)
 
 ```bash
 cloud im conversations                            # all your conversations
 cloud im conversations --unread                   # unread only
-cloud im conversations <conversationId> --members # agents + humans in this conversation
+cloud im conversations <conversationId> --members --json # exact agent + human participant fields
 ```
 
 ### Send a message
 
 ```bash
 # Direct message to an agent
-cloud send <to-username> "Please review the PR"
-cloud send <to-username> "## Report" -t markdown
-cloud send <to-username> --reply-to <messageId> "Acknowledged"
+cloud send <to-username> "Please review the PR" --by-username --workspace-id "$PRISMER_WORKSPACE_ID"
+cloud send <to-username> "## Report" -t markdown --by-username --workspace-id "$PRISMER_WORKSPACE_ID"
+cloud send <to-username> "Acknowledged" --reply-to <messageId> --by-username --workspace-id "$PRISMER_WORKSPACE_ID"
 
 # Conversation-scoped (multi-agent group)
 cloud im groups send <groupId> "Team update: feature shipped"
 
 # With routing metadata
-cloud send <to-username> "Need approval" --conversation-id <convId>
+cloud send <to-username> "Need approval" --conversation-id <convId> --by-username --workspace-id "$PRISMER_WORKSPACE_ID"
 ```
 
 ### Send with attached file
 
 > **决定怎么交付文件 — 先读这条:**
 >
-> - **你这次任务的最终交付物（要跟你的回复一起出现的产物）** → 写进
->   `${PRISMER_ARTIFACTS_DIR}`（当前 dispatch 的 `artifacts/` 目录）。
->   daemon artifacts-watcher 会自动归档并把 assetId **挂到你这条 dispatch
->   回复上**，于是「文件 + 你的总结文字」是**同一条消息**。这是默认路径。
+> - **用户明确要求随当前回复交付的文件** → 写入
+>   `${PRISMER_ARTIFACTS_DIR}`（当前 dispatch 的 `artifacts/` 目录），然后显式运行
+>   `cloud deliver <abs-path>`。auto-scan 默认 OFF；只写文件不算交付。
+> - **看板 task 的文件产物** → 显式运行 `cloud task attach <abs-path>`，并以
+>   命令返回的 assetId 为准。
 > - **`cloud file send` 会另起一条独立消息**（先于/晚于你的回复单独落），
 >   只适合「对话进行中临时丢个文件给对方看」这种 ad-hoc 分享，**不要**用它
 >   交付任务最终产物 —— 否则用户会看到「一条只有文件的消息」+「一条只有
 >   文字的消息」分裂开（release201/30 §4 + §7）。
 
 ```bash
-# 默认：最终交付物写进 artifacts/，随你的回复单条附带（无需任何 send 命令）
-cp ./report.pdf "${PRISMER_ARTIFACTS_DIR}/"     # 然后正常回复即可（平台自动收尾）
+# 当前回复的文件交付：写入 artifacts/ 后显式 deliver
+cp ./report.pdf "${PRISMER_ARTIFACTS_DIR}/"
+cloud deliver "${PRISMER_ARTIFACTS_DIR}/report.pdf"
+
+# 看板 task 文件产物：显式 attach
+cloud task attach "${PRISMER_ARTIFACTS_DIR}/report.pdf"
 
 # ad-hoc 临时分享（会另起独立消息 — 不要拿来交付最终产物）
 # 文字说明用 -c/--content（不是 --message —— 后者不存在，commander 会报
@@ -84,14 +105,15 @@ cloud file send <conversationId> ./report.pdf
 cloud file send <conversationId> ./report.pdf --content "Latest numbers, please review"
 cloud file send <conversationId> ./image.png --mime image/png
 
-# On hermes (no per-dispatch env): also pass --run-id "<run_id>" (copied from
-# <execution_context>) so the daemon proxy activates. Spawn adapters
-# (claude-code / codex) have the env set and don't need it.
-cloud file send <conversationId> ./report.pdf --run-id "<run_id>"
+# 常态（含 hermes）：直接 `cloud file send <conversationId> <path>` 即可——daemon
+# (release203/15c) 按 agent 身份自动关联你当前的 dispatch。仅当你要对另一个
+# (非当前) dispatch 交付、或 daemon 报 409 歧义时，才从 <execution_context> 抄
+# --run-id "<run_id>" 传入。Spawn 适配器 (claude-code / codex) env 已注入。
+cloud file send <conversationId> ./report.pdf --run-id "<run_id>"  # 仅跨-dispatch / 409 时
 
 # Or upload first, then send by asset id
 cloud file upload ./report.pdf                    # → returns assetId / uploadId
-cloud send <to-username> "See attached" --asset-id <assetId>
+cloud send <to-username> "See attached" --asset-id <assetId> --by-username --workspace-id "$PRISMER_WORKSPACE_ID"
 ```
 
 ### Attach a file to a message you ALREADY sent (`cloud attach`)
@@ -106,11 +128,11 @@ cloud send <to-username> "See attached" --asset-id <assetId>
 ```bash
 cloud attach <messageId> ./addendum.pdf
 
-# On hermes (no per-dispatch env): also pass --run-id "<run_id>" and
-# --conversation-id "<conversation_id>" (both copied from <execution_context>)
-# so the daemon proxy activates + the attach route knows which thread the
-# message lives in. Spawn adapters (claude-code / codex) have the env set.
-cloud attach <messageId> ./addendum.pdf --run-id "<run_id>" --conversation-id "<conversation_id>"
+# 常态（含 hermes）：直接 `cloud attach <messageId> <path>` 即可——daemon
+# (release203/15c) 按 agent 身份自动关联你当前的 dispatch（含 conversation）。
+# 仅当你要对另一个 (非当前) dispatch 操作、或 daemon 报 409 歧义时，才从
+# <execution_context> 抄 --run-id / --conversation-id 传入。
+cloud attach <messageId> ./addendum.pdf --run-id "<run_id>" --conversation-id "<conversation_id>"  # 仅跨-dispatch / 409 时
 ```
 
 ### Read earlier conversation context (on demand)
@@ -168,19 +190,19 @@ prismer session checkpoint restore <runId>   # re-apply a saved snapshot
 
 ## Workflow (delegating to another agent)
 
-1. **List conversation participants first.** `cloud im conversations <convId> --members` returns the `agents` array with `username`, `id`, `displayName`, `agentType`, `capabilities`. Don't `discover` if the target is already in the conversation — it leaks agents outside the routing scope into your candidate set.
-2. **Pick the target.** Match on capability + status. Exclude your own username. If multiple match, pick the most specific capability and surface the choice to the user if unclear.
+1. **List conversation participants first.** `cloud im conversations <convId> --members --json` returns a `participants` array. Each item has `{ id, role, user: { id, username, displayName, role, agentType } }`; it does not contain AgentCard capabilities or status. Don't `discover` if the intended target is already identifiable in this conversation.
+2. **Pick the target.** For an existing participant, select an agent by `user.role === "agent"` and use its exact `user.id` or `user.username`; exclude yourself. If the request instead requires capability/status-based selection, use the workspace-scoped Agent Registry with `cloud discover --workspace-id "$PRISMER_WORKSPACE_ID"`.
 3. **Compose a routed message** with: requested action, context, constraints, expected output. Don't bury the ask in pleasantries.
-4. **Send with the exact `to-username`** the listing returned. Don't transform "@Alice" → "alice" by yourself — use the exact string the service returned.
+4. **Send with the exact `username`** the listing returned via `cloud send <username> "<message>" --by-username --workspace-id "$PRISMER_WORKSPACE_ID"`. Don't transform "@Alice" → "alice" by yourself — use the exact string the service returned. Alternatively, pass the discovered `userId` directly and omit `--by-username`.
 5. **Check the return value.** `cloud send` may return `{ ok: false, error: 'agent_not_found' }` even when you got the username from listing (the agent may have left between calls). If `ok: false`, surface the error; don't pretend dispatch succeeded.
 
 ## Workflow (file attachment)
 
 1. Confirm the file exists locally and is the artifact the user should receive.
-2. Prefer writing new outputs under `PRISMER_ARTIFACTS_DIR` (the current dispatch's `artifacts/` dir) — the daemon artifacts-watcher auto-archives every file there as an IMAsset and attaches the IDs to your dispatch reply. See release201/30 §4 for the full pipeline.
-3. Use this skill for **existing files elsewhere** or when you need an explicit message title alongside the attachment.
-4. Record the uploaded asset ID returned by the service.
-5. Mention the attachment in the user-facing reply **only after** the send/queue succeeded.
+2. Follow the Runtime carrier directive first. An inline PKF is not a file attachment and must not create a parallel file.
+3. For an explicitly requested file, write new output under `PRISMER_ARTIFACTS_DIR`, then run `cloud deliver <abs-path>` for the current reply or `cloud task attach <abs-path>` for a task. Auto-scan is OFF.
+4. Use `cloud file send` for **ad-hoc conversation sharing**, or `cloud attach` to add a file to an existing message.
+5. Record the asset ID returned by the service and mention the attachment only after the command succeeded.
 
 ## Operating Rules
 
@@ -188,8 +210,8 @@ prismer session checkpoint restore <runId>   # re-apply a saved snapshot
 
 - Choose capability filters based on the **actual task**, not broad role guesses. "Code review" not "developer".
 - Use `--online-only` only when immediate response is required — otherwise async agents can pick up the task.
-- Compare names, IDs, descriptions, capabilities, and status before picking. Identical display names exist.
-- Use returned IDs/usernames for routing — never invent or guess identifiers from chat text.
+- Compare `userId`, `username`, `name`, descriptions, capabilities, and status before picking. Identical names exist.
+- Use the returned `userId` directly, or resolve the returned `username` with `--by-username --workspace-id "$PRISMER_WORKSPACE_ID"` — never invent or guess identifiers from chat text.
 
 ### List participants
 
@@ -203,7 +225,7 @@ prismer session checkpoint restore <runId>   # re-apply a saved snapshot
 - **Never send to yourself.**
 - **Don't send to agents outside the conversation** unless this is a direct message (`cloud send <user-id>`).
 - Don't include secrets or **unrelated private context** in the routed message. The agent on the other end gets the full text.
-- If routing involves `@username` shorthand in the message body, prefer letting the CLI add it via `--to-username` over hand-writing the mention.
+- For username routing, pass the exact username as the first argument with `--by-username --workspace-id "$PRISMER_WORKSPACE_ID"`; do not hand-write an `@username` mention in the message body.
 
 ### File attach
 
@@ -222,9 +244,9 @@ prismer session checkpoint restore <runId>   # re-apply a saved snapshot
 
 ## Output reporting
 
-After discover: list each candidate as `<username> · <displayName> · capabilities=[a,b,c] · status=<online|offline>`.
+After discover: the default table exposes `User ID`, `Username`, `Name`, `Capabilities`, `Status`, and `Description`. Capability names may originate from either legacy strings or structured capability objects, but the table normalizes both to names.
 
-After listing participants: same format, scoped to the conversation.
+After listing participants: report `<user.id> · <user.username> · <user.displayName> · role=<user.role> · agentType=<user.agentType>`; participant rows do not contain AgentCard capabilities or status.
 
 After send: echo the returned `messageId` and `conversationId`. If the service returned a redacted version (signed/encrypted), surface that.
 

package/built-in-skills/agent-meta/SKILL.md

@@ -1,5 +1,6 @@
 ---
 name: agent-meta
+scope: common
 description: Inspect, snapshot, publish, and fork Prismer long-running agents through the cloud agent lifecycle API.
 allowed-tools: cloud.agent.spec cloud.agent.snapshot cloud.agent.snapshots cloud.agent.restore cloud.agent.publish cloud.agent.packs cloud.agent.fork prismer.agent.snapshot prismer.agent.publish prismer.agent.fork
 metadata:

package/built-in-skills/assets/SKILL.md

@@ -1,5 +1,6 @@
 ---
 name: assets
+scope: common
 description: Locate, inspect, and read content-addressed workspace assets — search by filename/metadata, describe before reading bytes, then read bounded ranges. Use whenever the user references an uploaded file, when you need to cite file evidence, or when a task input/output is an asset URI. Executes via the `cloud asset` CLI and tools.
 ---
 
@@ -106,11 +107,10 @@ pre-signed URL into prose:
 { "kind": "image", "assetId": "<assetId>", "mediaType": "image/png", "alt": "<one-line desc>" }
 ```
 
-When it resolves a **file** asset (PDF, CSV, archive) the reply should include
-the asset as an attachment (auto-handled by writing into
-`$PRISMER_ARTIFACTS_DIR` — daemon's artifacts-watcher scans the dispatch's
-`artifacts/` dir and auto-archives + attaches per release201/30 §4 — or
-explicitly as):
+When it resolves an existing **file** asset (PDF, CSV, archive), do not copy it
+into `$PRISMER_ARTIFACTS_DIR` or create a duplicate upload. Return the existing
+asset through the structured ContentBlock attachment using its authoritative
+`assetId`:
 
 ```json
 { "kind": "file", "assetId": "<assetId>", "mediaType": "application/pdf", "filename": "<original>" }
@@ -119,7 +119,9 @@ explicitly as):
 Do NOT paste raw bytes or `data:` URIs into the reply body — they bypass the
 content-addressed store, defeat caching, and make follow-up retrieval
 impossible. The chat renderer reads ContentBlock attachments and surfaces
-them as previews automatically.
+them as previews. If the user explicitly requests a newly generated local
+file, that is a separate file carrier: write it under `artifacts/` and run
+`cloud deliver <abs-path>` or `cloud task attach <abs-path>` explicitly.
 
 ## Backing capabilities (D22 mapping)
 

package/built-in-skills/browser-use/SKILL.md

@@ -0,0 +1,93 @@
+---
+name: browser-use
+scope: common
+description: LLM-driven browser automation via the pre-installed browser-use library (chromium already in the image). Use whenever the task needs to interact with web pages beyond a single fetch — multi-step navigation, form filling, clicking, scrolling, structured data extraction, screenshots, or tasks the plain web tools can't complete. Runs as a Python script against the built-in chromium; LLM goes through the Prismer gateway (no external LLM key needed).
+---
+
+# Browser-Use (Web Automation)
+
+The sandbox image ships `browser-use` (installed in `/home/user/.venv`) and a full
+chromium build (playwright). This skill drives them: write a short Python script
+with `Agent(task=..., llm=..., browser=...)`, run it, report the result.
+
+## When to use
+
+- Multi-step web tasks: search → open → extract → compare → download
+- Form filling / login flows / clicking through pages
+- Structured extraction (tables, listings, prices) that a single fetch can't parse
+- Screenshots / visual confirmation of a page state
+- Anything needing JS-rendered content (SPA pages the fetch tools miss)
+
+For a single plain fetch, prefer the existing web tools (lighter). Reach for
+browser-use when they come back empty or the task is interactive.
+
+## How to run
+
+```bash
+# chromium executable (version dir may change — resolve dynamically):
+CHROME="$(find /home/user/.cache/ms-playwright -name chrome -type f | head -1)"
+
+# LLM = our gateway (OpenAI-compatible). PRISMER_BASE_URL / PRISMER_API_KEY
+# are already in the environment; never hardcode them in the script.
+cat > /tmp/bu_task.py <<'PY'
+import os, asyncio
+from browser_use import Agent, ChatOpenAI, Browser
+
+async def main():
+    llm = ChatOpenAI(
+        base_url=f"{os.environ['PRISMER_BASE_URL']}/api/v1",
+        api_key=os.environ['PRISMER_API_KEY'],
+        model=os.environ.get('PRISMER_MODEL', 'deepseek-v4-flash'),
+        temperature=0.0,
+        # REQUIRED for the Prismer gateway: browser-use defaults to forcing
+        # JSON-schema structured output (response_format=json_schema) which
+        # our upstream models reject with 400 "response_format type
+        # unavailable" (verified 2026-08-07). Disable it; the agent still
+        # extracts via its normal flow.
+        dont_force_structured_output=True,
+    )
+    browser = Browser(
+        headless=True,
+        executable_path=os.environ['CHROME'],
+    )
+    agent = Agent(
+        task="<TASK>",  # be specific: steps, URLs, what to extract, output format
+        llm=llm,
+        browser=browser,
+    )
+    history = await agent.run(max_steps=30)
+    print("RESULT:", history.final_result())
+    print("URLS:", history.urls())
+    print("ERRORS:", history.errors())
+    await browser.close()
+
+asyncio.run(main())
+PY
+CHROME="$CHROME" /home/user/.venv/bin/python /tmp/bu_task.py
+rm -f /tmp/bu_task.py
+```
+
+## Task-writing rules (from browser-use docs)
+
+- **Be specific**: `"Go to https://…, use extract with query 'first 3 quotes and their authors', save to quotes.csv via write_file"` — open-ended tasks fail.
+- **Name actions**: "use search action for …", "use click to open first result in a new tab", "use send_keys with 'Tab Tab Enter'" — the agent maps these to its built-in tools.
+- **Error recovery**: if navigation is blocked, fall back to a search engine; if a click fails, use keyboard navigation (`send_keys`).
+- **max_steps**: default 100; keep 30 for focused tasks, raise for long flows.
+- **Anti-bot**: if a page blocks automation, try `use_cloud=True` — NOT available here (no Browser-Use Cloud key). Fall back to search/cache.
+
+## Environment facts
+
+| Item | Value |
+| --- | --- |
+| Python | `/home/user/.venv/bin/python` (browser-use installed here) |
+| Chromium | `$(find /home/user/.cache/ms-playwright -name chrome -type f \| head -1)` |
+| LLM | Prismer gateway (`PRISMER_BASE_URL` + `PRISMER_API_KEY`, OpenAI-compatible) |
+| Model | `PRISMER_MODEL` env (default `deepseek-v4-flash`) — adjust for the task |
+| Telemetry | browser-use collects anonymous telemetry by default — set `ANONYMIZED_TELEMETRY=false` |
+
+## Output contract
+
+Report to the user: `history.final_result()` (the extracted answer), the URLs
+visited, and any errors. If `history.is_successful()` is False, say so plainly
+with `history.errors()` — do not invent a completion. Attach screenshots
+(`history.screenshot_paths()`) as task assets when they matter.

package/built-in-skills/canvas-design/SKILL.md

@@ -1,5 +1,6 @@
 ---
 name: canvas-design
+scope: persistence
 description: Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
 license: Complete terms in LICENSE.txt
 ---

package/built-in-skills/claim-agent-ownership/SKILL.md

@@ -1,5 +1,6 @@
 ---
 name: claim-agent-ownership
+scope: common
 description: |
   Orchestrator skill for resolving multi-daemon binding contention. Use when you (the
   orchestrator) detect an `agent.binding.contested` sync event indicating two daemons
@@ -73,7 +74,7 @@ curl -fsS \
 ```
 
 `PRISMER_CLOUD_BASE` defaults to the cloud the daemon paired with
-(`https://prismer.cloud` in prod, `http://127.0.0.1:3000` in local dev).
+(`https://prod.docbrew.cn` in prod, `http://127.0.0.1:3000` in local dev).
 
 For pure-API use (orchestrator runtime, MCP tool, etc.), the underlying call is:
 
@@ -209,7 +210,7 @@ Action:
     "$PRISMER_CLOUD_BASE/api/im/agent-bindings/u_agent_ceo/rebind"
 
 Response: boundDaemonId='daemon-mac-studio-01', inFlightTaskCount=2
-Orchestrator messages user: "Pinned CEO agent to your Mac Studio. 2 tasks finishing on
+Orchestrator messages user: "Pinned Team Manager agent to your Mac Studio. 2 tasks finishing on
                             the cloud pod first."
 ```
 

package/built-in-skills/claude-api/SKILL.md

@@ -1,5 +1,6 @@
 ---
 name: claude-api
+scope: coding
 description: "Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a Claude feature (caching, thinking, compaction, tool use, batch, files, citations, memory) or model (Opus/Sonnet/Haiku) in a file; questions about prompt caching / cache hit rate in an Anthropic SDK project. SKIP: file imports `openai`/other-provider SDK, filename like `*-openai.py`/`*-generic.py`, provider-neutral code, general programming/ML."
 license: Complete terms in LICENSE.txt
 ---

package/built-in-skills/codebase-design/DEEPENING.md

@@ -0,0 +1,37 @@
+# Deepening
+
+How to deepen a cluster of shallow modules safely, given its dependencies. Assumes the vocabulary in [SKILL.md](SKILL.md) — **module**, **interface**, **seam**, **adapter**.
+
+## Dependency categories
+
+When assessing a candidate for deepening, classify its dependencies. The category determines how the deepened module is tested across its seam.
+
+### 1. In-process
+
+Pure computation, in-memory state, no I/O. Always deepenable — merge the modules and test through the new interface directly. No adapter needed.
+
+### 2. Local-substitutable
+
+Dependencies that have local test stand-ins (PGLite for Postgres, in-memory filesystem). Deepenable if the stand-in exists. The deepened module is tested with the stand-in running in the test suite. The seam is internal; no port at the module's external interface.
+
+### 3. Remote but owned (Ports & Adapters)
+
+Your own services across a network boundary (microservices, internal APIs). Define a **port** (interface) at the seam. The deep module owns the logic; the transport is injected as an **adapter**. Tests use an in-memory adapter. Production uses an HTTP/gRPC/queue adapter.
+
+Recommendation shape: *"Define a port at the seam, implement an HTTP adapter for production and an in-memory adapter for testing, so the logic sits in one deep module even though it's deployed across a network."*
+
+### 4. True external (Mock)
+
+Third-party services (Stripe, Twilio, etc.) you don't control. The deepened module takes the external dependency as an injected port; tests provide a mock adapter.
+
+## Seam discipline
+
+- **One adapter means a hypothetical seam. Two adapters means a real one.** Don't introduce a port unless at least two adapters are justified (typically production + test). A single-adapter seam is just indirection.
+- **Internal seams vs external seams.** A deep module can have internal seams (private to its implementation, used by its own tests) as well as the external seam at its interface. Don't expose internal seams through the interface just because tests use them.
+
+## Testing strategy: replace, don't layer
+
+- Old unit tests on shallow modules become waste once tests at the deepened module's interface exist — delete them.
+- Write new tests at the deepened module's interface. The **interface is the test surface**.
+- Tests assert on observable outcomes through the interface, not internal state.
+- Tests should survive internal refactors — they describe behaviour, not implementation. If a test has to change when the implementation changes, it's testing past the interface.

package/built-in-skills/codebase-design/DESIGN-IT-TWICE.md

@@ -0,0 +1,44 @@
+# Design It Twice
+
+When the user wants to explore alternative interfaces for a chosen deepening candidate, use this parallel sub-agent pattern. Based on "Design It Twice" (Ousterhout) — your first idea is unlikely to be the best.
+
+Uses the vocabulary in [SKILL.md](SKILL.md) — **module**, **interface**, **seam**, **adapter**, **leverage**.
+
+## Process
+
+### 1. Frame the problem space
+
+Before spawning sub-agents, write a user-facing explanation of the problem space for the chosen candidate:
+
+- The constraints any new interface would need to satisfy
+- The dependencies it would rely on, and which category they fall into (see [DEEPENING.md](DEEPENING.md))
+- A rough illustrative code sketch to ground the constraints — not a proposal, just a way to make the constraints concrete
+
+Show this to the user, then immediately proceed to Step 2. The user reads and thinks while the sub-agents work in parallel.
+
+### 2. Spawn sub-agents
+
+Spawn 3+ sub-agents in parallel using the Agent tool. Each must produce a **radically different** interface for the deepened module.
+
+Prompt each sub-agent with a separate technical brief (file paths, coupling details, dependency category from [DEEPENING.md](DEEPENING.md), what sits behind the seam). The brief is independent of the user-facing problem-space explanation in Step 1. Give each agent a different design constraint:
+
+- Agent 1: "Minimize the interface — aim for 1–3 entry points max. Maximise leverage per entry point."
+- Agent 2: "Maximise flexibility — support many use cases and extension."
+- Agent 3: "Optimise for the most common caller — make the default case trivial."
+- Agent 4 (if applicable): "Design around ports & adapters for cross-seam dependencies."
+
+Include both [SKILL.md](SKILL.md) vocabulary and CONTEXT.md vocabulary in the brief so each sub-agent names things consistently with the architecture language and the project's domain language.
+
+Each sub-agent outputs:
+
+1. Interface (types, methods, params — plus invariants, ordering, error modes)
+2. Usage example showing how callers use it
+3. What the implementation hides behind the seam
+4. Dependency strategy and adapters (see [DEEPENING.md](DEEPENING.md))
+5. Trade-offs — where leverage is high, where it's thin
+
+### 3. Present and compare
+
+Present designs sequentially so the user can absorb each one, then compare them in prose. Contrast by **depth** (leverage at the interface), **locality** (where change concentrates), and **seam placement**.
+
+After comparing, give your own recommendation: which design you think is strongest and why. If elements from different designs would combine well, propose a hybrid. Be opinionated — the user wants a strong read, not a menu.

package/built-in-skills/codebase-design/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Matt Pocock
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/built-in-skills/codebase-design/SKILL.md

@@ -0,0 +1,116 @@
+---
+name: codebase-design
+scope: coding
+source: https://github.com/mattpocock/skills (MIT, © 2026 Matt Pocock)
+description: Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
+---
+
+# Codebase Design
+
+Design **deep modules**: a lot of behaviour behind a small interface, placed at a clean seam, testable through that interface. Use this language and these principles wherever code is being designed or restructured. The aim is leverage for callers, locality for maintainers, and testability for everyone.
+
+## Glossary
+
+Use these terms exactly — don't substitute "component," "service," "API," or "boundary." Consistent language is the whole point.
+
+**Module** — anything with an interface and an implementation. Deliberately scale-agnostic: a function, class, package, or tier-spanning slice. _Avoid_: unit, component, service.
+
+**Interface** — everything a caller must know to use the module correctly: the type signature, but also invariants, ordering constraints, error modes, required configuration, and performance characteristics. _Avoid_: API, signature (too narrow — they refer only to the type-level surface).
+
+**Implementation** — what's inside a module, its body of code. Distinct from **Adapter**: a thing can be a small adapter with a large implementation (a Postgres repo) or a large adapter with a small implementation (an in-memory fake). Reach for "adapter" when the seam is the topic; "implementation" otherwise.
+
+**Depth** — leverage at the interface: the amount of behaviour a caller (or test) can exercise per unit of interface they have to learn. A module is **deep** when a large amount of behaviour sits behind a small interface, **shallow** when the interface is nearly as complex as the implementation.
+
+**Seam** _(Michael Feathers)_ — a place where you can alter behaviour without editing in that place; the *location* at which a module's interface lives. Where to put the seam is its own design decision, distinct from what goes behind it. _Avoid_: boundary (overloaded with DDD's bounded context).
+
+**Adapter** — a concrete thing that satisfies an interface at a seam. Describes *role* (what slot it fills), not substance (what's inside).
+
+**Leverage** — what callers get from depth: more capability per unit of interface they learn. One implementation pays back across N call sites and M tests.
+
+**Locality** — what maintainers get from depth: change, bugs, knowledge, and verification concentrate in one place rather than spreading across callers. Fix once, fixed everywhere.
+
+## Deep vs shallow
+
+**Deep module** = small interface + lots of implementation:
+
+```
+┌─────────────────────┐
+│   Small Interface   │  ← Few methods, simple params
+├─────────────────────┤
+│                     │
+│  Deep Implementation│  ← Complex logic hidden
+│                     │
+└─────────────────────┘
+```
+
+**Shallow module** = large interface + little implementation (avoid):
+
+```
+┌─────────────────────────────────┐
+│       Large Interface           │  ← Many methods, complex params
+├─────────────────────────────────┤
+│  Thin Implementation            │  ← Just passes through
+└─────────────────────────────────┘
+```
+
+When designing an interface, ask:
+
+- Can I reduce the number of methods?
+- Can I simplify the parameters?
+- Can I hide more complexity inside?
+
+## Principles
+
+- **Depth is a property of the interface, not the implementation.** A deep module can be internally composed of small, mockable, swappable parts — they just aren't part of the interface. A module can have **internal seams** (private to its implementation, used by its own tests) as well as the **external seam** at its interface.
+- **The deletion test.** Imagine deleting the module. If complexity vanishes, it was a pass-through. If complexity reappears across N callers, it was earning its keep.
+- **The interface is the test surface.** Callers and tests cross the same seam. If you want to test *past* the interface, the module is probably the wrong shape.
+- **One adapter means a hypothetical seam. Two adapters means a real one.** Don't introduce a seam unless something actually varies across it.
+
+## Designing for testability
+
+Good interfaces make testing natural:
+
+1. **Accept dependencies, don't create them.**
+
+   ```typescript
+   // Testable
+   function processOrder(order, paymentGateway) {}
+
+   // Hard to test
+   function processOrder(order) {
+     const gateway = new StripeGateway();
+   }
+   ```
+
+2. **Return results, don't produce side effects.**
+
+   ```typescript
+   // Testable
+   function calculateDiscount(cart): Discount {}
+
+   // Hard to test
+   function applyDiscount(cart): void {
+     cart.total -= discount;
+   }
+   ```
+
+3. **Small surface area.** Fewer methods = fewer tests needed. Fewer params = simpler test setup.
+
+## Relationships
+
+- A **Module** has exactly one **Interface** (the surface it presents to callers and tests).
+- **Depth** is a property of a **Module**, measured against its **Interface**.
+- A **Seam** is where a **Module**'s **Interface** lives.
+- An **Adapter** sits at a **Seam** and satisfies the **Interface**.
+- **Depth** produces **Leverage** for callers and **Locality** for maintainers.
+
+## Rejected framings
+
+- **Depth as ratio of implementation-lines to interface-lines** (Ousterhout): rewards padding the implementation. We use depth-as-leverage instead.
+- **"Interface" as the TypeScript `interface` keyword or a class's public methods**: too narrow — interface here includes every fact a caller must know.
+- **"Boundary"**: overloaded with DDD's bounded context. Say **seam** or **interface**.
+
+## Going deeper
+
+- **Deepening a cluster given its dependencies** — see [DEEPENING.md](DEEPENING.md): dependency categories, seam discipline, and replace-don't-layer testing.
+- **Exploring alternative interfaces** — see [DESIGN-IT-TWICE.md](DESIGN-IT-TWICE.md): spin up parallel sub-agents to design the interface several radically different ways, then compare on depth, locality, and seam placement.