使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-blueprint开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
仓库原始内容
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
ds-blueprint
Fix the shape of the code before writing the bodies, so the model fills in a plan instead of inventing one as it goes.
Steps
- Ground yourself. Read every module the new code will touch. If you cannot explain how they fit together, run /ds-explain first. Skip this only for code with no surrounding system.
- Write at least two structurally different sketches. Each sketch is real files with types, signatures, module boundaries and stub bodies that raise "not implemented", plus short pseudocode. Use /ds-best-of-n to produce them in parallel when the design matters.
- Compare the sketches. Prefer the one with the smaller public surface that hides more inside. Prefer the one where a change that looks right from a single file is also right for the whole repo. Note what you rejected and why.
- Run the type checker or compiler on the chosen sketch. Paste the output. Stubs must compile.
- Show the user the chosen sketch and wait for agreement before you fill in bodies. In an unattended run, record the choice with /ds-ledger instead.
- Implement one stub at a time. After each, run the type checker and the relevant tests. If the sketch turns out wrong, stop and revise the sketch, not just the body.
- Delete leftover stubs, dead sketches and unused types. Grep for "not implemented" to prove none remain.
Stop when
- Every stub is implemented, the type checker passes and the tests pass, with output shown.
- Or the sketch needed three revisions during implementation. Stop and redesign with the user.
Rules
- Signatures change only through step 6's revise path, never silently.
- Keep each sketch file small enough to read in one pass.
- Evidence is compiler and test output, not "it should work".
