菜单
Use when the task involves architecture, module design, refactors, interface boundaries, adapters, dependency direction, deep module design, deletion tests, locality, leverage, encapsulation, and codebase structure decisions before or during APIVR planning and review.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/wfprieto/wcbs-build-kit --skill codebase-design-and-deep-modules命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Use when a WCBS plan, remediation backlog, migration, release, or multi-slice engineering objective has dependent work that requires requirement-to-node traceability, topology validation, READY-frontier scheduling, or evidence-backed node locking. Also activate when the user explicitly requests /graph execution.
Use when the task involves any build, fix, audit, debug, optimization, release, verification, prompt, skill, or agent-design task. Activates the APIVR lifecycle and Elite Build Goals guardrails from this repository before task-specific work.
Use when a build, fix, plan, audit, skill, agent, or pipeline has more than one viable design and the agent must choose the simplest safe option or challenge unjustified complexity.
| name | codebase-design-and-deep-modules |
| description | Use when the task involves architecture, module design, refactors, interface boundaries, adapters, dependency direction, deep module design, deletion tests, locality, leverage, encapsulation, and codebase structure decisions before or during APIVR planning and review. |
| activation | Activate when the description trigger applies to the current task. |
| required_inputs | Task request, relevant repository context, constraints, and authority dependencies. |
| required_outputs | Skill-specific artifact, verification evidence, canonical verdict, and next action. |
| authority_dependencies | 00_start_here/SOURCE_OF_TRUTH.md; 10_governance/APIVR_EXECUTION_LIFECYCLE.md; 10_governance/source_of_truth/Elite_Build_Goals_v3.md. |
| evidence_requirements | Executed checks or an honest Unknown, Not Run, or Blocked state for every material claim. |
Use this skill when the shape of the code matters as much as the code itself.
flowchart TD
A["Design or refactor needed"] --> B{"Is the business rule duplicated or scattered?"}
B -- "Yes" --> C["Create or strengthen core module"]
B -- "No" --> D{"Is integration detail leaking inward?"}
D -- "Yes" --> E["Add adapter boundary"]
D -- "No" --> F{"Can the change be deleted cleanly?"}
F -- "No" --> G["Narrow interface and improve locality"]
F -- "Yes" --> H["Proceed with APIVR plan"]
Scenario: Three providers calculate shipping estimates differently.
ShippingQuoteService exposes one domain method and provider adapters implement external details.