- validate-agents.js: reject invalid model names in agent frontmatter - package-manager.js: validate script/binary names against shell injection - session-manager.js: reject impossible month/day values in filenames - utils.js: support options.all for replaceInFile string patterns - strategic-compact/SKILL.md: fix hook matcher syntax and script reference - install.sh: warn when overwriting existing rule customizations - Add 24 new tests covering all validation and edge cases
Language: English | 繁體中文
Everything Claude Code
42K+ stars | 5K+ forks | 24 contributors | 6 languages supported | Anthropic Hackathon Winner
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.
|
|
|
| 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 |
What's New
v1.4.1 — Bug Fix (Feb 2026)
- Fixed instinct import content loss —
parse_instinct_file()was silently dropping all content after frontmatter (Action, Evidence, Examples sections) during/instinct-import. Fixed by community contributor @ericcai0814 (#148, #161)
v1.4.0 — Multi-Language Rules, Installation Wizard & PM2 (Feb 2026)
- Interactive installation wizard — New
configure-eccskill provides guided setup with merge/overwrite detection - PM2 & multi-agent orchestration — 6 new commands (
/pm2,/multi-plan,/multi-execute,/multi-backend,/multi-frontend,/multi-workflow) for managing complex multi-service workflows - Multi-language rules architecture — Rules restructured from flat files into
common/+typescript/+python/+golang/directories. Install only the languages you need - Chinese (zh-CN) translations — Complete translation of all agents, commands, skills, and rules (80+ files)
- GitHub Sponsors support — Sponsor the project via GitHub Sponsors
- Enhanced CONTRIBUTING.md — Detailed PR templates for each contribution type
v1.3.0 — OpenCode Plugin Support (Feb 2026)
- Full OpenCode integration — 12 agents, 24 commands, 16 skills with hook support via OpenCode's plugin system (20+ event types)
- 3 native custom tools — run-tests, check-coverage, security-audit
- LLM documentation —
llms.txtfor comprehensive OpenCode docs
v1.2.0 — Unified Commands & Skills (Feb 2026)
- Python/Django support — Django patterns, security, TDD, and verification skills
- Java Spring Boot skills — Patterns, security, TDD, and verification for Spring Boot
- Session management —
/sessionscommand for session history - Continuous learning v2 — Instinct-based learning with confidence scoring, import/export, evolution
See the full changelog in Releases.
🚀 Quick Start
Get up and running in under 2 minutes:
Step 1: Install the Plugin
# Add marketplace
/plugin marketplace add affaan-m/everything-claude-code
# Install plugin
/plugin install everything-claude-code@everything-claude-code
Step 2: Install Rules (Required)
⚠️ Important: Claude Code plugins cannot distribute
rulesautomatically. Install them manually:
# Clone the repo first
git clone https://github.com/affaan-m/everything-claude-code.git
cd everything-claude-code
# Recommended: use the installer (handles common + language rules safely)
./install.sh typescript # or python or golang
# You can pass multiple languages:
# ./install.sh typescript python golang
# or target cursor:
# ./install.sh --target cursor typescript
For manual install instructions see the README in the rules/ folder.
Step 3: Start Using
# Try a command
/plan "Add user authentication"
# Check available commands
/plugin list everything-claude-code@everything-claude-code
✨ That's it! You now have access to 13 agents, 37 skills, and 31 commands.
🌐 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:
- Environment variable:
CLAUDE_PACKAGE_MANAGER - Project config:
.claude/package-manager.json - package.json:
packageManagerfield - Lock file: Detection from package-lock.json, yarn.lock, pnpm-lock.yaml, or bun.lockb
- Global config:
~/.claude/package-manager.json - 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
| |-- go-reviewer.md # Go code review
| |-- go-build-resolver.md # Go build error resolution
| |-- python-reviewer.md # Python code review (NEW)
| |-- database-reviewer.md # Database/Supabase review (NEW)
|
|-- skills/ # Workflow definitions and domain knowledge
| |-- coding-standards/ # Language best practices
| |-- clickhouse-io/ # ClickHouse analytics, queries, data engineering
| |-- backend-patterns/ # API, database, caching patterns
| |-- frontend-patterns/ # React, Next.js patterns
| |-- continuous-learning/ # Auto-extract patterns from sessions (Longform Guide)
| |-- continuous-learning-v2/ # Instinct-based learning with confidence scoring
| |-- iterative-retrieval/ # Progressive context refinement for subagents
| |-- 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)
| |-- golang-patterns/ # Go idioms and best practices
| |-- golang-testing/ # Go testing patterns, TDD, benchmarks
| |-- cpp-testing/ # C++ testing with GoogleTest, CMake/CTest (NEW)
| |-- django-patterns/ # Django patterns, models, views (NEW)
| |-- django-security/ # Django security best practices (NEW)
| |-- django-tdd/ # Django TDD workflow (NEW)
| |-- django-verification/ # Django verification loops (NEW)
| |-- python-patterns/ # Python idioms and best practices (NEW)
| |-- python-testing/ # Python testing with pytest (NEW)
| |-- springboot-patterns/ # Java Spring Boot patterns (NEW)
| |-- springboot-security/ # Spring Boot security (NEW)
| |-- springboot-tdd/ # Spring Boot TDD (NEW)
| |-- springboot-verification/ # Spring Boot verification (NEW)
| |-- configure-ecc/ # Interactive installation wizard (NEW)
| |-- security-scan/ # AgentShield security auditor integration (NEW)
| |-- java-coding-standards/ # Java coding standards (NEW)
| |-- jpa-patterns/ # JPA/Hibernate patterns (NEW)
| |-- postgres-patterns/ # PostgreSQL optimization patterns (NEW)
| |-- nutrient-document-processing/ # Document processing with Nutrient API (NEW)
| |-- project-guidelines-example/ # Template for project-specific skills
| |-- database-migrations/ # Migration patterns (Prisma, Drizzle, Django, Go) (NEW)
| |-- api-design/ # REST API design, pagination, error responses (NEW)
| |-- deployment-patterns/ # CI/CD, Docker, health checks, rollbacks (NEW)
| |-- docker-patterns/ # Docker Compose, networking, volumes, container security (NEW)
| |-- e2e-testing/ # Playwright E2E patterns and Page Object Model (NEW)
|
|-- 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
| |-- go-review.md # /go-review - Go code review (NEW)
| |-- go-test.md # /go-test - Go TDD workflow (NEW)
| |-- go-build.md # /go-build - Fix Go build errors (NEW)
| |-- skill-create.md # /skill-create - Generate skills from git history (NEW)
| |-- instinct-status.md # /instinct-status - View learned instincts (NEW)
| |-- instinct-import.md # /instinct-import - Import instincts (NEW)
| |-- instinct-export.md # /instinct-export - Export instincts (NEW)
| |-- evolve.md # /evolve - Cluster instincts into skills
| |-- pm2.md # /pm2 - PM2 service lifecycle management (NEW)
| |-- multi-plan.md # /multi-plan - Multi-agent task decomposition (NEW)
| |-- multi-execute.md # /multi-execute - Orchestrated multi-agent workflows (NEW)
| |-- multi-backend.md # /multi-backend - Backend multi-service orchestration (NEW)
| |-- multi-frontend.md # /multi-frontend - Frontend multi-service orchestration (NEW)
| |-- multi-workflow.md # /multi-workflow - General multi-service workflows (NEW)
| |-- orchestrate.md # /orchestrate - Multi-agent coordination
| |-- sessions.md # /sessions - Session history management
| |-- eval.md # /eval - Evaluate against criteria
| |-- test-coverage.md # /test-coverage - Test coverage analysis
| |-- update-docs.md # /update-docs - Update documentation
| |-- update-codemaps.md # /update-codemaps - Update codemaps
| |-- python-review.md # /python-review - Python code review (NEW)
|
|-- rules/ # Always-follow guidelines (copy to ~/.claude/rules/)
| |-- README.md # Structure overview and installation guide
| |-- common/ # Language-agnostic principles
| | |-- coding-style.md # Immutability, file organization
| | |-- git-workflow.md # Commit format, PR process
| | |-- testing.md # TDD, 80% coverage requirement
| | |-- performance.md # Model selection, context management
| | |-- patterns.md # Design patterns, skeleton projects
| | |-- hooks.md # Hook architecture, TodoWrite
| | |-- agents.md # When to delegate to subagents
| | |-- security.md # Mandatory security checks
| |-- typescript/ # TypeScript/JavaScript specific
| |-- python/ # Python specific
| |-- golang/ # Go specific
|
|-- hooks/ # Trigger-based automations
| |-- README.md # Hook documentation, recipes, and customization guide
| |-- 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
| |-- saas-nextjs-CLAUDE.md # Real-world SaaS (Next.js + Supabase + Stripe)
| |-- go-microservice-CLAUDE.md # Real-world Go microservice (gRPC + PostgreSQL)
| |-- django-api-CLAUDE.md # Real-world Django REST API (DRF + Celery)
| |-- rust-api-CLAUDE.md # Real-world Rust API (Axum + SQLx + PostgreSQL) (NEW)
|
|-- mcp-configs/ # MCP server configurations
| |-- mcp-servers.json # GitHub, Supabase, Vercel, Railway, etc.
|
|-- marketplace.json # Self-hosted marketplace config (for /plugin marketplace add)
🛠️ Ecosystem Tools
Skill Creator
Two ways to generate Claude Code skills from your repository:
Option A: Local Analysis (Built-in)
Use the /skill-create command for local analysis without external services:
/skill-create # Analyze current repo
/skill-create --instincts # Also generate instincts for continuous-learning
This analyzes your git history locally and generates SKILL.md files.
Option B: GitHub App (Advanced)
For advanced features (10k+ commits, auto-PRs, team sharing):
Install GitHub App | ecc.tools
# Comment on any issue:
/skill-creator analyze
# Or auto-triggers on push to default branch
Both options create:
- SKILL.md files - Ready-to-use skills for Claude Code
- Instinct collections - For continuous-learning-v2
- Pattern extraction - Learns from your commit history
AgentShield — Security Auditor
Built at the Claude Code Hackathon (Cerebral Valley x Anthropic, Feb 2026). 876 tests, 98% coverage, 96 static analysis rules.
Scan your Claude Code configuration for vulnerabilities, misconfigurations, and injection risks.
# Quick scan (no install needed)
npx ecc-agentshield scan
# Auto-fix safe issues
npx ecc-agentshield scan --fix
# Deep analysis with three Opus 4.6 agents
npx ecc-agentshield scan --opus --stream
# Generate secure config from scratch
npx ecc-agentshield init
What it scans: CLAUDE.md, settings.json, MCP configs, hooks, agent definitions, and skills across 5 categories — secrets detection (14 patterns), permission auditing, hook injection analysis, MCP server risk profiling, and agent config review.
The --opus flag runs three Claude Opus 4.6 agents in a red-team/blue-team/auditor pipeline. The attacker finds exploit chains, the defender evaluates protections, and the auditor synthesizes both into a prioritized risk assessment. Adversarial reasoning, not just pattern matching.
Output formats: Terminal (color-graded A-F), JSON (CI pipelines), Markdown, HTML. Exit code 2 on critical findings for build gates.
Use /security-scan in Claude Code to run it, or add to CI with the GitHub Action.
🧠 Continuous Learning v2
The instinct-based learning system automatically learns your patterns:
/instinct-status # Show learned instincts with confidence
/instinct-import <file> # Import instincts from others
/instinct-export # Export your instincts for sharing
/evolve # Cluster related instincts into skills
See skills/continuous-learning-v2/ for full documentation.
📋 Requirements
Claude Code CLI Version
Minimum version: v2.1.0 or later
This plugin requires Claude Code CLI v2.1.0+ due to changes in how the plugin system handles hooks.
Check your version:
claude --version
Important: Hooks Auto-Loading Behavior
⚠️ For Contributors: Do NOT add a
"hooks"field to.claude-plugin/plugin.json. This is enforced by a regression test.
Claude Code v2.1+ automatically loads hooks/hooks.json from any installed plugin by convention. Explicitly declaring it in plugin.json causes a duplicate detection error:
Duplicate hooks file detected: ./hooks/hooks.json resolves to already-loaded file
History: This has caused repeated fix/revert cycles in this repo (#29, #52, #103). The behavior changed between Claude Code versions, leading to confusion. We now have a regression test to prevent this from being reintroduced.
📥 Installation
Option 1: Install as Plugin (Recommended)
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.
Note: The Claude Code plugin system does not support distributing
rulesvia plugins (upstream limitation). You need to install rules manually:# Clone the repo first git clone https://github.com/affaan-m/everything-claude-code.git # Option A: User-level rules (applies to all projects) cp -r everything-claude-code/rules/common/* ~/.claude/rules/ cp -r everything-claude-code/rules/typescript/* ~/.claude/rules/ # pick your stack cp -r everything-claude-code/rules/python/* ~/.claude/rules/ cp -r everything-claude-code/rules/golang/* ~/.claude/rules/ # Option B: Project-level rules (applies to current project only) mkdir -p .claude/rules cp -r everything-claude-code/rules/common/* .claude/rules/ cp -r everything-claude-code/rules/typescript/* .claude/rules/ # pick your stack
🔧 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 (common + language-specific)
cp -r everything-claude-code/rules/common/* ~/.claude/rules/
cp -r everything-claude-code/rules/typescript/* ~/.claude/rules/ # pick your stack
cp -r everything-claude-code/rules/python/* ~/.claude/rules/
cp -r everything-claude-code/rules/golang/* ~/.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, organized into common/ (language-agnostic) + language-specific directories:
rules/
common/ # Universal principles (always install)
typescript/ # TS/JS specific patterns and tools
python/ # Python specific patterns and tools
golang/ # Go specific patterns and tools
See rules/README.md for installation and structure details.
🗺️ Which Agent Should I Use?
Not sure where to start? Use this quick reference:
| I want to... | Use this command | Agent used |
|---|---|---|
| Plan a new feature | /plan "Add auth" |
planner |
| Design system architecture | /plan + architect agent |
architect |
| Write code with tests first | /tdd |
tdd-guide |
| Review code I just wrote | /code-review |
code-reviewer |
| Fix a failing build | /build-fix |
build-error-resolver |
| Run end-to-end tests | /e2e |
e2e-runner |
| Find security vulnerabilities | /security-scan |
security-reviewer |
| Remove dead code | /refactor-clean |
refactor-cleaner |
| Update documentation | /update-docs |
doc-updater |
| Review Go code | /go-review |
go-reviewer |
| Review Python code | /python-review |
python-reviewer |
| Audit database queries | (auto-delegated) | database-reviewer |
Common Workflows
Starting a new feature:
/plan "Add user authentication with OAuth" → planner creates implementation blueprint
/tdd → tdd-guide enforces write-tests-first
/code-review → code-reviewer checks your work
Fixing a bug:
/tdd → tdd-guide: write a failing test that reproduces it
→ implement the fix, verify test passes
/code-review → code-reviewer: catch regressions
Preparing for production:
/security-scan → security-reviewer: OWASP Top 10 audit
/e2e → e2e-runner: critical user flow tests
/test-coverage → verify 80%+ coverage
❓ FAQ
How do I check which agents/commands are installed?
/plugin list everything-claude-code@everything-claude-code
This shows all available agents, commands, and skills from the plugin.
My hooks aren't working / I see "Duplicate hooks file" errors
This is the most common issue. 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 #29, #52, #103.
My context window is shrinking / Claude is 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 your project's .claude/settings.json
{
"disabledMcpServers": ["supabase", "railway", "vercel"]
}
Keep under 10 MCPs enabled and under 80 tools active.
Can I use only some components (e.g., just agents)?
Yes. Use Option 2 (manual installation) and copy only what you need:
# Just agents
cp everything-claude-code/agents/*.md ~/.claude/agents/
# Just rules
cp -r everything-claude-code/rules/common/* ~/.claude/rules/
Each component is fully independent.
Does this work with Cursor / OpenCode?
Yes. ECC is cross-platform:
- Cursor: Pre-translated configs in
.cursor/. See Cursor IDE Support. - OpenCode: Full plugin support in
.opencode/. See OpenCode Support. - Claude Code: Native — this is the primary target.
How do I contribute a new skill or agent?
See CONTRIBUTING.md. The short version:
- Fork the repo
- Create your skill in
skills/your-skill-name/SKILL.md(with YAML frontmatter) - Or create an agent in
agents/your-agent.md - Submit a PR with a clear description of what it does and when to use it
🧪 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:
- Useful agents or skills
- Clever hooks
- Better MCP configurations
- Improved rules
Please contribute! See CONTRIBUTING.md for guidelines.
Ideas for Contributions
- Language-specific skills (Rust, C#, Swift, Kotlin) — Go, Python, Java already included
- Framework-specific configs (Rails, Laravel, FastAPI, NestJS) — Django, Spring Boot already included
- DevOps agents (Kubernetes, Terraform, AWS, Docker)
- Testing strategies (different frameworks, visual regression)
- Domain-specific knowledge (ML, data engineering, mobile)
Cursor IDE Support
ecc-universal includes pre-translated configurations for Cursor IDE. The .cursor/ directory contains rules, agents, skills, commands, and MCP configs adapted for Cursor's format.
Quick Start (Cursor)
# Install the package
npm install ecc-universal
# Install for your language(s)
./install.sh --target cursor typescript
./install.sh --target cursor python golang
What's Translated
| Component | Claude Code → Cursor | Parity |
|---|---|---|
| Rules | YAML frontmatter added, paths flattened | Full |
| Agents | Model IDs expanded, tools → readonly flag | Full |
| Skills | No changes needed (identical standard) | Identical |
| Commands | Path references updated, multi-* stubbed | Partial |
| MCP Config | Env interpolation syntax updated | Full |
| Hooks | No equivalent in Cursor | See alternatives |
See .cursor/README.md for details and .cursor/MIGRATION.md for the full migration guide.
🔌 OpenCode Support
ECC provides full OpenCode support including plugins and hooks.
Quick Start
# Install OpenCode
npm install -g opencode
# Run in the repository root
opencode
The configuration is automatically detected from .opencode/opencode.json.
Feature Parity
| Feature | Claude Code | OpenCode | Status |
|---|---|---|---|
| Agents | ✅ 13 agents | ✅ 12 agents | Claude Code leads |
| Commands | ✅ 31 commands | ✅ 24 commands | Claude Code leads |
| Skills | ✅ 37 skills | ✅ 16 skills | Claude Code leads |
| Hooks | ✅ 3 phases | ✅ 20+ events | OpenCode has more! |
| Rules | ✅ 8 rules | ✅ 8 rules | Full parity |
| MCP Servers | ✅ Full | ✅ Full | Full parity |
| Custom Tools | ✅ Via hooks | ✅ Native support | OpenCode is better |
Hook Support via Plugins
OpenCode's plugin system is MORE sophisticated than Claude Code with 20+ event types:
| Claude Code Hook | OpenCode Plugin Event |
|---|---|
| PreToolUse | tool.execute.before |
| PostToolUse | tool.execute.after |
| Stop | session.idle |
| SessionStart | session.created |
| SessionEnd | session.deleted |
Additional OpenCode events: file.edited, file.watcher.updated, message.updated, lsp.client.diagnostics, tui.toast.show, and more.
Available Commands (31)
| Command | Description |
|---|---|
/plan |
Create implementation plan |
/tdd |
Enforce TDD workflow |
/code-review |
Review code changes |
/build-fix |
Fix build errors |
/e2e |
Generate E2E tests |
/refactor-clean |
Remove dead code |
/orchestrate |
Multi-agent workflow |
/learn |
Extract patterns from session |
/checkpoint |
Save verification state |
/verify |
Run verification loop |
/eval |
Evaluate against criteria |
/update-docs |
Update documentation |
/update-codemaps |
Update codemaps |
/test-coverage |
Analyze coverage |
/go-review |
Go code review |
/go-test |
Go TDD workflow |
/go-build |
Fix Go build errors |
/python-review |
Python code review (PEP 8, type hints, security) |
/multi-plan |
Multi-model collaborative planning |
/multi-execute |
Multi-model collaborative execution |
/multi-backend |
Backend-focused multi-model workflow |
/multi-frontend |
Frontend-focused multi-model workflow |
/multi-workflow |
Full multi-model development workflow |
/pm2 |
Auto-generate PM2 service commands |
/sessions |
Manage session history |
/skill-create |
Generate skills from git |
/instinct-status |
View learned instincts |
/instinct-import |
Import instincts |
/instinct-export |
Export instincts |
/evolve |
Cluster instincts into skills |
/setup-pm |
Configure package manager |
Plugin Installation
Option 1: Use directly
cd everything-claude-code
opencode
Option 2: Install as npm package
npm install ecc-universal
Then add to your opencode.json:
{
"plugin": ["ecc-universal"]
}
Documentation
- Migration Guide:
.opencode/MIGRATION.md - OpenCode Plugin README:
.opencode/README.md - Consolidated Rules:
.opencode/instructions/INSTRUCTIONS.md - LLM Documentation:
llms.txt(complete OpenCode docs for LLMs)
📖 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.
Token Optimization
Claude Code usage can be expensive if you don't manage token consumption. These settings significantly reduce costs without sacrificing quality.
Recommended Settings
Add to ~/.claude/settings.json:
{
"model": "sonnet",
"env": {
"MAX_THINKING_TOKENS": "10000",
"CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "50"
}
}
| Setting | Default | Recommended | Impact |
|---|---|---|---|
model |
opus | sonnet | ~60% cost reduction; handles 80%+ of coding tasks |
MAX_THINKING_TOKENS |
31,999 | 10,000 | ~70% reduction in hidden thinking cost per request |
CLAUDE_AUTOCOMPACT_PCT_OVERRIDE |
95 | 50 | Compacts earlier — better quality in long sessions |
Switch to Opus only when you need deep architectural reasoning:
/model opus
Daily Workflow Commands
| Command | When to Use |
|---|---|
/model sonnet |
Default for most tasks |
/model opus |
Complex architecture, debugging, deep reasoning |
/clear |
Between unrelated tasks (free, instant reset) |
/compact |
At logical task breakpoints (research done, milestone complete) |
/cost |
Monitor token spending during session |
Strategic Compaction
The strategic-compact skill (included in this plugin) suggests /compact at logical breakpoints instead of relying on auto-compaction at 95% context. See skills/strategic-compact/SKILL.md for the full decision guide.
When to compact:
- After research/exploration, before implementation
- After completing a milestone, before starting the next
- After debugging, before continuing feature work
- After a failed approach, before trying a new one
When NOT to compact:
- Mid-implementation (you'll lose variable names, file paths, partial state)
Context Window Management
Critical: Don't enable all MCPs at once. Each MCP tool description consumes tokens from your 200k window, potentially reducing it to ~70k.
- Keep under 10 MCPs enabled per project
- Keep under 80 tools active
- Use
disabledMcpServersin project config to disable unused ones
Agent Teams Cost Warning
Agent Teams spawns multiple context windows. Each teammate consumes tokens independently. Only use for tasks where parallelism provides clear value (multi-module work, parallel reviews). For simple sequential tasks, subagents are more token-efficient.
⚠️ Important Notes
Token Optimization
Hitting daily limits? See the Token Optimization Guide for recommended settings and workflow tips.
Quick wins:
// ~/.claude/settings.json
{
"model": "sonnet",
"env": {
"MAX_THINKING_TOKENS": "10000",
"CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "50",
"CLAUDE_CODE_SUBAGENT_MODEL": "haiku"
}
}
Use /clear between unrelated tasks, /compact at logical breakpoints, and /cost to monitor spending.
Customization
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
💜 Sponsors
This project is free and open source. Sponsors help keep it maintained and growing.
Become a Sponsor | Sponsor Tiers
🌟 Star History
🔗 Links
- Shorthand Guide (Start Here): The Shorthand Guide to Everything Claude Code
- Longform Guide (Advanced): The Longform Guide to Everything Claude Code
- Follow: @affaanmustafa
- zenith.chat: zenith.chat
- Skills Directory: awesome-agent-skills
📄 License
MIT - Use freely, modify as needed, contribute back if you can.
Star this repo if it helps. Read both guides. Build something great.