사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-blueprint시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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".
