vnx-orchestration / T0
CLAUDE.md63 starsChanged 4 days agoMITView on GitHub
DO NOT edit role-orchestrator.md inside a consumer project: edit it in the VNX keystone (github.com/Vinix24/vnx-orchestration) and run vnx role sync to propagate. Project-specific context goes BELOW the import, in its own section, and is the only sanctioned per-project deviation. --> @role-orchestrator.md
In this repository56 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .claude/terminals/T1/CLAUDE.mdCLAUDE.md
- .claude/terminals/T2/CLAUDE.mdCLAUDE.md
- .claude/terminals/T3/CLAUDE.mdCLAUDE.md
- api-developerSkill
- architectSkill
- backend-developerSkill
- control-centreSkill
- data-analystSkill
- database-engineerSkill
- debuggerSkill
- excel-reporterSkill
- fabric-referenceSkill
- featureplan-kickoffSkill
- frontend-developerSkill
- horizonSkill
- intelligence-engineerSkill
- monitoring-specialistSkill
- panelSkill
- performance-profilerSkill
- plannerSkill
- pmSkill
- python-optimizerSkill
- quality-engineerSkill
- refactor-safeSkill
- reviewerSkill
- security-engineerSkill
- supabase-expertSkill
- t0-orchestratorSkill
- test-engineerSkill
- vnx-managerSkill
- api-developerSkill
- architectSkill
- backend-developerSkill
- data-analystSkill
- database-engineerSkill
- debuggerSkill
- excel-reporterSkill
- fabric-referenceSkill
- featureplan-kickoffSkill
- frontend-developerSkill
- horizonSkill
- intelligence-engineerSkill
- monitoring-specialistSkill
- performance-profilerSkill
- plannerSkill
- pmSkill
- python-optimizerSkill
- quality-engineerSkill
- refactor-safeSkill
- reviewerSkill
- security-engineerSkill
- supabase-expertSkill
- t0-orchestratorSkill
- test-engineerSkill
- vnx-managerSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
DO NOT edit role-orchestrator.md inside a consumer project: edit it in the VNX keystone (github.com/Vinix24/vnx-orchestration) and run vnx …
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 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.
Files
<!--
Thin T0 pointer. The canonical orchestrator role lives in role-orchestrator.md
and is identical across the whole fleet — synced by `vnx role sync`.
DO NOT edit role-orchestrator.md inside a consumer project: edit it in the VNX
keystone (github.com/Vinix24/vnx-orchestration) and run `vnx role sync` to
propagate. Project-specific context goes BELOW the import, in its own section,
and is the only sanctioned per-project deviation.
-->@role-orchestrator.md
<!--
t0-orchestrator's SKILL.md body is intentionally NOT `@`-imported here.
It's not model-invocable (A-4, disable-model-invocation: true), so an
import used to sit on this line as a passive delivery path — but a
`@`-import of a file outside this directory tree (.claude/skills/... is a
sibling, not a descendant, of .claude/terminals/T0/) is classified by
Claude Code as an "external CLAUDE.md file import" and blocks session
start on an interactive trust prompt. A fresh autonomous T0 spawn has no
human to answer that prompt and just hangs (F1, 2026-07-16 live smoke
test). The playbook body now reaches T0 via the SessionStart hook instead
(`hooks/sessionstart.sh`, deployed fleet-wide as
`.claude/hooks/sessionstart.sh` by `vnx init`/`bootstrap_hooks`), which
injects it as additionalContext before the first prompt — no import, no
Skill-tool call, no prompt. See role-orchestrator.md's "Mandatory Startup".
-->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
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.

