Claude Code

Claude Code is a first-class SDTK runtime: the runtime-aware toolkits install their skills as Claude Code skills with slash commands, and session-start guidance routes every request through SDTK's governance.

Setup

npm install -g sdtk-kit
sdtk init --runtime claude

Claude Code defaults to project scope — skills land in .claude/skills/ inside your repo, so skill versions travel with the project (ideal for teams). For machine-wide install instead:

sdtk init --runtime claude --global   # → ~/.claude/skills/

Slash commands installed

Command	Purpose
/orchestrator	Full SDLC orchestration — the recommended entry point
/pm	PM initiation + planning
/ba	Business analysis
/arch	Solution architecture
/dev	Development + code review
/qa	QA testing + release decision
/api-doc, /api-design-spec	API documentation and design specs
/screen-design-spec, /design-layout	Screen specs and layout wireframes
/test-case-spec	QA test-case specs
/dev-backend, /dev-frontend	Code conventions

Design and ops journeys install as skills too. SDTK-WIKI and SDTK-AGENT install no skills — they're CLI-driven, and there is deliberately no /agent slash command.

How a session flows

1. Open Claude Code in the initialized project.
2. Init wrote CLAUDE.md session guidance: Claude reads SDTK's routing rules at session start.
3. Type /orchestrator (or just describe what you want — unprefixed requests route through Orchestrator Intake).
4. The orchestrator classifies your intent — raw idea → discovery; formal delivery → the phase pipeline; bounded task → a single skill — and writes real artifacts into docs/.

/orchestrator
I want to build a lightweight CRM for solo consultants to track leads.

What calls leave your machine

SDTK CLIs run locally and make no model calls of their own. Model/API calls happen when you run Claude Code — every skill execution is a Claude session you started. Repo-owned artifacts (specs, ledgers, graphs, reports) stay in your repository.

Keeping skills current

sdtk update
sdtk init --runtime claude --force

Where to go next

Runtimes & SkillsScopes, the skill/CLI division of labor.

QuickstartFirst governed workflow end to end.

TroubleshootingSkills not loading or stale after update.