一键导入
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Ask which skill or flow fits your situation. A router over the skills in this repo.
Implement a piece of work based on a spec or set of tickets.
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
| name | improve-codebase-architecture |
| description | Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. |
This command is informed by the project's domain model and built on a shared design vocabulary:
codebase-design skill for the architecture vocabulary (module, interface, depth, seam, adapter, leverage, locality) and its principles (the deletion test, "the interface is the test surface", "one adapter = hypothetical seam, two = real"). Use these terms exactly in every suggestion — don't drift into "component," "service," "API," or "boundary.".zoo-flow/CONTEXT.md gives names to good seams; ADRs in .zoo-flow/docs/adr/ record decisions this command should not re-litigate..zoo-flow/CONTEXT.md..scratch/architecture-review-{timestamp}.html.Strong/Worth exploring/Speculative; ADR conflict only if real.xdg-open {path}, macOS open {path}, Windows start {path}.Which of these would you like to explore?Before broad reads, locate relevant files/symbols with Glob, Grep, or targeted file reads.
Prefer targeted Read with line ranges or block reads once the relevant area is known.
Read full files only when structure, ordering, or surrounding context is required for correctness.
Do not re-read unchanged files; use prior findings unless the file changed.
Use searches to identify dependency/call patterns before reading full modules. Read full files only for top candidates.
domain-modeling skill to update CONTEXT.md lazily.domain-modeling skill to update CONTEXT.md immediately.DESIGN-IT-TWICE.md from the codebase-design skill.COMPLETION PROTOCOL: Your final text message is your return value. Output this summary, then STOP — do not call any more tools.
.scratch/architecture-review-{timestamp}.html)/zoo-refactor to implement the chosen candidate, or /zoo-feature if it requires PRD + issue slicing)