The claude.md file & .claude folder

Learn how Claude Code organizes its configuration files and folders, both at the project level and at the system level. This lesson walks through the .claude folder structure, what each piece is for, and how project-level and system-level settings relate to each other.

Starting with the /init command to generate a claude.md file for an existing codebase, you'll see how the .claude folder houses your settings.json, custom commands, skills, and subagent configurations. Understanding the difference between project-level and system-level folders is key — anything placed in your home directory's .claude folder becomes available across all your projects.

• Using the /init command to generate a claude.md orientation file for your project
• The .claude folder structure: where settings, commands, skills, and agents live
• What settings.json is for: hooks, MCP servers, granular permissions, and other configuration
• The commands, skills, and agents subfolders and what each one holds
• Project-level vs. system-level .claude folders and how they differ
• System-level commands, skills, and agents are available across all your projects
• How to view hidden files and folders (Command+Shift+Period on Mac)