Claude Code Configurations

Claude Code is Anthropic's AI-powered coding assistant that extends Claude with tools for reading/writing files, running commands, and integrating with development workflows.

Key capabilities:

• File operations (read, write, edit)
• Code execution and shell commands
• Git integration
• Web search and fetching
• MCP (Model Context Protocol) server integration
• Extensible via slash commands and skills

• Tangling: Extract configurations to .claude/ directory using Org-mode's babel
• Documentation: Each config includes detailed explanations of what it does and why
• Modular: Separate files for different config types for easy navigation
• Team-Shareable: Project configs can be version-controlled and shared

Following the pattern established in the Emacs configurations, these Claude Code configs use literate programming:

1. Documentation comes first - explain the "why" before the "what"
2. Code blocks use :tangle directives to generate actual config files
3. Examples and best practices inline with implementation
4. Easy to understand, modify, and extend

Permissions, environment variables, model selection, hooks

Configure what tools Claude Code can use, set environment variables for your project, and control behavior through hooks.

Custom prompt templates for repeated workflows

User-invoked commands accessed by typing / in Claude Code. Includes commit message generation and org-roam capture integration.

Skills that Claude automatically activates based on context. Organized by domain:

External tool integrations via Model Context Protocol

Connect Claude Code to external services and tools. Configured for Emacs integration and project-scoped filesystem access.

Specialized agents for specific tasks (future)

Placeholder for upcoming custom subagent functionality. Will be updated when the feature becomes available.

1. Review configs: Read through the org files to understand what each config does
2. Customize paths: Edit MCP server paths in 04-mcp-servers.org if needed
3. Tangle configs: Run ./tangle-claude.sh from project root
4. Reload Claude Code: Restart or reload to pick up new configurations

From Emacs:

• Open any org file
• Run M-x org-babel-tangle or C-c C-v t

From command line:

emacs -Q --batch \
  --eval "(require 'org)" \
  --eval "(setq org-confirm-babel-evaluate nil)" \
  --eval "(find-file \"01-settings.org\")" \
  --eval "(org-babel-tangle)" \
  --kill

Use for configurations that should be shared with your team:

• Permission policies for the project
• MCP servers everyone uses
• Common slash commands (/review, /commit-msg)
• Team-wide skills
• Project-specific settings

Files: .claude/settings.json, .claude/commands/, .claude/skills/, .mcp.json

Use for personal preferences not in version control:

• Personal notification preferences
• Local development tools
• Experimental commands/skills
• API keys and credentials
• Personal MCP servers

Files: ~/.claude/settings.json, ~/.claude/commands/, ~/.claude/skills/

• Emacs Configurations - Similar literate config approach
• Neovim Configurations - Alternative editor setup
• Dotfiles - Other development tool configs

These org files are automatically processed by the site's build system:

• ./build.sh converts org files to HTML
• Generated files appear in public/agents/claude-code/
• Styling matches the rest of the site (GitHub Flavored Markdown theme)
• Floating table of contents for easy navigation

• Claude Code Documentation
• Model Context Protocol Specification
• Claude Code GitHub

• Claude Code Developer Cheatsheet
• MCP Server Directory

• CLAUDE.md - Instructions for Claude when working in this repo