forked from retoor/devplacepy
- Add `cmd_isslop_prune`, `cmd_isslop_clear`, `cmd_isslop_analyze` CLI commands for AI usage analysis job management - Register `/game` router with `index` and `farm` endpoints for Code Farm idle game - Add `politics` to allowed TOPICS constant replacing `signals` - Introduce `ISSLOP_DIR`, `ISSLOP_WORKSPACES_DIR`, `ISSLOP_RUNS_DIR`, `ISSLOP_MEDIA_DIR` config paths - Add `clear_user_stars` and `clear_user_projects_cache` calls on vote and project create/delete - Update `make prod` to use `nproc` workers via `DEVPLACE_WEB_WORKERS` env var - Convert `database.py` and `utils.py` to packages for modular structure - Add `devplace apikey` and `devplace token` CLI subcommands for API key and access token management
57 lines
3.1 KiB
HTML
57 lines
3.1 KiB
HTML
<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 enforces the platform's ten quality dimensions 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 | Twelve single-dimension maintainers plus a feature builder and a live-API operator. 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.
|
|
|
|
## 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`.
|
|
|
|
New to the setup? The [Manual](/docs/claude-manual.html) is the task-oriented guide:
|
|
how to add a feature, change existing code, fix an issue, verify, test, and review,
|
|
step by step. The remaining pages are the full reference for the subagents, the
|
|
commands, and the workflows.
|
|
</div>
|