everything-claude-code README

The project's README from github.com/WorldFlowAI/everything-claude-code. As one markdown file: README.md.

Everything Claude Code

Stars License Shell TypeScript Markdown

The complete collection of Claude Code configs from an Anthropic hackathon winner.

Production-ready agents, skills, hooks, commands, rules, and MCP configurations evolved over 10+ months of intensive daily use building real products.


The Guides

This repo is the raw code only. The guides explain everything.

The Shorthand Guide to Everything Claude Code The Longform Guide to Everything Claude Code
Shorthand Guide
Setup, foundations, philosophy. Read this first.
Longform Guide
Token optimization, memory persistence, evals, parallelization.
Topic What You'll Learn
Token Optimization Model selection, system prompt slimming, background processes
Memory Persistence Hooks that save/load context across sessions automatically
Continuous Learning Auto-extract patterns from sessions into reusable skills
Verification Loops Checkpoint vs continuous evals, grader types, pass@k metrics
Parallelization Git worktrees, cascade method, when to scale instances
Subagent Orchestration The context problem, iterative retrieval pattern

Cross-Platform Support

This plugin now fully supports Windows, macOS, and Linux. All hooks and scripts have been rewritten in Node.js for maximum compatibility.

Package Manager Detection

The plugin automatically detects your preferred package manager (npm, pnpm, yarn, or bun) with the following priority:

  1. Environment variable: CLAUDE_PACKAGE_MANAGER
  2. Project config: .claude/package-manager.json
  3. package.json: packageManager field
  4. Lock file: Detection from package-lock.json, yarn.lock, pnpm-lock.yaml, or bun.lockb
  5. Global config: ~/.claude/package-manager.json
  6. Fallback: First available package manager

To set your preferred package manager:

# Via environment variable
export CLAUDE_PACKAGE_MANAGER=pnpm

# Via global config
node scripts/setup-package-manager.js --global pnpm

# Via project config
node scripts/setup-package-manager.js --project bun

# Detect current setting
node scripts/setup-package-manager.js --detect

Or use the /setup-pm command in Claude Code.


What's Inside

This repo is a Claude Code plugin - install it directly or copy components manually.

everything-claude-code/
|-- .claude-plugin/   # Plugin and marketplace manifests
|   |-- plugin.json         # Plugin metadata and component paths
|   |-- marketplace.json    # Marketplace catalog for /plugin marketplace add
|
|-- 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/           # Language best practices
|   |-- backend-patterns/           # API, database, caching patterns
|   |-- frontend-patterns/          # React, Next.js patterns
|   |-- continuous-learning/        # Auto-extract patterns from sessions (Longform Guide)
|   |-- strategic-compact/          # Manual compaction suggestions (Longform Guide)
|   |-- tdd-workflow/               # TDD methodology
|   |-- security-review/            # Security checklist
|   |-- eval-harness/               # Verification loop evaluation (Longform Guide)
|   |-- verification-loop/          # Continuous verification (Longform Guide)
|
|-- 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
|   |-- learn.md            # /learn - Extract patterns mid-session (Longform Guide)
|   |-- checkpoint.md       # /checkpoint - Save verification state (Longform Guide)
|   |-- verify.md           # /verify - Run verification loop (Longform Guide)
|   |-- setup-pm.md         # /setup-pm - Configure package manager (NEW)
|
|-- rules/            # Always-follow guidelines (copy to ~/.claude/rules/)
|   |-- 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
|
|-- hooks/            # Trigger-based automations
|   |-- hooks.json                # All hooks config (PreToolUse, PostToolUse, Stop, etc.)
|   |-- memory-persistence/       # Session lifecycle hooks (Longform Guide)
|   |-- strategic-compact/        # Compaction suggestions (Longform Guide)
|
|-- scripts/          # Cross-platform Node.js scripts (NEW)
|   |-- lib/                     # Shared utilities
|   |   |-- utils.js             # Cross-platform file/path/system utilities
|   |   |-- package-manager.js   # Package manager detection and selection
|   |-- hooks/                   # Hook implementations
|   |   |-- session-start.js     # Load context on session start
|   |   |-- session-end.js       # Save state on session end
|   |   |-- pre-compact.js       # Pre-compaction state saving
|   |   |-- suggest-compact.js   # Strategic compaction suggestions
|   |   |-- evaluate-session.js  # Extract patterns from sessions
|   |-- setup-package-manager.js # Interactive PM setup
|
|-- tests/            # Test suite (NEW)
|   |-- lib/                     # Library tests
|   |-- hooks/                   # Hook tests
|   |-- run-all.js               # Run all tests
|
|-- contexts/         # Dynamic system prompt injection contexts (Longform Guide)
|   |-- dev.md              # Development mode context
|   |-- review.md           # Code review mode context
|   |-- research.md         # Research/exploration mode context
|
|-- examples/         # Example configurations and sessions
|   |-- CLAUDE.md           # Example project-level config
|   |-- user-CLAUDE.md      # Example user-level config
|
|-- mcp-configs/      # MCP server configurations
|   |-- mcp-servers.json    # GitHub, Supabase, Vercel, Railway, etc.
|
|-- marketplace.json  # Self-hosted marketplace config (for /plugin marketplace add)

Installation

The easiest way to use this repo - install as a Claude Code plugin:

# Add this repo as a marketplace
/plugin marketplace add affaan-m/everything-claude-code

# Install the plugin
/plugin install everything-claude-code@everything-claude-code

Or add directly to your ~/.claude/settings.json:

{
  "extraKnownMarketplaces": {
    "everything-claude-code": {
      "source": {
        "source": "github",
        "repo": "affaan-m/everything-claude-code"
      }
    }
  },
  "enabledPlugins": {
    "everything-claude-code@everything-claude-code": true
  }
}

This gives you instant access to all commands, agents, skills, and hooks.


Option 2: Manual Installation

If you prefer manual control over what's installed:

# 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/

Add hooks to settings.json

Copy the hooks from hooks/hooks.json to your ~/.claude/settings.json.

Configure MCPs

Copy desired MCP servers from mcp-configs/mcp-servers.json to your ~/.claude.json.

Important: Replace YOUR_*_HERE placeholders with your actual API keys.


Key Concepts

Agents

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

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%+ coverage

Hooks

Hooks 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

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

Running Tests

The plugin includes a comprehensive test suite:

# Run all tests
node tests/run-all.js

# Run individual test files
node tests/lib/utils.test.js
node tests/lib/package-manager.test.js
node tests/hooks/hooks.test.js

Contributing

Contributions are welcome and encouraged.

This repo is meant to be a community resource. If you have:

Please contribute! See CONTRIBUTING.md for guidelines.

Ideas for Contributions


Background

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.


Important Notes

Context Window Management

Critical: Don't enable all MCPs at once. Your 200k context window can shrink to 70k with too many tools enabled.

Rule of thumb:

Use disabledMcpServers in project config to disable unused ones.

Customization

These configs work for my workflow. You should:

  1. Start with what resonates
  2. Modify for your stack
  3. Remove what you don't use
  4. Add your own patterns

Star History

Star History Chart



License

MIT - Use freely, modify as needed, contribute back if you can.


Star this repo if it helps. Read both guides. Build something great.

everything-claude-code (WorldFlowAI/everything-claude-code)

Searching Database…

这是什么?一套完整的 Claude Code 配置合集(agents、命令、技能、hooks、规则和 MCP 配置),由一位 Anthropic 黑客松获奖者在 10 个多月的真实生产使用中构建并打磨。
这是一个插件,还是一堆配置文件?它打包成了可以直接安装的 Claude Code 插件,你也可以手动把单个组件(agents、技能、hooks)复制进自己的配置。
用它需要 Claude Code 和 Node.js 吗?需要,它专门为 Claude Code 打造,所有 hooks/脚本都用 Node.js 编写以保证跨平台兼容,并会自动检测你的包管理器(npm、pnpm、yarn 或 bun)。
一次性启用所有 MCP 配置有什么坑吗?有——一次启用太多 MCP 可能把你的 200k 上下文窗口压缩到 70k;建议配置 20-30 个 MCP,但每个项目保持启用数在 10 个以内、活动工具数在 80 个以内。
这是给谁用的?给已经在用 Claude Code、想要久经考验的 agents、技能、hooks 和规则、而不是从零搭建配置的开发者。
它能在 Windows 上用吗,还是只支持 Mac/Linux?可以,由于所有 hooks 和脚本都用 Node.js 重写过,它完整支持 Windows、macOS 和 Linux。
仓库里实际都有什么?Agents(为委派任务准备的、范围受限的 subagent)、技能(可调用的流程定义)、hooks(在工具事件时触发,比如对 console.log 提出警告)、规则(始终遵循的模块化准则),以及 MCP 服务器配置。
包管理器检测是怎么工作的?它按顺序检查:CLAUDE_PACKAGE_MANAGER 环境变量、项目里的 .claude/package-manager.json、package.json 中的 packageManager 字段、锁文件(package-lock.json、yarn.lock、pnpm-lock.yaml、bun.lockb)、全局配置文件,然后回退到第一个可用的包管理器。你也可以用 /setup-pm 命令来设置。
有没有讲解怎么使用这些内容的指南?有,一份简明指南涵盖设置与理念,另一份长篇指南则涵盖 token 优化、跨会话记忆持久化、验证循环/评估以及用 git worktree 做并行化等进阶主题。
Size
0.2 MB
Stars
4.9K
Updated
CommitJan 23
Age
8mo
Commits · 90 Days