agentleFS
Ablation-LabAblation-Lab/claude-lore/.claude/CLAUDE.md

claude-lore

CLAUDE.md0 starsChanged 12 days agoMITView on GitHub

A Claude Code skill and an optional SessionStart hook that keep Claude's answers about Claude, Claude Code and the Claude apps tied to Anthropic's official sources.

  • In this repositoryOne other file it gives its agents.

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
  1. Very specific:

    Test against a throwaway folder by setting CLAUDE_CONFIG_DIR.

    line 7

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 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 Lore

A Claude Code skill and an optional SessionStart hook that keep Claude's answers about Claude, Claude Code and the Claude apps tied to Anthropic's official sources.

  • skills/lore-lookup/SKILL.md and README.md must describe the same behaviour. Whenever you edit one (or code that changes behaviour), check the other and update it in the same change. CONTRIBUTING.md has the checklist.
  • Plain Node 18+, built-in modules only. Run node --test after changes.
  • Test against a throwaway folder by setting CLAUDE_CONFIG_DIR. Never run hook-on, hook-off or install.mjs against the real ~/.claude unless asked.
  • The hook must print nothing, always exit 0, fetch successfully at most once a day, and retry at most once an hour while every page fails.

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.