菜单
Icebox a raised-but-undecided concern instead of forcing a plan-or-dismiss call: record it with no verdict so the context survives. Use when a review, PR, audit, or eval surfaces something real-maybe that should not be scheduled or closed yet, or when the user says to icebox or park an item.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add a new shared workspace package under packages/*. Use when creating a new @packages/<name>, whether a bundled library other workspaces import or a build-only script package that runs during a build.
Orient in this repo: which file to edit for a change, how a change ripples across the stack, and how to search the code. Use at the start of a task in an unfamiliar area, or before a cross-cutting change.
Prefer Bun-native APIs, else Node built-ins with the node: prefix. Use when importing a Node built-in (fs, path, child_process, crypto, os, util), reading or writing files, spawning a process, or choosing between a Bun and a Node API.
Add a typed Hono API endpoint or WebSocket route: router, OpenAPI docs, validation envelope, and RPC client wiring. Use when adding or modifying routes in api/hono.
Start, restart, and verify the ZeroStarter dev stack. `bun run dev` serves portless named `.localhost` URLs (branch-prefixed in a worktree); resolve them with `bunx portless get`. Use when asked to run the app, when the API returns NOT_FOUND for routes that exist in source, or before browser testing.
Verify a frontend or UI change in a real browser. Use after any change to web/next pages, components, or styles, before opening or updating a PR, or when an end-to-end flow needs checking.
| name | icebox |
| description | Icebox a raised-but-undecided concern instead of forcing a plan-or-dismiss call: record it with no verdict so the context survives. Use when a review, PR, audit, or eval surfaces something real-maybe that should not be scheduled or closed yet, or when the user says to icebox or park an item. |
A concern got raised that you cannot honestly schedule or resolve right now. Do not force it into a plan or a dismissal. Put it on ice: record it with no verdict, so the context survives until someone can decide. The Icebox is the middle state between the plans backlog and a closed issue; its full definition and the standing index issue live in .github/notes/plans/README.md.
All three hold:
A clear next action goes to the plans backlog; a clear verdict gets done or closed. The Icebox is only for the genuinely undecided.
.github/notes/plans/<slug>.md, or append a section to a fitting existing file. State the concern, its context, and the open question; give no verdict and no plan. Done when a reader learns the concern and what is unresolved, and finds no recommendation.## Icebox in .github/notes/plans/README.md, linking the write-up. Done when the index links the file.plans/<slug>.md path. Done when gh issue view 707 shows it.An item leaves the Icebox only by being decided. When that happens, check its box in #707, note what happened (shipped, dismissed, or moved to the backlog), and graduate its write-up to the plans backlog or delete it.