> ## Documentation Index
> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# .claude ディレクトリを探索する
> Claude Code が CLAUDE.md、settings.json、hooks、skills、commands、subagents、workflows、rules、auto memory を読み込む場所。プロジェクト内の .claude ディレクトリとホームディレクトリの ~/.claude を探索します。
export const ClaudeExplorer = () => {
const A = useMemo(() => ({href, children}) => {children}, []);
const C = useMemo(() => ({children}) => {children}, []);
const commandsNote = useMemo(() => <>Commands and skills are now the same mechanism. For new workflows, use skills/ instead: same /name invocation, plus you can bundle supporting files., []);
const FILE_TREE = useMemo(() => ({
project: {
label: 'your-project/',
children: [{
id: 'claude-md',
label: 'CLAUDE.md',
type: 'file',
icon: 'md',
color: '#6A9BCC',
badge: 'committed',
oneLiner: 'Project instructions Claude reads every session',
when: 'Loaded into context at the start of every session',
description: 'Project-specific instructions that shape how Claude works in this repository. Put your conventions, common commands, and architectural context here so Claude operates with the same assumptions your team does.',
tips: ['Target under 200 lines. Longer files still load in full but may reduce adherence', <>CLAUDE.md loads into every session. If something only matters for specific tasks, move it to a skill or a path-scoped rule so it loads only when needed, 'List the commands you run most, like build, test, and format, so Claude knows them without you spelling them out each time', <>Run /memory to open and edit CLAUDE.md from within a session, <>Also works at .claude/CLAUDE.md if you prefer to keep the project root clean],
exampleIntro: 'This example is for a TypeScript and React project. It lists the build and test commands, the framework conventions Claude should follow, and project-specific rules like export style and file layout.',
example: `# Project conventions
## Commands
- Build: \`npm run build\`
- Test: \`npm test\`
- Lint: \`npm run lint\`
## Stack
- TypeScript with strict mode
- React 19, functional components only
## Rules
- Named exports, never default exports
- Tests live next to source: \`foo.ts\` -> \`foo.test.ts\`
- All API routes return \`{ data, error }\` shape`,
docsLink: '/en/memory'
}, {
id: 'mcp-json',
label: '.mcp.json',
type: 'file',
icon: 'json',
color: '#9B7BC4',
badge: 'committed',
oneLiner: 'Project-scoped MCP servers, shared with your team',
when: <>Servers connect when the session begins. Tool schemas are deferred by default and load on demand via tool search,
description: <>Configures Model Context Protocol (MCP) servers that give Claude access to external tools: databases, APIs, browsers, and more. This file holds the project-scoped servers your whole team uses. Personal servers you want to keep to yourself go in ~/.claude.json instead.,
tips: [<>Use environment variable references for secrets: {'${GITHUB_TOKEN}'}, <>Lives at the project root, not inside .claude/, <>For servers only you need, run claude mcp add --scope user. This writes to ~/.claude.json instead of .mcp.json],
exampleIntro: <>This example configures the GitHub MCP server so Claude can read issues and open pull requests. The {'${GITHUB_TOKEN}'} reference is read from your shell environment when Claude Code starts the server, so the token never lands in the file.,
example: `{
"mcpServers": {
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_TOKEN": "\${GITHUB_TOKEN}"
}
}
}
}`,
docsLink: '/en/mcp'
}, {
id: 'worktreeinclude',
label: '.worktreeinclude',
type: 'file',
icon: 'md',
color: '#8FA876',
badge: 'committed',
oneLiner: 'Gitignored files to copy into new worktrees',
when: <>Read when Claude creates a git worktree via --worktree, the EnterWorktree tool, or subagent isolation: worktree,
description: <>Lists gitignored files to copy from your main repository into each new worktree. Worktrees are fresh checkouts, so untracked files like .env are missing by default. Patterns here use .gitignore syntax. Only files that match a pattern and are also gitignored get copied, so tracked files are never duplicated.,
tips: [<>Lives at the project root, not inside .claude/, <>Git-only: if you configure a WorktreeCreate hook for a different VCS, this file is not read. Copy files inside your hook script instead, <>Also applies to parallel sessions in the desktop app],
exampleIntro: 'This example copies your local environment files and a secrets config into every worktree Claude creates. Comments start with # and blank lines are ignored, same as .gitignore.',
example: `# Local environment
.env
.env.local
# API credentials
config/secrets.json`,
docsLink: '/en/worktrees#copy-gitignored-files-into-worktrees'
}, {
id: 'dot-claude',
label: '.claude/',
type: 'folder',
icon: 'folder',
color: 'var(--ce-accent)',
oneLiner: 'Project-level configuration, rules, and extensions',
description: 'Everything Claude Code reads that is specific to this project. If you use git, commit most files here so your team shares them; a few, like settings.local.json, are automatically gitignored. Each file badge shows which.',
children: [{
id: 'settings-json',
label: 'settings.json',
type: 'file',
icon: 'json',
color: 'var(--ce-text-3)',
badge: 'committed',
oneLiner: 'Permissions, hooks, and configuration',
when: <>Overrides global ~/.claude/settings.json. Local settings, CLI flags, and managed settings override this,
description: 'Settings that Claude Code applies directly. Permissions control which commands and tools Claude can use; hooks run your scripts at specific points in a session. Unlike CLAUDE.md, which Claude reads as guidance, these are enforced whether Claude follows them or not.',
contains: [<>permissions: allow, deny, or prompt before Claude uses specific tools or commands, <>hooks: run your own scripts on events like before a tool call or after a file edit, <>statusLine: customize the line shown at the bottom while Claude works, <>model: pick a default model for this project, <>env: environment variables set in every session, <>outputStyle: select a custom system-prompt style from output-styles/],
tips: [<>Bash permission patterns support wildcards: Bash(npm test *) matches any command starting with npm test, <>Array settings like permissions.allow combine across all scopes; scalar settings like model use the most specific value],
exampleIntro: <>This example allows npm test and npm run commands without prompting, blocks rm -rf, and runs Prettier on files after Claude edits or writes them.,
example: `{
"permissions": {
"allow": [
"Bash(npm test *)",
"Bash(npm run *)"
],
"deny": [
"Bash(rm -rf *)"
]
},
"hooks": {
"PostToolUse": [{
"matcher": "Edit|Write",
"hooks": [{
"type": "command",
"command": "jq -r '.tool_input.file_path' | xargs npx prettier --write"
}]
}]
}
}`,
docsLink: '/en/settings'
}, {
id: 'settings-local-json',
label: 'settings.local.json',
type: 'file',
icon: 'json',
color: 'var(--ce-text-3)',
badge: 'gitignored',
oneLiner: 'Your personal settings overrides for this project',
when: 'Highest of the user-editable settings files; CLI flags and managed settings still take precedence',
description: 'Personal settings that take precedence over the project defaults. Same JSON format as settings.json, but not committed. Use this when you need different permissions or defaults than the team config.',
tips: [<>Same schema as settings.json. Array settings like permissions.allow combine across scopes; scalar settings like model use the local value, <>Claude Code adds this file to ~/.config/git/ignore the first time it writes one. If you use a custom core.excludesFile, add the pattern there too. To share the ignore rule with your team, also add it to the project .gitignore],
exampleIntro: 'This example adds Docker permissions on top of whatever the team settings.json allows.',
example: `{
"permissions": {
"allow": [
"Bash(docker *)"
]
}
}`,
docsLink: '/en/settings'
}, {
id: 'rules',
label: 'rules/',
type: 'folder',
icon: 'folder',
color: '#9B7BC4',
oneLiner: 'Topic-scoped instructions, optionally gated by file paths',
when: <>Rules without paths: load at session start. Rules with paths: load when a matching file enters context,
description: [<>Project instructions split into topic files that can load conditionally based on file paths. A rule without paths: frontmatter loads at session start like CLAUDE.md; a rule with paths: loads only when Claude reads a matching file., <>Like CLAUDE.md, rules are guidance Claude reads, not configuration Claude Code enforces. For guaranteed behavior use hooks or permissions.],
tips: [<>Use paths: frontmatter with globs to scope rules to directories or file types, <>Subdirectories work: .claude/rules/frontend/react.md is discovered automatically, 'When CLAUDE.md approaches 200 lines, start splitting into rules'],
docsLink: '/en/memory#organize-rules-with-claude/rules/',
children: [{
id: 'rule-testing',
label: 'testing.md',
type: 'file',
icon: 'md',
color: '#9B7BC4',
badge: 'committed',
oneLiner: 'Test conventions scoped to test files',
when: <>Loaded when Claude reads a file matching the paths: globs below,
description: <>An example rule that only loads when Claude is working on test files. The paths: globs in the frontmatter define which files trigger it; here, anything ending in .test.ts or .test.tsx. For other files, this rule is not loaded into context.,
example: `---
paths:
- "**/*.test.ts"
- "**/*.test.tsx"
---
# Testing Rules
- Use descriptive test names: "should [expected] when [condition]"
- Mock external dependencies, not internal modules
- Clean up side effects in afterEach`
}, {
id: 'rule-api',
label: 'api-design.md',
type: 'file',
icon: 'md',
color: '#9B7BC4',
badge: 'committed',
oneLiner: 'API conventions scoped to backend code',
when: <>Loaded when Claude reads a file matching the paths: glob below,
description: <>A second example showing a rule scoped to backend code. The paths: glob matches files under src/api/, so these conventions load only when Claude is editing API routes.,
example: `---
paths:
- "src/api/**/*.ts"
---
# API Design Rules
- All endpoints must validate input with Zod schemas
- Return shape: { data: T } | { error: string }
- Rate limit all public endpoints`
}]
}, {
id: 'skills',
label: 'skills/',
type: 'folder',
icon: 'folder',
color: '#D4A843',
oneLiner: 'Reusable prompts you or Claude invoke by name',
when: <>Invoked with /skill-name or when Claude matches the task to a skill,
description: <>Each skill is a folder with a SKILL.md file plus any supporting files it needs. By default, both you and Claude can invoke a skill. Use frontmatter to control that: disable-model-invocation: true for user-only workflows like /deploy, or user-invocable: false to hide from the / menu while Claude can still invoke it.,
tips: [<>Skills accept arguments: /deploy staging passes "staging" as $ARGUMENTS. Use $0, $1, and so on for positional access, <>The description frontmatter determines when Claude auto-invokes the skill, 'Bundle reference docs alongside SKILL.md. Claude knows the skill directory path and can read supporting files when you mention them'],
docsLink: '/en/skills',
children: [{
id: 'skill-review',
label: 'security-review/',
type: 'folder',
icon: 'folder',
color: '#D4A843',
oneLiner: 'A skill bundling SKILL.md with supporting files',
children: [{
id: 'skill-review-md',
label: 'SKILL.md',
type: 'file',
icon: 'md',
color: '#D4A843',
badge: 'committed',
oneLiner: 'Entrypoint: trigger, invocability, instructions',
when: <>User types /security-review <target>; Claude cannot auto-invoke this skill,
description: [<>This skill uses disable-model-invocation: true so only you can trigger it; Claude never invokes it on its own., <>The !`...` line runs a shell command and injects its output into the prompt. $ARGUMENTS substitutes whatever you typed after the skill name. Claude sees the skill directory path, so mentioning a bundled file like checklist.md lets Claude read it.],
example: `---
description: Reviews code changes for security vulnerabilities, authentication gaps, and injection risks
disable-model-invocation: true
argument-hint:
---
## Diff to review
!\`git diff $ARGUMENTS\`
Audit the changes above for:
1. Injection vulnerabilities (SQL, XSS, command)
2. Authentication and authorization gaps
3. Hardcoded secrets or credentials
Use checklist.md in this skill directory for the full review checklist.
Report findings with severity ratings and remediation steps.`
}, {
id: 'skill-checklist',
label: 'checklist.md',
type: 'file',
icon: 'md',
color: '#D4A843',
badge: 'committed',
oneLiner: 'Supporting file bundled with the skill',
when: 'Claude reads it on demand while running the skill',
description: <>Skills can bundle any supporting files: reference docs, templates, scripts. The skill directory path is prepended to SKILL.md, so Claude can read bundled files by name. For scripts in bash injection commands, use the {'${CLAUDE_SKILL_DIR}'} placeholder.,
example: `# Security Review Checklist
## Input Validation
- [ ] All user input sanitized before DB queries
- [ ] File upload MIME types validated
- [ ] Path traversal prevented on file operations
## Authentication
- [ ] JWT tokens expire after 24 hours
- [ ] API keys stored in environment variables
- [ ] Passwords hashed with bcrypt or argon2`
}]
}]
}, {
id: 'commands',
label: 'commands/',
type: 'folder',
icon: 'folder',
color: '#788C5D',
oneLiner: <>Single-file prompts invoked with /name,
note: commandsNote,
when: <>User types /command-name,
description: <>A file at commands/deploy.md creates /deploy the same way a skill at skills/deploy/SKILL.md does, and both can be auto-invoked by Claude. Skills use a directory with SKILL.md, letting you bundle reference docs, templates, or scripts alongside the prompt.,
tips: [<>Use $ARGUMENTS in the file to accept parameters: /fix-issue 123, 'If a skill and command share a name, the skill takes precedence', 'New commands should usually be skills instead; commands remain supported'],
docsLink: '/en/skills',
children: [{
id: 'cmd-example',
label: 'fix-issue.md',
type: 'file',
icon: 'md',
color: '#788C5D',
badge: 'committed',
oneLiner: <>Invoked as /fix-issue <number>,
note: commandsNote,
description: [<>An example command for fixing a GitHub issue. Type /fix-issue 123 and the !`...` line runs gh issue view 123 in your shell, injecting the output into the prompt before Claude sees it., <>$ARGUMENTS substitutes whatever you typed after the command name. For positional access, use $0$1 and so on.],
example: `---
argument-hint:
---
!\`gh issue view $ARGUMENTS\`
Investigate and fix the issue above.
1. Trace the bug to its root cause
2. Implement the fix
3. Write or update tests
4. Summarize what you changed and why`
}]
}, {
id: 'output-styles',
label: 'output-styles/',
type: 'folder',
icon: 'folder',
color: '#5AA7A7',
oneLiner: 'Project-scoped output styles, if your team shares any',
when: 'Applied at session start when selected via the outputStyle setting',
description: <>Output styles are usually personal, so most live in ~/.claude/output-styles/. Put one here if your team shares a style, like a review mode everyone uses. See the Global tab for the full explanation and example.,
docsLink: '/en/output-styles',
children: []
}, {
id: 'agents',
label: 'agents/',
type: 'folder',
icon: 'folder',
color: '#C46686',
oneLiner: 'Specialized subagents with their own context window',
when: 'Runs in its own context window when you or Claude invoke it',
description: 'Each markdown file defines a subagent with its own system prompt, tool access, and optionally its own model. Subagents run in a fresh context window, keeping the main conversation clean. Useful for parallel work or isolated tasks.',
tips: ['Each agent gets a fresh context window, separate from your main session', <>Restrict tool access per agent with the tools: frontmatter field, 'Type @ and pick an agent from the autocomplete to delegate directly'],
docsLink: '/en/sub-agents',
children: [{
id: 'agent-reviewer',
label: 'code-reviewer.md',
type: 'file',
icon: 'md',
color: '#C46686',
badge: 'committed',
oneLiner: 'Subagent for isolated code review',
when: 'Claude spawns it for review tasks, or you @-mention it from the autocomplete',
description: <>An example subagent restricted to read-only tools. The description frontmatter tells Claude when to delegate to it automatically; tools: limits it to Read, Grep, and Glob so it can inspect code but never edit. The body becomes the subagent's system prompt.,
example: `---
name: code-reviewer
description: Reviews code for correctness, security, and maintainability
tools: Read, Grep, Glob
---
You are a senior code reviewer. Review for:
1. Correctness: logic errors, edge cases, null handling
2. Security: injection, auth bypass, data exposure
3. Maintainability: naming, complexity, duplication
Every finding must include a concrete fix.`
}]
}, {
id: 'workflows',
label: 'workflows/',
type: 'folder',
icon: 'folder',
color: '#C46686',
oneLiner: 'Dynamic workflow scripts that orchestrate many subagents',
when: 'Loaded at startup; each file becomes a / command',
description: <>Each .js file is a dynamic workflow: a script the runtime executes to spawn and coordinate many subagents. Workflows are written by Claude and saved here from /workflows rather than authored from scratch.,
tips: [<>Save a run from /workflows with s to create one of these, <>A project workflow takes precedence over a personal one in ~/.claude/workflows/ with the same name],
docsLink: '/en/workflows'
}, {
id: 'agent-memory',
label: 'agent-memory/',
type: 'folder',
icon: 'folder',
color: '#C46686',
badge: 'committed',
autogen: true,
oneLiner: 'Subagent persistent memory, separate from your main session auto memory',
when: 'First 200 lines (capped at 25KB) of MEMORY.md loaded into the subagent system prompt when it runs',
description: <>Subagents with memory: project in their frontmatter get a dedicated memory directory here. This is distinct from your main session auto memory at ~/.claude/projects/: each subagent reads and writes its own MEMORY.md, not yours.,
tips: [<>Only created for subagents that set the memory: frontmatter field, <>This directory holds project-scoped subagent memory, meant to be shared with your team. To keep memory out of version control use memory: local, which writes to .claude/agent-memory-local/ instead. For cross-project memory use memory: user, which writes to ~/.claude/agent-memory/, <>The main session auto memory is a different feature; see ~/.claude/projects/ in the Global tab],
docsLink: '/en/sub-agents#enable-persistent-memory',
children: [{
id: 'agent-memory-sub',
label: '/',
type: 'folder',
icon: 'folder',
color: '#C46686',
autogen: true,
children: [{
id: 'agent-memory-md',
label: 'MEMORY.md',
type: 'file',
icon: 'md',
color: '#C46686',
badge: 'committed',
autogen: true,
oneLiner: 'The subagent writes and maintains this file automatically',
when: 'Loaded into the subagent system prompt when the subagent starts',
description: <>Works the same as your main auto memory: the subagent creates and updates this file itself. You do not write it. The subagent reads it at the start of each task and writes back what it learns.,
example: `# code-reviewer memory
## Patterns seen
- Project uses custom Result type, not exceptions
- Auth middleware expects Bearer token in Authorization header
- Tests use factory functions in test/factories/
## Recurring issues
- Missing null checks on API responses (src/api/*)
- Unhandled promise rejections in background jobs`
}]
}]
}]
}]
},
global: {
label: '~/',
children: [{
id: 'claude-json',
label: '.claude.json',
type: 'file',
icon: 'json',
color: 'var(--ce-text-3)',
badge: 'local',
oneLiner: 'App state and UI preferences',
when: <>Read at session start for your preferences and MCP servers. Claude Code writes back to it when you change settings in /config or approve trust prompts,
description: <>Holds state that does not belong in settings.json: theme, OAuth session, per-project trust decisions, your personal MCP servers, and UI toggles. Mostly managed through /config rather than editing directly.,
tips: [<>IDE toggles like autoConnectIde and externalEditorContext live here, not in settings.json, <>The projects key tracks per-project state like trust-dialog acceptance and last-session metrics. Permission rules you approve in-session go to .claude/settings.local.json instead, <>MCP servers here are yours only: user scope applies across all projects, local scope is per-project but not committed. Team-shared servers go in .mcp.json at the project root instead],
example: `{
"autoConnectIde": true,
"externalEditorContext": true,
"mcpServers": {
"my-tools": {
"command": "npx",
"args": ["-y", "@example/mcp-server"]
}
}
}`,
docsLink: '/en/settings#global-config-settings'
}, {
id: 'global-dot-claude',
label: '.claude/',
type: 'folder',
icon: 'folder',
color: 'var(--ce-accent)',
oneLiner: 'Your personal configuration across all projects',
description: 'The global counterpart to your project .claude/ directory. Files here apply to every project you work in and are never committed to any repository.',
children: [{
id: 'global-claude-md',
label: 'CLAUDE.md',
type: 'file',
icon: 'md',
color: '#6A9BCC',
badge: 'local',
oneLiner: 'Personal preferences across every project',
when: 'Loaded at the start of every session, in every project',
description: 'Your global instruction file. Loaded alongside the project CLAUDE.md at session start, so both are in context together. When instructions conflict, project-level instructions take priority. Keep this to preferences that apply everywhere: response style, commit format, personal conventions.',
tips: ['Keep it short since it loads into context for every project, alongside that project\'s own CLAUDE.md', 'Good for response style, commit format, and personal conventions'],
example: `# Global preferences
- Keep explanations concise
- Use conventional commit format
- Show the terminal command to verify changes
- Prefer composition over inheritance`,
docsLink: '/en/memory'
}, {
id: 'global-settings',
label: 'settings.json',
type: 'file',
icon: 'json',
color: 'var(--ce-text-3)',
badge: 'local',
oneLiner: 'Default settings for all projects',
when: 'Your defaults. Project and local settings.json override any keys you also set there',
description: [<>Same keys as project settings.json: permissions, hooks, model, environment variables, and the rest. Put settings here that you want in every project, like permissions you always allow, a preferred model, or a notification hook that runs regardless of which project you're in., <>Settings follow a precedence order: project settings.json overrides any matching keys you set here. This is different from CLAUDE.md, where global and project files are both loaded into context rather than merged key by key.],
example: `{
"permissions": {
"allow": [
"Bash(git log *)",
"Bash(git diff *)"
]
}
}`,
docsLink: '/en/settings'
}, {
id: 'keybindings',
label: 'keybindings.json',
type: 'file',
icon: 'json',
color: 'var(--ce-text-3)',
badge: 'local',
oneLiner: 'Custom keyboard shortcuts',
when: 'Read at session start and hot-reloaded when you edit the file',
description: <>Rebind keyboard shortcuts in the interactive CLI. Run /keybindings to create or open this file with a schema reference. Ctrl+C, Ctrl+D, Ctrl+M, and Caps Lock are reserved and cannot be rebound.,
exampleIntro: <>This example binds Ctrl+E to open your external editor and unbinds Ctrl+U by setting it to null. The context field scopes bindings to a specific part of the CLI, here the main chat input.,
example: `{
"$schema": "https://www.schemastore.org/claude-code-keybindings.json",
"$docs": "https://code.claude.com/docs/en/keybindings",
"bindings": [
{
"context": "Chat",
"bindings": {
"ctrl+e": "chat:externalEditor",
"ctrl+u": null
}
}
]
}`,
docsLink: '/en/keybindings'
}, {
id: 'themes',
label: 'themes/',
type: 'folder',
icon: 'folder',
color: '#5AA7A7',
oneLiner: 'Custom color themes',
when: <>Read at session start and hot-reloaded when files change. Listed in /theme,
description: <>Each .json file defines a custom color theme: a built-in base preset plus an overrides map of color tokens. Create one interactively with /theme or write the JSON by hand. Selecting a custom theme stores custom:<slug> as your theme preference.,
example: `{
"name": "Dracula",
"base": "dark",
"overrides": {
"claude": "#bd93f9",
"error": "#ff5555",
"success": "#50fa7b"
}
}`,
docsLink: '/en/terminal-config#create-a-custom-theme',
children: []
}, {
id: 'global-projects',
label: 'projects/',
type: 'folder',
icon: 'folder',
color: '#E8A45C',
autogen: true,
oneLiner: "Auto memory: Claude's notes to itself, per project",
when: 'MEMORY.md loaded at session start; topic files read on demand',
description: 'Auto memory lets Claude accumulate knowledge across sessions without you writing anything. Claude saves notes as it works: build commands, debugging insights, architecture notes. Each project gets its own memory directory keyed by the repository path.',
tips: [<>On by default. Toggle with /memory or autoMemoryEnabled in settings, 'MEMORY.md is the index loaded each session. The first 200 lines, or 25KB, whichever comes first, are read', 'Topic files like debugging.md are read on demand, not at startup', 'These are plain markdown. Edit or delete them anytime'],
docsLink: '/en/memory#auto-memory',
children: [{
id: 'memory-dir',
label: '/memory/',
type: 'folder',
icon: 'folder',
color: '#E8A45C',
autogen: true,
oneLiner: "Claude's accumulated knowledge for one project",
children: [{
id: 'memory-md',
label: 'MEMORY.md',
type: 'file',
icon: 'md',
color: '#E8A45C',
badge: 'local',
autogen: true,
oneLiner: 'Claude writes and maintains this file automatically',
when: 'First 200 lines (capped at 25KB) loaded at session start',
description: 'Claude creates and updates this file as it works; you do not write it yourself. It acts as an index that Claude reads at the start of every session, pointing to topic files for detail. You can edit or delete it, but Claude will keep updating it.',
example: `# Memory Index
## Project
- [build-and-test.md](build-and-test.md): npm run build (~45s), Vitest, dev server on 3001
- [architecture.md](architecture.md): API client singleton, refresh-token auth
## Reference
- [debugging.md](debugging.md): auth token rotation and DB connection troubleshooting`,
docsLink: '/en/memory'
}, {
id: 'memory-topic',
label: 'debugging.md',
type: 'file',
icon: 'md',
color: '#E8A45C',
badge: 'local',
autogen: true,
oneLiner: 'Topic notes Claude writes when MEMORY.md gets long',
when: 'Claude reads this when a related task comes up',
description: 'An example of a topic file Claude creates when MEMORY.md grows too long. Claude picks the filename based on what it splits out: debugging.md, architecture.md, build-commands.md, or similar. You never create these yourself. Claude reads a topic file back only when the current task relates to it.',
example: `---
name: Debugging patterns
description: Auth token rotation and database connection troubleshooting for this project
type: reference
---
## Auth Token Issues
- Refresh token rotation: old token invalidated immediately
- If 401 after refresh: check clock skew between client and server
## Database Connection Drops
- Connection pool: max 10 in dev, 50 in prod
- Always check \`docker compose ps\` first`
}]
}]
}, {
id: 'global-rules',
label: 'rules/',
type: 'folder',
icon: 'folder',
color: '#9B7BC4',
oneLiner: 'User-level rules that apply to every project',
when: <>Rules without paths: load at session start. Rules with paths: load when a matching file enters context,
description: 'Same as project .claude/rules/ but applies everywhere. Use this for conventions you want across all your work, like personal code style or commit message format.',
docsLink: '/en/memory#organize-rules-with-claude/rules/',
children: []
}, {
id: 'global-skills',
label: 'skills/',
type: 'folder',
icon: 'folder',
color: '#D4A843',
oneLiner: 'Personal skills available in every project',
when: <>Invoked with /skill-name in any project,
description: 'Skills you built for yourself that work everywhere. Same structure as project skills: each is a folder with SKILL.md, scoped to your user account instead of a single project.',
docsLink: '/en/skills',
children: []
}, {
id: 'global-commands',
label: 'commands/',
type: 'folder',
icon: 'folder',
color: '#788C5D',
oneLiner: 'Personal single-file commands available in every project',
note: commandsNote,
when: <>User types /command-name in any project,
description: 'Same as project commands/ but scoped to your user account. Each markdown file becomes a command available everywhere.',
docsLink: '/en/skills',
children: []
}, {
id: 'global-output-styles',
label: 'output-styles/',
type: 'folder',
icon: 'folder',
color: '#5AA7A7',
oneLiner: 'Custom system-prompt sections that adjust how Claude works',
when: 'Applied at session start when selected via the outputStyle setting',
description: [<>Each markdown file defines an output style: a section appended to the system prompt that, by default, also drops the built-in software-engineering task instructions. Use this to adapt Claude Code for uses beyond coding, or to add teaching or review modes., <>Select a built-in or custom style with /config or the outputStyle key in settings. Styles here are available in every project; project-level styles with the same name take precedence.],
tips: ['Built-in styles Explanatory and Learning are included with Claude Code; custom styles go here', <>Set keep-coding-instructions: true in frontmatter to keep the default task instructions alongside your additions, 'Changes take effect on the next session since the system prompt is fixed at startup for caching'],
docsLink: '/en/output-styles',
children: [{
id: 'output-style-example',
label: 'teaching.md',
type: 'file',
icon: 'md',
color: '#5AA7A7',
badge: 'local',
oneLiner: 'Example style that adds explanations and leaves small changes for you',
when: <>Active when outputStyle in settings is set to teaching,
description: <>This style appends instructions to the system prompt: Claude adds a "Why this approach" note after each task and leaves TODO(human) markers for changes under 10 lines instead of writing them itself. Select it by setting outputStyle to the filename without .md, or to the name field if you set one in frontmatter.,
example: `---
description: Explains reasoning and asks you to implement small pieces
keep-coding-instructions: true
---
After completing each task, add a brief "Why this approach" note
explaining the key design decision.
When a change is under 10 lines, ask the user to implement it
themselves by leaving a TODO(human) marker instead of writing it.`
}]
}, {
id: 'global-agents',
label: 'agents/',
type: 'folder',
icon: 'folder',
color: '#C46686',
oneLiner: 'Personal subagents available in every project',
when: 'Claude delegates or you @-mention in any project',
description: 'Subagents defined here are available across all your projects. Same format as project agents.',
docsLink: '/en/sub-agents',
children: []
}, {
id: 'global-workflows',
label: 'workflows/',
type: 'folder',
icon: 'folder',
color: '#C46686',
oneLiner: 'Personal dynamic workflows available in every project',
when: 'Loaded at startup; each file becomes a / command',
description: <>Workflow scripts saved here are available across all your projects. A project workflow with the same name in .claude/workflows/ takes precedence.,
docsLink: '/en/workflows',
children: []
}, {
id: 'global-agent-memory',
label: 'agent-memory/',
type: 'folder',
icon: 'folder',
color: '#C46686',
autogen: true,
oneLiner: <>Persistent memory for subagents with memory: user,
when: 'Loaded into the subagent system prompt when the subagent starts',
description: <>Subagents with memory: user in their frontmatter store knowledge here that persists across all projects. For project-scoped subagent memory, see .claude/agent-memory/ instead.,
docsLink: '/en/sub-agents#enable-persistent-memory',
children: []
}]
}]
}
}), []);
const BADGE_STYLES = useMemo(() => ({
committed: {
bg: 'rgba(85,138,66,0.08)',
color: 'var(--ce-badge-committed)',
border: 'rgba(85,138,66,0.15)',
label: 'committed'
},
gitignored: {
bg: 'rgba(217,119,87,0.06)',
color: 'var(--ce-badge-gitignored)',
border: 'rgba(217,119,87,0.15)',
label: 'gitignored'
},
local: {
bg: 'rgba(115,114,108,0.06)',
color: 'var(--ce-badge-local)',
border: 'rgba(115,114,108,0.12)',
label: 'local only'
},
autogen: {
bg: 'rgba(232,164,92,0.1)',
color: 'var(--ce-badge-autogen)',
border: 'rgba(232,164,92,0.2)',
label: 'Claude writes'
}
}), []);
const allNodes = useMemo(() => {
const flatten = (nodes, acc, path, parentId) => {
for (const node of nodes) {
const nextPath = [...path, node.label];
acc[node.id] = {
...node,
path: nextPath,
parentId
};
if (node.children) flatten(node.children, acc, nextPath, node.id);
}
return acc;
};
const project = flatten(FILE_TREE.project.children, {}, [FILE_TREE.project.label]);
const global = flatten(FILE_TREE.global.children, {}, [FILE_TREE.global.label]);
for (const id in project) project[id].root = 'project';
for (const id in global) global[id].root = 'global';
return {
...project,
...global
};
}, [FILE_TREE]);
const allFolderIds = useMemo(() => Object.keys(allNodes).filter(id => allNodes[id].type === 'folder'), [allNodes]);
const DEFAULT_EXPANDED = ['dot-claude', 'rules', 'skills', 'skill-review', 'commands', 'agents', 'agent-memory', 'agent-memory-sub', 'global-dot-claude', 'global-output-styles', 'global-projects', 'memory-dir'];
const [mounted, setMounted] = useState(false);
const [activeRoot, setActiveRoot] = useState('project');
const [selectedId, setSelectedId] = useState('claude-md');
const [expandedFolders, setExpandedFolders] = useState(() => new Set(DEFAULT_EXPANDED));
const [forceMobile, setForceMobile] = useState(false);
const [copiedId, setCopiedId] = useState(null);
const [isFullscreen, setIsFullscreen] = useState(false);
const copyTimeoutRef = useRef(null);
const rootRef = useRef(null);
useEffect(() => {
setMounted(true);
const applyHash = scroll => {
const hash = window.location.hash.slice(1);
if (!hash.startsWith('ce-')) return;
const id = hash.slice(3);
const node = allNodes[id];
if (!node) return;
setActiveRoot(node.root);
setSelectedId(id);
setExpandedFolders(new Set(allFolderIds));
if (scroll && rootRef.current) rootRef.current.scrollIntoView({
behavior: 'smooth',
block: 'start'
});
};
applyHash(false);
const onHashChange = () => applyHash(true);
const onFsChange = () => setIsFullscreen(!!document.fullscreenElement);
window.addEventListener('hashchange', onHashChange);
document.addEventListener('fullscreenchange', onFsChange);
return () => {
if (copyTimeoutRef.current) clearTimeout(copyTimeoutRef.current);
window.removeEventListener('hashchange', onHashChange);
document.removeEventListener('fullscreenchange', onFsChange);
};
}, []);
useEffect(() => {
if (!mounted || !rootRef.current) return;
const hash = window.location.hash.slice(1);
if (hash.startsWith('ce-') && allNodes[hash.slice(3)]) {
rootRef.current.scrollIntoView({
behavior: 'smooth',
block: 'start'
});
}
}, [mounted]);
if (!mounted) return null;
const selected = allNodes[selectedId];
const tree = FILE_TREE[activeRoot];
const isCopied = copiedId === selected.id;
const toggleFolder = id => {
const next = new Set(expandedFolders);
next.has(id) ? next.delete(id) : next.add(id);
setExpandedFolders(next);
};
const switchRoot = root => {
if (root === activeRoot) return;
setActiveRoot(root);
const firstId = FILE_TREE[root].children[0].id;
setSelectedId(firstId);
try {
history.replaceState(null, '', '#ce-' + firstId);
} catch (e) {}
};
const toggleFullscreen = () => {
if (!rootRef.current) return;
if (document.fullscreenElement) document.exitFullscreen(); else rootRef.current.requestFullscreen().catch(() => {});
};
const selectNode = n => {
setSelectedId(n.id);
if (n.type === 'folder' && !expandedFolders.has(n.id)) toggleFolder(n.id);
try {
history.replaceState(null, '', '#ce-' + n.id);
} catch (e) {}
};
const iconBtn = {
width: 28,
flexShrink: 0,
borderRadius: '6px',
border: 'none',
cursor: 'pointer',
background: 'transparent',
color: 'var(--ce-text-4)',
display: 'flex',
alignItems: 'center',
justifyContent: 'center'
};
const visibleFolderIds = allFolderIds.filter(id => allNodes[id].root === activeRoot);
const allExpanded = visibleFolderIds.every(id => expandedFolders.has(id));
const toggleAllFolders = () => {
const next = new Set(expandedFolders);
visibleFolderIds.forEach(id => allExpanded ? next.delete(id) : next.add(id));
setExpandedFolders(next);
};
const onTreeKeyDown = e => {
if (!['ArrowDown', 'ArrowUp', 'ArrowRight', 'ArrowLeft'].includes(e.key)) return;
const visible = [];
const walk = nodes => {
for (const n of nodes) {
visible.push(n.id);
if (n.children && expandedFolders.has(n.id)) walk(n.children);
}
};
walk(tree.children);
const i = visible.indexOf(selectedId);
if (i === -1) return;
e.preventDefault();
if (e.key === 'ArrowDown' && i < visible.length - 1) selectNode(allNodes[visible[i + 1]]); else if (e.key === 'ArrowUp' && i > 0) selectNode(allNodes[visible[i - 1]]); else if (e.key === 'ArrowRight' && selected.type === 'folder') {
if (!expandedFolders.has(selectedId)) toggleFolder(selectedId); else if (selected.children && selected.children.length) selectNode(allNodes[selected.children[0].id]);
} else if (e.key === 'ArrowLeft') {
if (selected.type === 'folder' && expandedFolders.has(selectedId)) toggleFolder(selectedId); else if (selected.parentId) selectNode(allNodes[selected.parentId]);
}
};
const copyExample = (id, text) => {
const done = () => {
setCopiedId(id);
if (copyTimeoutRef.current) clearTimeout(copyTimeoutRef.current);
copyTimeoutRef.current = setTimeout(() => setCopiedId(null), 2000);
};
const fallback = () => {
const ta = document.createElement('textarea');
ta.value = text;
ta.style.position = 'fixed';
ta.style.opacity = '0';
document.body.appendChild(ta);
ta.select();
try {
if (document.execCommand('copy')) done();
} catch (e) {}
document.body.removeChild(ta);
};
if (navigator.clipboard) {
navigator.clipboard.writeText(text).then(done, fallback);
} else {
fallback();
}
};
const renderIcon = (icon, color, size) => {
const sz = size || 14;
if (icon === 'folder') {
return ;
}
if (icon === 'json') {
return ;
}
return ;
};
const renderNode = (node, depth) => {
const isFolder = node.type === 'folder';
const isExpanded = expandedFolders.has(node.id);
const isSelected = selectedId === node.id;
return