Paste your CLAUDE.md across all four scopes. Toggle each on or off. See the concatenated context Claude Code actually loads, walk the subdirectory lazy-loading tree, resolve @-imports up to 5 hops. Everything runs in your browser — no signup, no upload, free. Compound tool for the CLAUDE.md guide.
Claude Code concatenates discovered CLAUDE.md files into context at session start — it doesn't pick one. When rules conflict, your last-read scope wins (by convention).
Toggle a scope on and start typing to see what Claude Code would concatenate into its context window.
Subdirectory CLAUDE.md files are lazy-loaded — Claude only concatenates them when it actually reads files inside that directory. Click a file in the tree to see the walk.
CLAUDE.md and CLAUDE.local.md from the file's directory upward to repo root. Plus any always-loaded scopes (Project root, User, Managed). Subdirectory files don't load until Claude reads inside them.Use @path/to/file.md to import another file's contents. Relative paths resolve against the importing file, not the working directory. Recursion stops after 5 hops.
Paste a CLAUDE.md with @ imports to see how Claude Code would expand it at session start.
Managed, Project, User, Local — each loaded scope gets concatenated into the context window. Nothing is overridden. When two files say opposite things, Claude arbitrates in the moment.
A /src/auth/CLAUDE.md only loads when Claude reads files inside /src/auth. Not at session start. Plan your nested files around what Claude touches, not what exists.
Imports resolve relative to the importing file. Recursion is bounded — if your import graph has cycles or nests deeper than 5, only part of your content ever reaches Claude's context.
No. Everything runs locally in your browser. There is no backend, no analytics call, no upload. You can pull the page offline and it keeps working.
Yes. Enterprise managed path is platform-specific (/Library/Application Support/ClaudeCode/CLAUDE.md on macOS, /etc/claude-code/CLAUDE.md on Linux/WSL, C:\Program Files\ClaudeCode\CLAUDE.md on Windows). Project CLAUDE.md can live at the repo root or inside ./.claude/. User scope is ~/.claude/CLAUDE.md. CLAUDE.local.md is gitignored by convention and appends after project CLAUDE.md at the same directory level.
It generates a starter ./CLAUDE.md at your repo root by analyzing your codebase. If one already exists, it suggests improvements rather than overwriting. You can run it any time; the playground is a faster way to iterate on the contents than re-running /init.
The documented behavior is "Claude may pick arbitrarily" on conflicts. In practice, later-read content tends to win (recency bias of language models), which is why Anthropic's docs note that CLAUDE.local.md is appended last at each directory level — it's where your personal overrides live. The safer fix: don't write conflicting rules across scopes in the first place.
Not yet — the scope model is Claude-specific. Copilot's equivalent is a single .github/copilot-instructions.md plus per-path .instructions.md files (see the Copilot Customization Kit). Cursor uses .cursor/rules/*.mdc files (see the Cursor Rules Kit). Different inheritance models; if enough people ask, a Cursor/Copilot playground is next.
Free. No signup. Same author.
Guess the prompt that produced an AI output. 30 puzzles, Wordle-style share, streak tracking.
Guide · 5 minThe pillar guide this playground was built to compound with. Six sections, copy-paste examples, update cadence.
Kit 001 · Free5 ready-to-drop CLAUDE.md templates, 10 slash commands, hooks cookbook, settings profiles.
Saved you time? Tip the maker in BTC — no account, no signup, just paste.
bc1qs04leape97ner4wqa98n94l9n0gv9aa84eg4ux