mayankjain1815-commitsmayankjain1815-commits/CITADEL/CLAUDE.md

CITADEL

CLAUDE.md4 starsChanged 4 months agoMITView on GitHub

An agent orchestration system for Claude Code. This repo IS the harness. The harness is a collection of skills, agents, hooks, and state files that enable Claude Code to operate autonomously on any codebase. It provides: - Intent routing (/do) that dispatches tasks to the right tool - Campaign persistence across sessions - Parallel agent coordination with discovery sharing - Automated quality enforcement through lifecycle hooks Always run tests after modifying hooks or skills. Five levels: Adding a new skill:…

In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architectSkill
- archonSkill
- ascii-diagramSkill
- autopilotSkill
- costSkill
- create-appSkill
- create-skillSkill
- daemonSkill
- dashboardSkill
- decision-mapSkill
- deploy-stewardSkill
- designSkill
- doc-genSkill
- doSkill
- evolveSkill
- experimentSkill
- fleetSkill
- grillSkill
- housecleanSkill
- improveSkill
- infra-auditSkill
- learnSkill
- live-previewSkill
- loopSkill
- mapSkill
- marshalSkill
- merge-reviewSkill
- organizeSkill
- postmortemSkill
- prdSkill
- pr-watchSkill
- qaSkill
- refactorSkill
- research-fleetSkill
- researchSkill
- reviewSkill
- scaffoldSkill
- scheduleSkill
- session-handoffSkill
- setupSkill
- systematic-debuggingSkill
- telemetrySkill
- test-genSkill
- triageSkill
- unharnessSkill
- verifySkill
- watchSkill
- wikiSkill
- workspaceSkill

The file

We split this CLAUDE.md into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Always run tests after modifying hooks or skills.
line 30
Very specific:
Adding a new skill: create skills/{name}/SKILL.md, then run node scripts/skill-lint.js {name} to verify structure.
line 43
Very specific:
Adding a benchmark scenario: create skills/{name}/__benchmarks__/{scenario}.md, then run node scripts/skill-bench.js --skill {name} to …
line 45
Distinctive:
Keep individual phases under 35 minutes of execution time.
line 51
Distinctive:
Every phase must have a verifiable exit condition -- binary pass/fail signals (typecheck, tests, build) are force multipliers on agent …
line 52
Very specific:
After completing any task, output a HANDOFF block:
line 58

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

CLAUDE.md

Claude Harness

An agent orchestration system for Claude Code. This repo IS the harness.

What This Is

The harness is a collection of skills, agents, hooks, and state files that enable Claude Code to operate autonomously on any codebase. It provides:

Intent routing (/do) that dispatches tasks to the right tool
Campaign persistence across sessions
Parallel agent coordination with discovery sharing
Automated quality enforcement through lifecycle hooks

Key Conventions

Skills live in skills/. Each skill is a directory skills/{name}/SKILL.md.
Agents live in agents/. They spawn as sub-processes with their own context.
Hooks live in hooks_src/. Installed per-project via scripts/install-hooks.js.
The init-project hook auto-scaffolds per-project state on session start:
- .planning/ — campaign state, fleet sessions, intake, telemetry
- .citadel/scripts/ — utility scripts (telemetry, coordination, compression)
- .claude/agent-context/ — rules injected into sub-agents
Campaign state lives in .planning/campaigns/ (per-project).
Fleet session state lives in .planning/fleet/ (per-project).
Templates live in .planning/_templates/ (copied from plugin on init).
Configuration lives in .claude/harness.json (generated by /do setup, per-project).

Testing

Always run tests after modifying hooks or skills. Five levels:

Command	What it checks	When to run
`node scripts/test-all.js`	Hooks + skill structure (fast, no LLM)	After any change
`node hooks_src/smoke-test.js`	Hooks only	After hook changes
`node scripts/verify-hooks.js`	Hook install + runtime (synthetic payloads, no LLM)	After hook changes
`node scripts/integration-test.js`	Full Pre→tool→Post pipeline sequences (no LLM)	After hook changes
`node scripts/skill-lint.js`	All SKILL.md structure	After skill changes
`node scripts/skill-bench.js`	Scenario file validity	After adding benchmarks
`node scripts/skill-bench.js --execute`	Live scenario execution	Before shipping
`node scripts/skill-bench.js --execute --verify-hooks`	Live execution + confirms hooks fired	Before shipping

Adding a new skill: create skills/{name}/SKILL.md, then run node scripts/skill-lint.js {name} to verify structure.

Adding a benchmark scenario: create skills/{name}/__benchmarks__/{scenario}.md, then run node scripts/skill-bench.js --skill {name} to validate.

CI: node scripts/test-all.js exits non-zero on any failure. Use --strict to treat WARNs as failures.

Campaign Design Principles

Keep individual phases under 35 minutes of execution time. Failure rate increases 4x beyond this boundary (Morph, 2026).
Every phase must have a verifiable exit condition -- binary pass/fail signals (typecheck, tests, build) are force multipliers on agent autonomy.
Skill SKILL.md files: terse and accurate only. Stale or vague guidance actively degrades agent accuracy. Update based on observed failures, not by accumulation.
Sub-agents have isolated context windows -- pass only distilled findings back to the orchestrator, never raw tool output.

Handoff Summary (Required)

After completing any task, output a HANDOFF block:

---HANDOFF---
- What was built or changed
- Key decisions and tradeoffs
- Unresolved items or next steps
---

3-5 bullets, under 150 words.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free