Quick Start

Get Everything Claude Code installed and ready to use in under 2 minutes.

Install the Plugin

The easiest way to use Everything Claude Code is to install it as a Claude Code plugin.

# Add marketplace
/plugin marketplace add affaan-m/everything-claude-code

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

{
  "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:

13 specialized agents (planner, architect, tdd-guide, code-reviewer, etc.)
33 slash commands (/plan, /tdd, /code-review, /build-fix, etc.)
56+ skills (coding standards, TDD workflow, security review, etc.)
Automated hooks (memory persistence, strategic compaction, security warnings)

Install Rules (Required)

Claude Code plugins cannot distribute rules automatically (upstream limitation). You need to install rules manually.

Clone the repository first:

git clone https://github.com/affaan-m/everything-claude-code.git
cd everything-claude-code

Automated (Recommended)
Manual

Use the installer script to handle common + language rules safely:

./install.sh typescript

./install.sh python

./install.sh golang

./install.sh typescript python golang

./install.sh --target cursor typescript

The installer copies rules to ~/.claude/rules/ maintaining the directory structure:

common/ - Language-agnostic principles (always installed)
typescript/, python/, golang/, etc. - Language-specific rules

For manual installation, copy rules maintaining the directory structure:

# Common rules (always install)
mkdir -p ~/.claude/rules
cp -r rules/common/* ~/.claude/rules/

# Language-specific rules (pick your stack)
cp -r rules/typescript/* ~/.claude/rules/
cp -r rules/python/* ~/.claude/rules/
cp -r rules/golang/* ~/.claude/rules/

# Common rules (always install)
mkdir -p .claude/rules
cp -r rules/common/* .claude/rules/

# Language-specific rules (pick your stack)
cp -r rules/typescript/* .claude/rules/

Rules are always-follow guidelines that ensure consistent code quality, security, and best practices across your projects.

Start Using Commands

Try your first command to verify installation:

# Plan a new feature
/everything-claude-code:plan "Add user authentication"

# Run TDD workflow
/everything-claude-code:tdd

# Review code changes
/everything-claude-code:code-review

# Check available commands
/plugin list everything-claude-code@everything-claude-code

# Plan a new feature
/plan "Add user authentication"

# Run TDD workflow
/tdd

# Review code changes
/code-review

Plugin installs use the namespaced form (/everything-claude-code:plan) while manual installs use the shorter form (/plan).

Configure Package Manager (Optional)

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

Environment variable: CLAUDE_PACKAGE_MANAGER
Project config: .claude/package-manager.json
package.json: packageManager field
Lock file detection
Global config: ~/.claude/package-manager.json
Fallback: First available

To set your preferred package manager:

export CLAUDE_PACKAGE_MANAGER=pnpm

node scripts/setup-package-manager.js --global pnpm

node scripts/setup-package-manager.js --project bun

node scripts/setup-package-manager.js --detect

/setup-pm

✨ That’s It!

You now have access to:

13 specialized agents for planning, architecture, TDD, code review, security, and more
56+ skills covering coding standards, backend/frontend patterns, security, testing, and continuous learning
33 commands for instant execution of common workflows
Automated hooks for memory persistence, strategic compaction, and security warnings

First Steps

Try a Command

Start with /plan "Add user authentication" to see the planner agent in action.

Review Available Commands

Use /plugin list everything-claude-code@everything-claude-code to see all available commands.

Learn About Agents

Check out the Agents Concept to understand when to use each agent.

Optimize Token Usage

Review Token Optimization to reduce costs without sacrificing quality.

Common First Commands

Command	What It Does	When to Use
`/plan "feature"`	Creates implementation plan	Starting a new feature
`/tdd`	Enforces test-driven development	Writing new code or fixing bugs
`/code-review`	Reviews code for quality & security	After writing/modifying code
`/build-fix`	Fixes build and type errors	When build fails
`/e2e`	Generates E2E tests	Testing critical user flows
`/orchestrate`	Multi-agent workflow	Complex tasks requiring multiple agents

Example Workflow

Here’s a typical workflow for adding a new feature:

Plan the Feature

/everything-claude-code:plan "Add OAuth authentication with Google and GitHub"

The planner agent creates a detailed implementation blueprint.

Implement with TDD

/everything-claude-code:tdd

The tdd-guide agent enforces write-tests-first workflow.

Review the Code

/everything-claude-code:code-review

The code-reviewer agent checks quality, security, and maintainability.

Fix Any Build Errors

/everything-claude-code:build-fix

The build-error-resolver agent fixes TypeScript errors and build issues.

Add E2E Tests

/everything-claude-code:e2e

The e2e-runner agent generates Playwright tests for critical flows.

Next Steps

Installation Guide

Detailed installation options and platform-specific notes

Key Concepts

Learn about agents, skills, hooks, and rules

Token Optimization

Reduce costs without sacrificing quality

Troubleshooting

Commands not found / plugin not loading

Verify the plugin is enabled in ~/.claude/settings.json:

{
  "enabledPlugins": {
    "everything-claude-code@everything-claude-code": true
  }
}

Restart Claude Code after enabling the plugin.

Hooks aren't working / 'Duplicate hooks file' errors

Do NOT add a "hooks" field to .claude-plugin/plugin.json.Claude Code v2.1+ automatically loads hooks/hooks.json from installed plugins. Explicitly declaring it causes duplicate detection errors.See issues #29, #52, #103.

Context window shrinking / running out of context

Too many MCP servers eat your context. Each MCP tool description consumes tokens from your 200k window, potentially reducing it to ~70k.Fix: Disable unused MCPs per project in .claude/settings.json:

{
  "disabledMcpServers": ["supabase", "railway", "vercel"]
}

Keep under 10 MCPs enabled and under 80 tools active.

Rules not being followed

Verify rules are installed in the correct location:

# Check user-level rules
ls -la ~/.claude/rules/

# Check project-level rules
ls -la .claude/rules/

Rules should maintain the directory structure:

common/ - Language-agnostic principles
typescript/, python/, golang/, etc. - Language-specific rules

Getting Help

GitHub Issues

Report bugs or request features

Shorthand Guide

Setup, foundations, and philosophy

Longform Guide

Token optimization, memory persistence, evals, parallelization

Follow @affaanmustafa

Get updates and tips

Get Started

Core Concepts

Platform Support

Guides

Quick Start

Quick Start

✨ That’s It!

First Steps

Try a Command

Review Available Commands

Learn About Agents

Optimize Token Usage

Common First Commands

Example Workflow

Next Steps

Installation Guide

Key Concepts

Token Optimization

Troubleshooting

Getting Help

GitHub Issues

Shorthand Guide

Longform Guide

Follow @affaanmustafa

​Quick Start

​✨ That’s It!

​First Steps

Try a Command

Review Available Commands

Learn About Agents

Optimize Token Usage

​Common First Commands

​Example Workflow

​Next Steps

Installation Guide

Key Concepts

Token Optimization

​Troubleshooting

​Getting Help

GitHub Issues

Shorthand Guide

Longform Guide

Follow @affaanmustafa

Quick Start

✨ That’s It!

First Steps

Common First Commands

Example Workflow

Next Steps

Troubleshooting

Getting Help