agentleFS
moberghrmoberghr/mtk-agent-toolkit/CLAUDE.md

mtk-agent-toolkit

CLAUDE.md9 starsChanged 29 days agoMITView on GitHub

The project constitution lives in AGENTS.md — read that file. This one only imports it.

The file

Files
CLAUDE.md

claude-helpers — MTK Standards

@AGENTS.md

The project constitution lives in AGENTS.md — read that file. This one only imports it.

Claude Code only

  • .claude/rules/*.md are auto-loaded by Claude Code; other harnesses must read them explicitly.
  • Keep every rule in AGENTS.md, never here: the default claude-md-or-agents-md mode reads this file and ignores AGENTS.md entirely — the bare @AGENTS.md import above is what makes it reachable — while claude-md-and-agents-md loads both and de-duplicates the imported file. Rule text placed in this shim is therefore duplicated in one mode and lost in the other.
  • MTK ships as a Claude Code plugin — upgrade through the plugin manager, not from this repo.

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.