ds-blueprint — Claude Code skill: what it does, how to install
A Claude Code skill that defines types, signatures, and module boundaries before writing code bodies. It triggers on /ds-blueprint or when asked to design the structure first.
MIT 546 installs ★ 320 updated 2026-10-28
npx skills add aicodeking/deepseek-stack --skill ds-blueprint -a claude-codeWhat ds-blueprint does
The skill fixes the interface layout before the model writes any function bodies. It inspects existing modules and prepares at least two distinct sketches with real files, types, and stubs that raise not implemented. The sketch with the smaller public surface wins.
The chosen layout must pass the project type checker or compiler while still in stub form. The model presents this sketch to the user and waits for agreement before filling in logic. Implementation proceeds one stub at a time, running tests and type checks after each change.
Signatures cannot change silently during coding. If an implementation forces three sketch revisions, the process stops completely to redesign with the user. A final grep check ensures no unimplemented stubs remain in the tree.
What it helps with
- design types and function signatures before writing bodies
- compare alternative architectural sketches using compiler feedback
- enforce approval of public interfaces before implementing logic
- verify that no
not implementedstubs remain in the codebase
Example prompts for the agent
- /ds-blueprint design this first
- architect this storage engine before implementing it
- /ds-blueprint
How to install ds-blueprint
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-blueprint -a claude-code2Manually: put the files in place
~/.claude/skills/ds-blueprint/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ds-blueprint/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-blueprint -a codex2Manually: put the files in place
.agents/skills/ds-blueprint/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-blueprint -a cursor2Manually: put the files in place
.cursor/skills/ds-blueprint/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aicodeking/deepseek-stack skills/ds-blueprint2Manually: put the files in place
.github/skills/ds-blueprint/SKILL.md1Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-blueprint -a gemini-cli2Platform CLI
gemini skills install https://github.com/aicodeking/deepseek-stack --path skills/ds-blueprintManually: put the files in place
.devin/skills/ds-blueprint/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aicodeking/deepseek-stack --skill ds-blueprint -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ds-blueprint
How to install ds-blueprint in Claude Code?
Run npx skills add aicodeking/deepseek-stack --skill ds-blueprint -a claude-code. You can also place the skill file manually at ~/.claude/skills/ds-blueprint/SKILL.md.
What does ds-blueprint do?
It creates compiling interface sketches with stubs and types, waits for user approval, and then implements bodies one by one with continuous compiler checks.
What happens if the design fails during coding?
If the sketch requires three revisions during implementation, the skill halts execution and prompts for a full redesign.
Source text
SKILL.md · MIT
--- name: ds-blueprint description: "Design the types, function signatures and module layout first, agree on that shape, then implement against it. Use when work is non-trivial and coding straight away would lock in the wrong structure, or for /ds-blueprint, 'design this first', 'architect this'." --- # 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 1. 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. 2. 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. 3. 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. 4. Run the type checker or compiler on the chosen sketch. Paste the output. Stubs must compile. 5. 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. 6. 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. 7. 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".
© aicodeking · MIT · aicodeking/deepseek-stack