dev-kit

dev-kit — a Claude Code workflow plugin

An opinionated, cross-machine Claude Code setup that you install once and get everywhere.

It bundles:

• MCPs: OpenViking (persistent memory, auto-recall on every prompt), Context7 (live library docs), Serena (LSP-powered code retrieval), Sequential Thinking (structured reasoning), plus optional Brave Search and local memory graph
• Subagents: orchestrator, researcher, planner, reverse-reasoner, implementer, reviewer, security-reviewer, test-runner, debugger, ci-triager, memory-curator — each in its own context window
• Hooks: bash guard, write guard, auto-format on edit, project-snapshot on session start, session capture on stop
• Skills: project-bootstrap, debug-playbook, pr-checklist, security-review, dependency-audit, incident-response, deploy-check, onboard
• Slash commands: /bootstrap, /pr-check, /security-check, /refresh
• Workflow guides: feature-workflow, hotfix-workflow, recovery-playbook

Designed so installing it on a new machine is two commands.

---

One-time setup per machine

1. Prerequisites

You need these on each machine. Anything missing means a piece of the kit silently no-ops, never breaks.

Tool	Why	Install
python3 (3.10+ required)	Hook scripts. 3.9 will fail silently on session_context.py. Check: python3 --version	macOS: brew install python · Ubuntu: apt install python3 · Windows: python.org
node + npx	Context7 + Sequential Thinking MCPs	nodejs.org or nvm
uv (uvx)	Serena MCP	curl -LsSf https://astral.sh/uv/install.sh | sh (Mac/Linux) · winget install astral-sh.uv (Windows)
git	SessionStart hook reads git state	already on most systems

Optional but recommended formatters (auto-format hook detects what's installed): prettier, ruff or black, gofmt, rustfmt, shfmt, rubocop.

2. Install the plugin

From inside Claude Code (any project, anywhere):

/plugin marketplace add atalias-tech/claude-dev-kit
/plugin install dev-kit@dev-kit-marketplace

You'll be prompted for the userConfig values (Context7 API key — optional, leave blank for free tier; OpenViking URL and API key; the boolean toggles).

That's it. On the next session start in any project, the hooks fire, the MCPs come up, and the subagents are available.

3. Bootstrap a project

In any project, run:

/bootstrap

It drops a CLAUDE.md and .claude/memory/decisions.md tailored to whatever stack it detects. Review the file, fix the bits it got wrong, commit. Run /refresh later when the stack changes.

---

Cross-machine memory (the "what did I do here vs there" piece)

The kit ships three memory layers, active by default:

Layer 1 — OpenViking (semantic memory, built-in)

OpenViking is ByteDance's open-source context database for AI agents. The kit wires it directly — no separate plugin needed.

What the kit does automatically:

• SessionStart — fetches your recent memories and preferences from OpenViking and injects them as <openviking-context> so Claude starts every session with persistent context.
• UserPromptSubmit — searches OpenViking for memories relevant to each prompt and injects them as <relevant-memories> before Claude responds.
• Stop — sends the conversation transcript to OpenViking for memory extraction and indexing.
• MCP — openviking MCP server registered at http://127.0.0.1:1933 by default, exposing mcp__openviking__search, mcp__openviking__store, mcp__openviking__read, mcp__openviking__forget, and others.

Setup: Start an OpenViking server locally (docker run -p 1933:1933 volcengine/openviking) or point openviking_base_url at a remote one. Set openviking_api_key if your server requires auth. The kit writes ~/.openviking/ovcli.conf on first session start.

For cross-machine sharing, point OpenViking's data dir at a synced folder (~/Dropbox/openviking).

Layer 2 — decisions.md (zero infra)

The session_capture.py Stop hook appends a timestamped git snapshot to .claude/memory/decisions.md at the end of every session. Syncs naturally if the project is on a synced drive.

Layer 3 — local knowledge graph (optional)

If you prefer a local JSONL graph over OpenViking, set memory_path in userConfig and use the mcp__memory__* tools. Set memory_system: local-graph to have the session-start nudge point Claude at the right tools.

---

What's in the kit, in one page