Skip to main content

​
Quick Start

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

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
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)
2

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
Rules are always-follow guidelines that ensure consistent code quality, security, and best practices across your projects.
3

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
Plugin installs use the namespaced form (/everything-claude-code:plan) while manual installs use the shorter form (/plan).
4

Configure Package Manager (Optional)

The plugin automatically detects your preferred package manager (npm, pnpm, yarn, 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
  5. Global config: ~/.claude/package-manager.json
  6. Fallback: First available
To set your preferred package manager:
export CLAUDE_PACKAGE_MANAGER=pnpm

​
✨ 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

CommandWhat It DoesWhen to Use
/plan "feature"Creates implementation planStarting a new feature
/tddEnforces test-driven developmentWriting new code or fixing bugs
/code-reviewReviews code for quality & securityAfter writing/modifying code
/build-fixFixes build and type errorsWhen build fails
/e2eGenerates E2E testsTesting critical user flows
/orchestrateMulti-agent workflowComplex tasks requiring multiple agents

​
Example Workflow

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

Plan the Feature

/everything-claude-code:plan "Add OAuth authentication with Google and GitHub"
The planner agent creates a detailed implementation blueprint.
2

Implement with TDD

/everything-claude-code:tdd
The tdd-guide agent enforces write-tests-first workflow.
3

Review the Code

/everything-claude-code:code-review
The code-reviewer agent checks quality, security, and maintainability.
4

Fix Any Build Errors

/everything-claude-code:build-fix
The build-error-resolver agent fixes TypeScript errors and build issues.
5

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

Verify the plugin is enabled in ~/.claude/settings.json:
{
  "enabledPlugins": {
    "everything-claude-code@everything-claude-code": true
  }
}
Restart Claude Code after enabling the plugin.
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.
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.
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