agentleFS
Sign inStart free
saksham10arora-dotcomsaksham10arora-dotcom/everything-claude-codex/templates/CLAUDE.md

everything-claude-codex / templates

CLAUDE.md74 starsChanged 9 days agoMITView on GitHub

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask before changing my resume, sending anything, or deleting anything.

    line 27

≈ “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.md: {{NAME}}'s second brain

Who I am

<!-- Two or three lines: what you do, what you're aiming for, what you're great at. Claude reads this every session. -->

Context loading (every session, including after /compact)

  • .remember/hot.md is the source of truth for right now: deadlines, live projects, hard rules. It is injected at session start by the session_context hook.
  • Starting the day: /daily. End of session: /tldr.
  • Running in the cloud (Claude app / Claude Code on the web, laptop off)? Follow AGENTS.md section 7: boot from context/, save anything new as one note in inbox/.

Vault structure

inbox/      drop zone: everything new lands here first, sorted later
daily/      daily notes (YYYY-MM-DD.md)
projects/   builds and their status
personal/   people, opportunities, applications, resume, trackers
research/   deep dives and playbooks
wiki/       compiled knowledge base (/wiki)
content/    drafts, queue, published log
archive/    finished work: never deleted, just moved
context/    auto-generated mirror for phone agents (do not edit)

How I work

  • Capture first, organize later (inbox/).
  • Content must sound like me: Claude drafts, I edit.
  • Ask before changing my resume, sending anything, or deleting anything.

Talking to Codex (agent mail)

  • Send: python3 {{ECX}}/agent-sync/sync.py send --from claude --to codex --thread <topic> "message"
  • Unread mail is injected automatically. Readable log: agents/AGENT_CHAT.md.

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