everything

name	everything
aliases	["everything-claude-code","ecc","omo"]
description	Universal skill for Everything Claude Code - provides access to all commands, agents, skills, rules, and workflows in the OMO ecosystem. Single entry point for all functionality.

Everything Claude Code - Universal Skill

This skill provides access to the complete Everything Claude Code ecosystem (OhMyOpenCode/OMO). Use this as your single entry point for all commands, agents, skills, rules, and workflows.

Quick Reference

What You Want	Command
Plan a feature	/plan <description>
Write code with tests	/tdd <description>
Review code	/code-review
Fix build errors	/build-fix
Run E2E tests	/e2e <journey>
Clean dead code	/refactor-clean
Extract patterns	/learn
Verify state	`/verify [quick
Create checkpoint	/checkpoint create <name>
Run evals	`/eval [define
Orchestrate workflow	`/orchestrate [feature

Available Commands

/plan - Implementation Planning

Create step-by-step implementation plan before writing code.

When to use: New features, significant architecture changes, complex refactoring

Invokes: planner agent

Workflow:

1. Analyze requirements
2. Break into phases
3. Identify risks
4. Wait for confirmation

Example:

/plan Add real-time notifications when markets resolve

---

/tdd - Test-Driven Development

Write tests first, then implement to pass, then refactor.

When to use: New features, bug fixes, adding functions/components

Invokes: tdd-guide agent, uses tdd-workflow skill

Workflow: RED → GREEN → REFACTOR

1. Write failing tests (RED)
2. Implement minimal code (GREEN)
3. Refactor while tests pass (REFACTOR)
4. Verify 80%+ coverage

Example:

/tdd Create function to calculate market liquidity score

---

/code-review - Quality Review

Review uncommitted changes for security and quality issues.

When to use: Before commits, before PRs, after writing code

Invokes: code-reviewer agent

Checks:

• CRITICAL: Secrets, SQL injection, XSS, auth issues
• HIGH: Code quality (>50 line functions, >800 line files)
• MEDIUM: Best practices, tests, accessibility

Example:

/code-review

---

/build-fix - Fix Build Errors

Incrementally fix TypeScript and build errors.

When to use: Build fails, type errors, compilation issues

Invokes: build-error-resolver agent

Process:

1. Run build and parse errors
2. Fix one error at a time
3. Verify after each fix
4. Stop if fix introduces new errors

Example:

/build-fix

---

/e2e - End-to-End Testing

Generate and run Playwright E2E tests for user journeys.

When to use: Critical user flows, UI interactions, pre-deployment

Invokes: e2e-runner agent

Output:

• Generated Playwright tests
• Screenshots/videos/traces
• HTML report
• Flaky test detection

Example:

/e2e Test the market search and view flow

---

/refactor-clean - Dead Code Removal

Safely identify and remove unused code with test verification.

When to use: Code maintenance, reducing tech debt

Invokes: refactor-cleaner agent

Tools: knip, depcheck, ts-prune

Process:

1. Run analysis tools
2. Categorize by severity (SAFE/CAUTION/DANGER)
3. Run tests before each deletion
4. Rollback if tests fail

Example:

/refactor-clean

---

/learn - Pattern Extraction

Extract reusable patterns from current session.

When to use: After solving non-trivial problems

Process:

1. Review session for patterns
2. Identify valuable insights
3. Create skill file
4. Save to ~/.claude/skills/learned/

Extracts: Error resolutions, debugging techniques, workarounds

Example:

/learn

---

/verify - State Verification

Run comprehensive verification on codebase.

When to use: Before commits, before PRs, health checks

Modes:

• quick - Build + types only
• full (default) - All checks
• pre-commit - Commit-relevant checks
• pre-pr - Full + security scan

Checks: Build, Types, Lint, Tests, Secrets, console.logs

Example:

/verify full

---

/checkpoint - Save/Verify State

Create or verify checkpoints in your workflow.

When to use: Milestones, before risky changes

Args:

• create <name> - Create checkpoint
• verify <name> - Compare to checkpoint
• list - Show all checkpoints

Example:

/checkpoint create feature-start

---

/eval - Eval-Driven Development

Manage eval definitions and verification.

When to use: Feature validation, regression testing

Args:

• define <name> - Create eval definition
• check <name> - Run evals
• report <name> - Generate report
• list - Show all evals

Example:

/eval define user-authentication

---

/orchestrate - Agent Workflows

Run sequential agent workflows for complex tasks.

When to use: Complex features, multi-step processes

Workflows:

• feature - planner → tdd-guide → code-reviewer → security-reviewer
• bugfix - explorer → tdd-guide → code-reviewer
• refactor - architect → code-reviewer → tdd-guide
• security - security-reviewer → code-reviewer → architect

Example:

/orchestrate feature Add user authentication

---

/test-coverage - Coverage Check

Run tests and verify coverage meets thresholds.

Example:

/test-coverage

---

/update-codemaps - Update Code Maps

Update codebase structure documentation.

Example:

/update-codemaps

---

/update-docs - Update Documentation

Sync documentation with code changes.

Invokes: doc-updater agent

Example:

/update-docs

Available Agents

Agent	Purpose	Command
planner	Implementation planning	/plan
tdd-guide	Test-driven development	/tdd
code-reviewer	Quality review	/code-review
security-reviewer	Security audit	via /orchestrate security
build-error-resolver	Fix build errors	/build-fix
e2e-runner	E2E testing	/e2e
refactor-cleaner	Dead code cleanup	/refactor-clean
architect	System design	via /orchestrate
doc-updater	Documentation sync	/update-docs

Available Skills

Skill	Purpose
tdd-workflow	TDD methodology and patterns
security-review	Security checklist and patterns
coding-standards	Language best practices
frontend-patterns	React/Next.js patterns
backend-patterns	API/database patterns
verification-loop	Continuous verification
eval-harness	Evaluation framework
continuous-learning	Pattern extraction
strategic-compact	Context management
postgres-patterns	PostgreSQL best practices
clickhouse-io	ClickHouse analytics
golang-patterns	Go best practices
golang-testing	Go testing patterns

Rules (Always Active)

Located in ~/.claude/rules/:

Rule	Purpose
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
performance.md	Model selection, context management
hooks.md	Hook system guidelines
patterns.md	Common patterns and conventions

Hooks System

Hooks in ~/.claude/settings.json fire on:

Hook Type	When	Purpose
PreToolUse	Before tool execution	Validation, parameter modification
PostToolUse	After tool execution	Auto-format, checks
PreCompact	Before context compaction	State saving
SessionStart	When session starts	Context loading
Stop	When session ends	Final verification

Current Hooks

PreToolUse:

• Block dev servers outside tmux
• Reminder for long-running commands
• Pause before git push
• Block unnecessary .md file creation
• Suggest context compaction

PostToolUse:

• Log PR URL after creation
• Auto-format JS/TS with Prettier
• Run TypeScript check
• Warn about console.log

Stop:

• Check for console.log before session end

Usage Patterns

Feature Development Workflow

1. /plan Add user authentication
2. /tdd Implement auth service
3. /code-review
4. /verify pre-pr
5. git commit and push

Bug Fix Workflow

1. /orchestrate bugfix "Fix login redirect issue"
2. /verify quick
3. git commit

Refactoring Workflow

1. /checkpoint create "before-refactor"
2. /orchestrate refactor "Simplify data layer"
3. /checkpoint verify "before-refactor"
4. /refactor-clean

Pre-Deployment Workflow

1. /verify full
2. /e2e Test critical user flows
3. /code-review
4. Deploy

Installation

As Plugin (Recommended)

/plugin marketplace add affaan-m/everything-claude-code
/plugin install everything-claude-code@everything-claude-code

Manual Installation

cp -r skills/everything ~/.claude/skills/
cp commands/*.md ~/.claude/commands/
cp agents/*.md ~/.claude/agents/
cp rules/*.md ~/.claude/rules/

Key Principles

1. TDD First - Always write tests before code
2. 80% Coverage - Minimum test coverage requirement
3. Small Files - 200-400 lines typical, 800 max
4. Immutability - Never mutate objects or arrays
5. Security - No hardcoded secrets, validate all inputs
6. Parallel Execution - Use agents in parallel when possible
7. Continuous Verification - Run /verify before commits

---

Best Practices Archive

Cloud Drive (网盘系统) - 完整实现案例

日期: 2025-01-31
规模: 35+ 文件, 4000+ 行代码, 85%+ 测试覆盖
技术栈: Next.js 14 + TypeScript + Prisma + NextAuth

核心功能

• 用户认证系统 (JWT)
• 文件分片上传 (1MB chunks, 断点续传)
• 文件下载 (流式传输)
• 文件夹管理 (无限层级)
• 存储配额管理 (10GB)
• 软删除机制

相关文档

• EXAMPLES.md - 项目概述和核心代码
• TEMPLATES.md - 可复用的配置文件模板
• WORKFLOW.md - Everything Skill 开发流程指南
• README.md - 完整使用文档

项目位置

D:\everything-claude-code\cloud-drive

快速复用

# 复制模板
cp -r cloud-drive/ my-new-project/
cd my-new-project

# 修改配置
# - package.json
# - .env.local
# - prisma/schema.prisma

# 启动
npm install
npx prisma migrate dev
npm run dev

---

Why This Is A Best Practice

1. Complete Feature Set

• Full authentication system
• Chunked file upload with resume
• Folder management with nesting
• Storage quota enforcement
• Soft delete for safety

2. Code Quality

• TDD development (test first)
• 80%+ test coverage
• TypeScript strict mode
• Small files (200-400 lines)
• Clear architecture layers

3. Security

• bcrypt password hashing
• JWT token authentication
• Zod input validation
• SQL injection protection
• XSS prevention

4. Everything Skill Integration

• /plan - Detailed project planning
• /tdd - Test-driven development
• /code-review - Quality checks
• /verify - Continuous validation
• /e2e - End-to-end testing

---

Using Everything Skill for New Projects

Step 1: Plan

/plan Build a [feature] with [requirements]

Step 2: TDD

/tdd Implement [feature] with tests

Step 3: Review

/code-review

Step 4: Verify

/verify full

Step 5: E2E

/e2e Test [critical workflow]

---

Archive Files

File	Purpose
SKILL.md	This file - complete reference
README.md	User guide and quick start
EXAMPLES.md	Best practice examples
TEMPLATES.md	Reusable code templates
WORKFLOW.md	Development workflow guide

---

Everything Skill - Best practices from real-world projects