If You Use Claude Code and Haven’t Configured…

By: Chorouk Maloum — Founder AgentX Academy | Follow for insights on AI & Business automation

🚨 If you use Claude Code and haven’t configured your .claude/ folder, you’re leaving 80% of its power on the table.

The .claude/ Folder Structure

The .claude/ folder is the control center for how Claude behaves in your project. It holds your instructions, your permissions, your custom workflows, and even Claude’s memory across sessions.

Key Files Explained

📌 CLAUDE.md → Team Instructions

• Most important file — Claude reads it at the start of every session
• Add coding conventions, architecture decisions, build commands
• Keep under 200 lines for best results

📌 CLAUDE.local.md → Personal Overrides

• Same as CLAUDE.md but gitignored
• Use for personal preferences without affecting team

📌 settings.json → Permissions + Config

• Controls what Claude can/can’t do
• Committed to git so whole team shares guardrails

📌 settings.local.json → Personal Permissions

• Local permission overrides
• Gitignored

📌 commands/ → Custom Slash Commands

• Each .md file becomes a slash command
• review.md → /project:review
• deploy.md → /project:deploy
• Reusable prompt templates for team

📌 rules/ → Modular Instruction Files

• Break long CLAUDE.md into focused modules
• code-style.md, testing.md, api-conventions.md
• Claude loads right rules based on files you’re working in

📌 skills/ → Auto-Invoked Workflows

• Unlike commands, skills trigger automatically
• Claude reads task and decides which skill to invoke
• Each skill = folder with SKILL.md + scripts

📌 agents/ → Subagent Personas

• Specialized personas in isolated contexts
• code-reviewer.md, security-auditor.md
• Each gets its own focus and instructions

One folder. Everything Claude needs to know about your project.

Source: LinkedIn Post

---

More from author: Join 30K builders for weekly AI agent briefings | Substack