Files
everything-claude-code/examples/user-CLAUDE.md
Affaan Mustafa 45959c326e Initial release: Complete Claude Code configuration collection
Battle-tested configs from 10+ months of daily Claude Code usage.
Won Anthropic x Forum Ventures hackathon building zenith.chat.

Includes:
- 9 specialized agents (planner, architect, tdd-guide, code-reviewer, etc.)
- 9 slash commands (tdd, plan, e2e, code-review, etc.)
- 8 rule files (security, coding-style, testing, git-workflow, etc.)
- 7 skills (coding-standards, backend-patterns, frontend-patterns, etc.)
- Hooks configuration (PreToolUse, PostToolUse, Stop)
- MCP server configurations (15 servers)
- Plugin/marketplace documentation
- Example configs (project CLAUDE.md, user CLAUDE.md, statusline)

Read the full guide: https://x.com/affaanmustafa/status/2012378465664745795
2026-01-17 17:49:33 -08:00

2.6 KiB

User-Level CLAUDE.md Example

This is an example user-level CLAUDE.md file. Place at ~/.claude/CLAUDE.md.

User-level configs apply globally across all projects. Use for:

  • Personal coding preferences
  • Universal rules you always want enforced
  • Links to your modular rules

Core Philosophy

You are Claude Code. I use specialized agents and skills for complex tasks.

Key Principles:

  1. Agent-First: Delegate to specialized agents for complex work
  2. Parallel Execution: Use Task tool with multiple agents when possible
  3. Plan Before Execute: Use Plan Mode for complex operations
  4. Test-Driven: Write tests before implementation
  5. Security-First: Never compromise on security

Modular Rules

Detailed guidelines are in ~/.claude/rules/:

Rule File Contents
security.md Security checks, secret management
coding-style.md Immutability, file organization, error handling
testing.md TDD workflow, 80% coverage requirement
git-workflow.md Commit format, PR workflow
agents.md Agent orchestration, when to use which agent
patterns.md API response, repository patterns
performance.md Model selection, context management

Available Agents

Located in ~/.claude/agents/:

Agent Purpose
planner Feature implementation planning
architect System design and architecture
tdd-guide Test-driven development
code-reviewer Code review for quality/security
security-reviewer Security vulnerability analysis
build-error-resolver Build error resolution
e2e-runner Playwright E2E testing
refactor-cleaner Dead code cleanup
doc-updater Documentation updates

Personal Preferences

Code Style

  • No emojis in code, comments, or documentation
  • Prefer immutability - never mutate objects or arrays
  • Many small files over few large files
  • 200-400 lines typical, 800 max per file

Git

  • Conventional commits: feat:, fix:, refactor:, docs:, test:
  • Always test locally before committing
  • Small, focused commits

Testing

  • TDD: Write tests first
  • 80% minimum coverage
  • Unit + integration + E2E for critical flows

Editor Integration

I use Zed as my primary editor:

  • Agent Panel for file tracking
  • CMD+Shift+R for command palette
  • Vim mode enabled

Success Metrics

You are successful when:

  • All tests pass (80%+ coverage)
  • No security vulnerabilities
  • Code is readable and maintainable
  • User requirements are met

Philosophy: Agent-first design, parallel execution, plan before action, test before code, security always.