aicodeking/deepseek-stack

ds-blueprint

Design the types, function signatures and module layout first, agree on that shape, then implement against it.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
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

  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".
同じリポジトリから

関連する Skills

すべての Skills
aicodeking
コミュニティ

ds-adopt

Takes over an existing PR, branch or agent thread and finishes its original goal while keeping credit for the first contributors. Use when the user says take over, adopt, pick up or finish this PR, or /ds-adopt.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-best-of-n

Run N independent attempts at the same task in parallel, pick the strongest as the base, and graft the best parts of the others into it. Use when one attempt at a non-trivial artifact could land on the wrong shape, or for /ds-best-of-n, 'try a few versions', 'best of 3'.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-blast-radius

Find what a change could break outside its own diff, then prove the key safety fact by running real code. Use before shipping a risky or untrusted change, for 'what could this break', 'blast radius of X', or /ds-blast-radius.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-catchup

Give the user a short plain-language catch-up on what changed since their last message, followed by every decision still waiting on them. Use when the user returns after a long or unattended run, asks 'where are we', 'what did I miss', or types /ds-catchup.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日