The Problem
Out of the box, Claude Code is powerful but undisciplined. It will:
- Start coding before understanding the codebase
- Make sweeping changes across files you didn't ask it to touch
- Skip verification steps and ship broken code
- Forget lessons from previous mistakes
- Install dependencies and change architecture without asking
The Solution
This kit provides a CLAUDE.md instruction set and supporting templates that enforce a structured workflow:
Plan > Confirm > Implement > Verify — every single time.
Quick Start
npx @tansuasici/claude-code-kit init
Or with curl:
curl -fsSL https://raw.githubusercontent.com/tansuasici/claude-code-kit/main/install.sh | bash
Or as a Claude Code plugin:
/plugin marketplace add tansuasici/claude-plugins
/plugin install code-kit@tansuasici
Installed it the old way, from the tansuasici/claude-code-kit marketplace? That install keeps working and keeps updating — nothing breaks. To move to the shared marketplace, uninstall the old claude-code-kit plugin and run the two lines above; the kit's commands are then under /code-kit:*.
| Path | What you get | When to use |
|---|
| npx / curl | Full kit — CLAUDE.md, agent_docs, all skills, all hooks, agents, scripts, examples | Default. Best when you want the comprehensive discipline layer in your repo. |
| Plugin marketplace | Kit as a Claude Code plugin (skills, agents and hooks; commands namespaced under /code-kit:*) | Lightweight discovery path; sits alongside other plugins. Does not seed CLAUDE.md / CODEBASE_MAP.md into your repo. |
Then fill in CODEBASE_MAP.md with your project's details and start a Claude Code session.
Maintainers: see RELEASING.md for the release flow (npm token setup, 2FA mode requirement, EOTP recovery).
Installer options
| Flag | Description |
|---|
--template nextjs | Use a stack-specific template (nextjs, node-api, python-fastapi, go, rust, django, dotnet). Auto-detected if omitted. |
--profile minimal | Hooks only, no CLAUDE.md or docs |
--profile strict | All hooks enabled — the 5 opt-in ones too (auto-lint, auto-format, skill-compliance, skill-extract-reminder, notify-waiting) — and the gates that only warn by default turn into blocks: build-config edits (CCK_PROTECT_BUILD_CONFIGS=1), and a stop or a git commit while a test is missing or red (CCK_TEST_FIRST=strict) |
--upgrade | Update kit-managed files. Ones you edited are kept and reported (the kit's copy lands next to them as <file>.kit-new, never over an earlier one — then .kit-new.1, …); project files are never touched. Needs sha256sum, shasum or python3 |
--diff | Preview exactly what --upgrade would do (it runs the upgrade on a scratch copy that follows symlinks): files to update, add, keep and resolve, kit paths that are symlinks --upgrade would write through, plus what an upgrade can't fix — stale kit files, kit hooks missing from .claude/settings.json, registrations of scripts that don't exist. Read-only |
--gitignore | Add kit files to .gitignore (keep kit local, don't push to repo) |
--wiki | Add knowledge wiki module (personal knowledge base) |
--html | Add HTML artifacts module (specs, reports, PR writeups as HTML — see ARTIFACTS.md) |
--version v1.0.0 | Install a specific version instead of latest |
Uninstall
curl -fsSL https://raw.githubusercontent.com/tansuasici/claude-code-kit/main/uninstall.sh | bash
| Flag | Description |
|---|
--dry-run | Show what would be removed without deleting |
--keep-tasks | Preserve tasks/ directory (lessons, decisions, handoffs) |
--keep-project | Preserve project overlay files (CLAUDE.project.md, agent_docs/project/, etc.) |
--force | Remove without confirmation |
Examples:
# Install with npx
npx @tansuasici/claude-code-kit init --template nextjs
npx @tansuasici/claude-code-kit init --profile strict
npx @tansuasici/claude-code-kit init --wiki
npx @tansuasici/claude-code-kit init --html
npx @tansuasici/claude-code-kit init --upgrade
# Or with curl
curl -fsSL .../install.sh | bash -s -- --template nextjs
curl -fsSL .../install.sh | bash -s -- --gitignore
curl -fsSL .../install.sh | bash -s -- --upgrade
curl -fsSL .../install.sh | bash -s -- --diff
curl -fsSL .../install.sh | bash -s -- --version v1.0.0
Next to another Claude kit
The Marketing, Design and Research kits use the same CLAUDE.md and the same hook names, so two kits can't share a folder. install.sh and uninstall.sh stop and change nothing when they find one of those kits in the target folder.
Install this kit into a subfolder instead, and open Claude Code in that subfolder:
mkdir -p code && cd code
curl -fsSL https://raw.githubusercontent.com/tansuasici/claude-code-kit/main/install.sh | bash
claude
Hooks only run from the folder the session opened in. A session opened at the repo root doesn't run the subfolder's hooks, so secret-scan won't check a write under code/ from there.
A copy of one of those kits from before this check doesn't stop: its install.sh or uninstall.sh still replaces or deletes this kit's files.
npx CLI commands
npx @tansuasici/claude-code-kit init # Install kit
npx @tansuasici/claude-code-kit doctor # Check installation health
npx @tansuasici/claude-code-kit skills # List available /skill commands
npx @tansuasici/claude-code-kit convert all # Export to Cursor/Windsurf/Aider/AGENTS.md + .agents/skills
npx @tansuasici/claude-code-kit convert codex # Codex: AGENTS.md rules + .agents/skills
npx @tansuasici/claude-code-kit generate agents-md # Generate AGENTS.md only
npx @tansuasici/claude-code-kit --version # Show version
This is the beginning of the README. Read the rest at the original. Read the full README ↗
