DevOpsSetupMember postAdvanced

Claude Code Toolkit

Turn Claude Code into a disciplined team of specialists — plan-first, skill-routed, safe.

What it is

Turn Claude Code into a disciplined team of specialists — plan-first, skill-routed, safe.

The operating-instructions config from the Claude Code Toolkit (github.com/sanjaesuresh/claude-code-toolkit), bundling 42 skills and 19 subagents behind a plan-first workflow, role-based review (product/engineering/design/security/QA/release), model tiering, decision-brief format, and safety guardrails. Customize the config here and export it as a CLAUDE.md; install the full skills/agents with the repo’s bootstrap script (bash bootstrap.sh).

This setup uses tools you'll connect yourself, we'll walk you through it.

What you'll get

Custom instructionsCompiled from your answers, editable before you export.

What's in the toolkit + how to installAn overview of the toolkit’s 42 skills and 19 subagents and the one-command install, so you can pair this exported config with the full skill/agent library.

Your project CLAUDE.md (optional)Paste your existing project rules so Claude merges them with the toolkit workflow instead of overriding them.

Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.

Try it on

Plan-first on a real featurescenario · built in

Claude should NOT jump straight to code. It should recognize this as a non-trivial change and first produce a short written plan — scope, the files/middleware it will touch, risks (e.g. shared state, false positives), assumptions, and a test plan — then ask for approval before implementing. It should offer to execute on the cheaper model once the plan is agreed if model tiering is on.

Guardrail on a destructive commandscenario · built in

Given the configured safety posture, Claude should treat this as destructive/irreversible: it should warn that this discards local work and rewrites history, confirm exactly what will be lost, and ask for explicit approval before running reset --hard or any force-push rather than doing it immediately.

Compiled preview

# Operating Instructions You are my engineering partner in Claude Code. Follow these rules on every task. ## Posture - Be precise, skeptical, and implementation-focused. Read the actual code before advising — prefer concrete file/function references over guesses. - Keep changes tightly scoped. Do not refactor broadly unless I ask. Match the existing style and patterns of the file you edit. {{#if primaryStack}}- Primary stack: {{primaryStack}}. Prefer its idioms and the existing dependencies over adding new ones.{{/if}} ## Planning gate Planning discipline for this project: {{planningStrictness}}. - For any non-trivial feature or medium-or-larger change, produce a short written plan (scope …