|
<div class="docs-content" data-render>
|
|
# Claude Code setup
|
|
|
|
DevPlace ships a complete, version-controlled setup for [Claude Code](https://claude.com/claude-code),
|
|
Anthropic's command-line coding agent. Everything lives under the `.claude/`
|
|
directory in the repository root, so it is shared with every contributor through
|
|
git and applies the moment the repository is opened in Claude Code.
|
|
|
|
This setup mirrors the autonomous Python
|
|
[maintenance agents](/docs/maintenance-agents.html) and extends them into
|
|
feature work, all expressed in Claude Code's own primitives.
|
|
|
|
## What is in `.claude/`
|
|
|
|
| Path | Primitive | Purpose |
|
|
|------|-----------|---------|
|
|
| `.claude/agents/*.md` | Subagents | Ten single-dimension reviewers, one per quality dimension. See [Subagents](/docs/claude-agents.html). |
|
|
| `.claude/commands/*.md` | Slash commands | Lifecycle commands for understanding, building, verifying, testing, and operating. See [Commands](/docs/claude-commands.html). |
|
|
| `.claude/workflows/*.js` | Workflows | Deterministic multi-agent scripts for auditing and for building features. See [Workflows](/docs/claude-workflows.html). |
|
|
| `.claude/settings.local.json` | Settings | Local permission configuration. |
|
|
|
|
## Three layers of orchestration
|
|
|
|
The setup offers the same capability at three levels of control, from most
|
|
interactive to most deterministic.
|
|
|
|
1. **Subagents** are the building blocks. Each enforces exactly one quality
|
|
dimension (security, audit coverage, documentation, and so on) and can be
|
|
invoked on its own or spawned by anything else.
|
|
2. **Commands** are model-driven slash commands. Claude reads the command and acts
|
|
in the current conversation. They cover the everyday lifecycle (understand, build,
|
|
verify, test, operate) and orchestration (`/maintenance`). Best for a quick,
|
|
interactive step with a human in the loop.
|
|
3. **Workflows** are script-driven orchestration. A JavaScript file in
|
|
`.claude/workflows/` runs the same agents in a fixed, reproducible order, with
|
|
structured output and adversarial verification of every finding. Best for a
|
|
repeatable audit or a feature build.
|
|
|
|
## Relationship to the Python fleet
|
|
|
|
The repository also contains the standalone Python agent fleet in `agents/`, run
|
|
through the `make` targets (`make agents-all`, `make maintenance`). Both the
|
|
Python fleet and the Claude Code subagents enforce the **same ten quality
|
|
dimensions**; they differ only in the engine that runs them. The Python fleet uses
|
|
its own model engine and is suited to headless and continuous-integration runs;
|
|
the Claude Code setup runs inside an interactive Claude Code session and reuses its
|
|
tools and models.
|
|
|
|
The `agents/` directory is deliberately excluded from every reviewer in both
|
|
systems: it contains the very patterns the reviewers search for as detection data,
|
|
not as mistakes, so scanning it would produce false findings.
|
|
|
|
## Quick reference
|
|
|
|
- Run one dimension: mention the subagent, for example
|
|
`@agent-security-maintainer review the routers`.
|
|
- Orient on an area: `/explain <area>`, `/trace <route>`.
|
|
- Check or fix the whole fleet: `/maintenance`, `/maintenance fix`,
|
|
`/maintenance check changed`, `/maintenance fix security,audit`.
|
|
- Verified audit of all dimensions: `/fleet`. Review the current diff: `/review`.
|
|
- Build a feature end to end: `/feature add bookmarks to gists`.
|
|
- Scaffold one route, a Devii tool, or an async job:
|
|
`/endpoint`, `/devii-tool`, `/job-service`.
|
|
- Lighter build recipes: `/docs-page`, `/audit-event`, `/service`.
|
|
- Verify and run: `/serve`, `/screenshot <path>`, `/api-test`, `/validate`, `/test`.
|
|
|
|
The next pages document the subagents, the commands, and the workflows in full.
|
|
</div>
|