Home

Home

This page tells what dotclaude 1.0.0 does and which plugins it has. It is for new users, who read it before the install steps. It also shows where to read next for each task.

What dotclaude Does

dotclaude is a Claude Code plugin marketplace for software engineering. It changes Claude Code through the Mod API, settings, hooks, skills, agents, and output styles. It does not patch the binary. Its goal is the highest intelligence for the lowest token cost. This wiki describes dotclaude 1.0.0. The binary facts are for Claude Code 2.1.296, which is the value of TESTED_VERSION.

dotclaude does the following:

• Gives permission rules and a sandbox in the settings snippet. The rules ask or deny destructive actions, as Guards describes.
• Gives ask rules for recursive rm calls in the settings snippet.
• Disables auto compaction, with autoCompactEnabled set to false. It sets CLAUDE_CODE_AUTO_COMPACT_WINDOW and CLAUDE_CODE_MAX_CONTEXT_TOKENS to 300000. See Context-And-Handoff.
• Selects the output style dotclaude:Concise with the settings snippet. The style leads with the result and keeps replies short.
• Changes parts of the built-in system prompt and of the tool descriptions, through the Mod API. See Prompt-Surface.
• Gives Claude six agents, each with a model, an effort, and a turn limit: reviewer, implementer, debugger, investigator, planner, and researcher. See Agents.
• Writes the packages and the states of a change to the spec store with the dotclaude-spec CLI. See Spec-Store.
• Shows the folder, the git state, the spec change, the model and effort, the context, the cost, and the 5-hour limit. It shows them in a status line. See Status-Line.

The Plugins

The core plugin is dotclaude. Each add-on is a separate plugin. Each add-on works without the core plugin.

Plugin	What it does	Reference
dotclaude	The core plugin. It gives the output style, the agents, the guards, the status line, the handoff, and the drift check. It also gives the spec store and the second opinion from TypeSafe Jev (second_opinion).	Architecture, Second-Opinion
dotclaude-codegraph	Gives Claude the code graph of a project from the CodeGraph CLI codegraph.	Code-Graph
dotclaude-browser	Drives a browser with agent-browser. It answers each WebSearch call with a headless browser search.	Browser
dotclaude-docs	Gets current library and API docs with the Context7 CLI ctx7.	Library-Docs
dotclaude-sessions	Measures the start of a session by source, and the usage of each run.	Sessions
dotclaude-lab	Gives tools for plugin authors: a sandbox for Claude Code, a request capture, the JSON Schema of settings.json, and an eval compare.	Lab
dcc-plugin-agents-md	Loads AGENTS.md files where Claude Code loads CLAUDE.md.	AGENTS.md
dcc-plugin-you-should-know	Opt-in. Shows one thing to know before Claude changes something.	You Should Know

The marketplace and the install steps are in Add-Ons and Install.

The Principles

The design principles are on Design. These are five of them.

• Only documented extension points.
• No model call for a check that a script can make.
• One owner for each bound.
• Jev decides, and the user approves.
• Each plugin works alone.

Where to Read

Page	Read it to
Quickstart	See what happens in a first session.
Install	Install the marketplace and the plugins.
Architecture	See how the core plugin is built, from src/ to plugins/.
Guards	Learn what asks, what denies, and what the sandbox does.
Settings-Snippet	Copy the keys that Claude Code needs. See also Settings-Snippet-Keys and Settings-Schema.
Hook-Events	See the events that Claude Code sends, and the map to the dotclaude events.
Undocumented-Reads	See the settings and env vars that the binary reads and the docs do not name.
Troubleshooting	Fix a symptom.
Development and Sandbox	Change dotclaude and test a checkout.
Attributions	See the projects whose ideas dotclaude reimplements.

Concepts and Evidence

Page	What it holds
Design	The principles of dotclaude 1.0.0, and why each is in force.
Decisions	The design decisions D1 to D47.
Usage-Evidence	The plans, the prices, the models, and the usage of one measured week.
Prompt-Surface	The output style, the prompt sections, and the tool texts.
Request-Build	The system prompt sections, the attachments, and the cache of a request.
Evals	What the evals measure, and the Claude Code version that they need.
Release-History	What changed in each release, and why.

The CHANGELOG lists each release. The section of the version in package.json holds the changes of the release in progress until that version has a tag. After the tag, the [Unreleased] section holds the new changes.

Source Labels

The evidence pages label each fact with its source.

Label	Source
official	Anthropic documentation or support pages
binary	read from the installed Claude Code bundle, never patched
capture	a request body that Claude Code sent to a local listener
measured	a run or a transcript scan on the maintainer's machine
reported	user reports
inference	a conclusion from the facts above

The binary facts in this wiki are for Claude Code 2.1.296. The extracts of the bundle are in the git-ignored external/ folder, as Claude-Code-Internals describes.

Related Pages

• Install: install the marketplace and the plugins.
• Quickstart: see what happens in a first session.