The complete collection of Claude Code configs from an Anthropic hackathon winner.
This repo contains production-ready agents, skills, hooks, commands, rules, and MCP configurations that I use daily with Claude Code. These configs evolved over 10+ months of intensive use building real products.
Before diving into these configs, read the complete guide on X:
The Shorthand Guide to Everything Claude Code
The guide explains:
- What each config type does and when to use it
- How to structure your Claude Code setup
- Context window management (critical for performance)
- Parallel workflows and advanced techniques
- The philosophy behind these configs
This repo is configs only! Tips, tricks and more examples are in my X articles and videos (links will be appended to this readme as it evolves).
everything-claude-code/
|-- agents/ # Specialized subagents for delegation
| |-- planner.md # Feature implementation planning
| |-- architect.md # System design decisions
| |-- tdd-guide.md # Test-driven development
| |-- code-reviewer.md # Quality and security review
| |-- security-reviewer.md # Vulnerability analysis
| |-- build-error-resolver.md
| |-- e2e-runner.md # Playwright E2E testing
| |-- refactor-cleaner.md # Dead code cleanup
| |-- doc-updater.md # Documentation sync
|
|-- skills/ # Workflow definitions and domain knowledge
| |-- coding-standards.md # Language best practices
| |-- backend-patterns.md # API, database, caching patterns
| |-- frontend-patterns.md # React, Next.js patterns
| |-- project-guidelines-example.md # Example project-specific skill
| |-- tdd-workflow/ # TDD methodology
| |-- security-review/ # Security checklist
| |-- clickhouse-io.md # ClickHouse analytics
|
|-- commands/ # Slash commands for quick execution
| |-- tdd.md # /tdd - Test-driven development
| |-- plan.md # /plan - Implementation planning
| |-- e2e.md # /e2e - E2E test generation
| |-- code-review.md # /code-review - Quality review
| |-- build-fix.md # /build-fix - Fix build errors
| |-- refactor-clean.md # /refactor-clean - Dead code removal
| |-- test-coverage.md # /test-coverage - Coverage analysis
| |-- update-codemaps.md # /update-codemaps - Refresh docs
| |-- update-docs.md # /update-docs - Sync documentation
|
|-- rules/ # Always-follow guidelines
| |-- security.md # Mandatory security checks
| |-- coding-style.md # Immutability, file organization
| |-- testing.md # TDD, 80% coverage requirement
| |-- git-workflow.md # Commit format, PR process
| |-- agents.md # When to delegate to subagents
| |-- performance.md # Model selection, context management
| |-- patterns.md # API response formats, hooks
| |-- hooks.md # Hook documentation
|
|-- hooks/ # Trigger-based automations
| |-- hooks.json # PreToolUse, PostToolUse, Stop hooks
|
|-- mcp-configs/ # MCP server configurations
| |-- mcp-servers.json # GitHub, Supabase, Vercel, Railway, etc.
|
|-- plugins/ # Plugin ecosystem documentation
| |-- README.md # Plugins, marketplaces, skills guide
|
|-- examples/ # Example configurations
|-- CLAUDE.md # Example project-level config
|-- user-CLAUDE.md # Example user-level config (~/.claude/CLAUDE.md)
|-- statusline.json # Custom status line config
# Clone the repo
git clone https://github.com/affaan-m/everything-claude-code.git
# Copy agents to your Claude config
cp everything-claude-code/agents/*.md ~/.claude/agents/
# Copy rules
cp everything-claude-code/rules/*.md ~/.claude/rules/
# Copy commands
cp everything-claude-code/commands/*.md ~/.claude/commands/
# Copy skills
cp -r everything-claude-code/skills/* ~/.claude/skills/Copy the hooks from hooks/hooks.json to your ~/.claude/settings.json.
Copy desired MCP servers from mcp-configs/mcp-servers.json to your ~/.claude.json.
Important: Replace YOUR_*_HERE placeholders with your actual API keys.
Seriously, read the guide. These configs make 10x more sense with context.
Subagents handle delegated tasks with limited scope. Example:
---
name: code-reviewer
description: Reviews code for quality, security, and maintainability
tools: Read, Grep, Glob, Bash
model: opus
---
You are a senior code reviewer...Skills are workflow definitions invoked by commands or agents:
# TDD Workflow
1. Define interfaces first
2. Write failing tests (RED)
3. Implement minimal code (GREEN)
4. Refactor (IMPROVE)
5. Verify 80%+ coverageHooks fire on tool events. Example - warn about console.log:
{
"matcher": "tool == \"Edit\" && tool_input.file_path matches \"\\\\.(ts|tsx|js|jsx)$\"",
"hooks": [{
"type": "command",
"command": "#!/bin/bash\ngrep -n 'console\\.log' \"$file_path\" && echo '[Hook] Remove console.log' >&2"
}]
}Rules are always-follow guidelines. Keep them modular:
~/.claude/rules/
security.md # No hardcoded secrets
coding-style.md # Immutability, file limits
testing.md # TDD, coverage requirements
Contributions are welcome and encouraged.
This repo is meant to be a community resource. If you have:
- Useful agents or skills
- Clever hooks
- Better MCP configurations
- Improved rules
Please contribute! See CONTRIBUTING.md for guidelines.
- Language-specific skills (Python, Go, Rust patterns)
- Framework-specific configs (Django, Rails, Laravel)
- DevOps agents (Kubernetes, Terraform, AWS)
- Testing strategies (different frameworks)
- Domain-specific knowledge (ML, data engineering, mobile)
I've been using Claude Code since the experimental rollout. Won the Anthropic x Forum Ventures hackathon in Sep 2025 building zenith.chat with @DRodriguezFX - entirely using Claude Code.
These configs are battle-tested across multiple production applications.
Critical: Don't enable all MCPs at once. Your 200k context window can shrink to 70k with too many tools enabled.
Rule of thumb:
- Have 20-30 MCPs configured
- Keep under 10 enabled per project
- Under 80 tools active
Use disabledMcpServers in project config to disable unused ones.
These configs work for my workflow. You should:
- Start with what resonates
- Modify for your stack
- Remove what you don't use
- Add your own patterns
- Full Guide: The Shorthand Guide to Everything Claude Code
- Follow: @affaanmustafa
- zenith.chat: zenith.chat
MIT - Use freely, modify as needed, contribute back if you can.
Star this repo if it helps. Read the guide. Build something great.