config-settingslisted

# Configuration and Settings Management ## Purpose Configure Claude Code's behavior, permissions, and memory across the settings hierarchy. Understand which settings file to edit, how permissions evaluate, and how to manage the context window effectively through CLAUDE.md, skills, and context strategies. ## When to Use - Setting up a new project's .claude/settings.json and CLAUDE.md - Configuring permission rules (allow, deny, ask) for tools - Creating settings.local.json for personal overrides - Writing or improving a CLAUDE.md file - Managing context window size and preventing context rot - Understanding why a permission rule is not behaving as expected ## Examples **Example 1: Setting up project permissions** ``` User: "Configure Claude Code to auto-approve reads but ask before running npm install" Claude: [Uses config-settings] Creates .claude/settings.json: { "permissions": { "allow": ["Read", "Glob", "Grep", "Bash(git status)", "Bash(git log *)"], "ask": ["Bash(npm install *)", "Bash(git push *)"], "deny": ["Read(./.env*)", "Bash(rm -rf *)"] } } Explains: Deny is checked first (blocks .env reads), then Ask (prompts for npm install), then Allow (auto-approves reads). ``` **Example 2: Writing a CLAUDE.md** ``` User: "Create a CLAUDE.md for this Next.js project" Claude: [Uses config-settings] Generates a concise CLAUDE.md (~50 lines): - Stack overview (Next.js 14, TypeScript, Tailwind, Supabase) - Core commands (dev, test, lint, build) - Coding stand