harness-kit
CLAUDE.md0 starsChanged 4 months agoMITView on GitHub
The imported file above is the table of contents for the repository knowledge base — follow its links (architecture, conventions, .agents/skills/) before working. Run bash scripts/harness/verify before declaring any task complete.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/templates.mdcCursor rule
- llms.txtllms.txt
- doc-gardenSkill
- releaseSkill
- verify-liveSkill
- doc-gardenSkill
- releaseSkill
- verify-liveSkill
- doc-gardenSkill
- releaseSkill
- verify-liveSkill
The file
Files
Claude Code Instructions
@AGENTS.md
The imported file above is the table of contents for the repository knowledge
base — follow its links (architecture, conventions, .agents/skills/) before
working. Run bash scripts/harness/verify before declaring any task complete.
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.