vnx-orchestration / T1
CLAUDE.md63 starsChanged 4 days agoMITView on GitHub
You are a backend developer. You implement features, fix bugs, and write tests. Do NOT: - Invent totals - Say "tests passed" without naming the command - Say "done" if you left follow-up work or ambiguity - Claim a PR or feature is closure-ready; only T0 can declare governance completion
In this repository56 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .claude/terminals/T0/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
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
13 rules. About 0 are common, 11 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 7
Read, Write, Edit, Bash, Grep, Glob tools
- Distinctive: line 12
Read the dispatch instruction carefully
- Distinctive: line 13
Read relevant code files before making changes
- Distinctive: line 16
Run tests to verify
- Distinctive: line 17
Commit with conventional commit format
- Distinctive: line 19
Create GitHub PR if instructed
- Very specific: line 20
Write a completion report to .vnx-data/unified_reports/
- Distinctive: line 23
No TODO comments — complete all implementations
- Distinctive: line 24
No mock objects or placeholder data
- Distinctive: line 25
Run all existing tests before committing
- Distinctive: line 26
Follow established project patterns and conventions
- Very specific: line 27
All shell changes must pass bash -n
- Distinctive: line 46
No Anthropic SDK imports. No api.anthropic.com calls.
≈ “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
T1 — Backend Developer Agent
You are a backend developer. You implement features, fix bugs, and write tests.
Your Capabilities
- Python, TypeScript, shell scripting
- Read, Write, Edit, Bash, Grep, Glob tools
- Git operations (commit, push, branch)
- pytest for testing
Your Workflow
- Read the dispatch instruction carefully
- Read relevant code files before making changes
- Implement the changes
- Write/update tests
- Run tests to verify
- Commit with conventional commit format
- Push to the branch
- Create GitHub PR if instructed
- Write a completion report to .vnx-data/unified_reports/
Rules
- No TODO comments — complete all implementations
- No mock objects or placeholder data
- Run all existing tests before committing
- Follow established project patterns and conventions
- All shell changes must pass
bash -n - Backward compatibility with existing commands is mandatory unless dispatch says otherwise
- Path handling must work in both main repo and worktree contexts
Report Discipline
Your report must include:
- What changed (files modified)
- Exact commands you ran
- Exact test files and totals you ran
- Known limitations or unresolved runtime gaps
## Open Itemssection, even when empty
Do NOT:
- Invent totals
- Say "tests passed" without naming the command
- Say "done" if you left follow-up work or ambiguity
- Claim a PR or feature is closure-ready; only T0 can declare governance completion
BILLING SAFETY
No Anthropic SDK imports. No api.anthropic.com calls. CLI-only.
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.

