docs: salvage remaining stable zh-CN skill translations

Port the current-source-safe command documentation subset from stale PR #1687.\n\nEach copied command page maps to an English source file unchanged since the stale PR base; fastapi-review remains deferred because #1687 did not include a matching zh-CN translation.

.agents/skills/claude-api/SKILL.md

@@ -1,336 +0,0 @@
----
-name: claude-api
-description: Anthropic Claude API patterns for Python and TypeScript. Covers Messages API, streaming, tool use, vision, extended thinking, batches, prompt caching, and Claude Agent SDK. Use when building applications with the Claude API or Anthropic SDKs.
----
-
-# Claude API
-
-Build applications with the Anthropic Claude API and SDKs.
-
-## When to Activate
-
-- Building applications that call the Claude API
-- Code imports `anthropic` (Python) or `@anthropic-ai/sdk` (TypeScript)
-- User asks about Claude API patterns, tool use, streaming, or vision
-- Implementing agent workflows with Claude Agent SDK
-- Optimizing API costs, token usage, or latency
-
-## Model Selection
-
-| Model | ID | Best For |
-|-------|-----|----------|
-| Opus 4.6 | `claude-opus-4-6` | Complex reasoning, architecture, research |
-| Sonnet 4.6 | `claude-sonnet-4-6` | Balanced coding, most development tasks |
-| Haiku 4.5 | `claude-haiku-4-5-20251001` | Fast responses, high-volume, cost-sensitive |
-
-Default to Sonnet 4.6 unless the task requires deep reasoning (Opus) or speed/cost optimization (Haiku).
-
-## Python SDK
-
-### Installation
-
-```bash
-pip install anthropic
-```
-
-### Basic Message
-
-```python
-import anthropic
-
-client = anthropic.Anthropic()  # reads ANTHROPIC_API_KEY from env
-
-message = client.messages.create(
-    model="claude-sonnet-4-6",
-    max_tokens=1024,
-    messages=[
-        {"role": "user", "content": "Explain async/await in Python"}
-    ]
-)
-print(message.content[0].text)
-```
-
-### Streaming
-
-```python
-with client.messages.stream(
-    model="claude-sonnet-4-6",
-    max_tokens=1024,
-    messages=[{"role": "user", "content": "Write a haiku about coding"}]
-) as stream:
-    for text in stream.text_stream:
-        print(text, end="", flush=True)
-```
-
-### System Prompt
-
-```python
-message = client.messages.create(
-    model="claude-sonnet-4-6",
-    max_tokens=1024,
-    system="You are a senior Python developer. Be concise.",
-    messages=[{"role": "user", "content": "Review this function"}]
-)
-```
-
-## TypeScript SDK
-
-### Installation
-
-```bash
-npm install @anthropic-ai/sdk
-```
-
-### Basic Message
-
-```typescript
-import Anthropic from "@anthropic-ai/sdk";
-
-const client = new Anthropic(); // reads ANTHROPIC_API_KEY from env
-
-const message = await client.messages.create({
-  model: "claude-sonnet-4-6",
-  max_tokens: 1024,
-  messages: [
-    { role: "user", content: "Explain async/await in TypeScript" }
-  ],
-});
-console.log(message.content[0].text);
-```
-
-### Streaming
-
-```typescript
-const stream = client.messages.stream({
-  model: "claude-sonnet-4-6",
-  max_tokens: 1024,
-  messages: [{ role: "user", content: "Write a haiku" }],
-});
-
-for await (const event of stream) {
-  if (event.type === "content_block_delta" && event.delta.type === "text_delta") {
-    process.stdout.write(event.delta.text);
-  }
-}
-```
-
-## Tool Use
-
-Define tools and let Claude call them:
-
-```python
-tools = [
-    {
-        "name": "get_weather",
-        "description": "Get current weather for a location",
-        "input_schema": {
-            "type": "object",
-            "properties": {
-                "location": {"type": "string", "description": "City name"},
-                "unit": {"type": "string", "enum": ["celsius", "fahrenheit"]}
-            },
-            "required": ["location"]
-        }
-    }
-]
-
-message = client.messages.create(
-    model="claude-sonnet-4-6",
-    max_tokens=1024,
-    tools=tools,
-    messages=[{"role": "user", "content": "What's the weather in SF?"}]
-)
-
-# Handle tool use response
-for block in message.content:
-    if block.type == "tool_use":
-        # Execute the tool with block.input
-        result = get_weather(**block.input)
-        # Send result back
-        follow_up = client.messages.create(
-            model="claude-sonnet-4-6",
-            max_tokens=1024,
-            tools=tools,
-            messages=[
-                {"role": "user", "content": "What's the weather in SF?"},
-                {"role": "assistant", "content": message.content},
-                {"role": "user", "content": [
-                    {"type": "tool_result", "tool_use_id": block.id, "content": str(result)}
-                ]}
-            ]
-        )
-```
-
-## Vision
-
-Send images for analysis:
-
-```python
-import base64
-
-with open("diagram.png", "rb") as f:
-    image_data = base64.standard_b64encode(f.read()).decode("utf-8")
-
-message = client.messages.create(
-    model="claude-sonnet-4-6",
-    max_tokens=1024,
-    messages=[{
-        "role": "user",
-        "content": [
-            {"type": "image", "source": {"type": "base64", "media_type": "image/png", "data": image_data}},
-            {"type": "text", "text": "Describe this diagram"}
-        ]
-    }]
-)
-```
-
-## Extended Thinking
-
-For complex reasoning tasks:
-
-```python
-message = client.messages.create(
-    model="claude-sonnet-4-6",
-    max_tokens=16000,
-    thinking={
-        "type": "enabled",
-        "budget_tokens": 10000
-    },
-    messages=[{"role": "user", "content": "Solve this math problem step by step..."}]
-)
-
-for block in message.content:
-    if block.type == "thinking":
-        print(f"Thinking: {block.thinking}")
-    elif block.type == "text":
-        print(f"Answer: {block.text}")
-```
-
-## Prompt Caching
-
-Cache large system prompts or context to reduce costs:
-
-```python
-message = client.messages.create(
-    model="claude-sonnet-4-6",
-    max_tokens=1024,
-    system=[
-        {"type": "text", "text": large_system_prompt, "cache_control": {"type": "ephemeral"}}
-    ],
-    messages=[{"role": "user", "content": "Question about the cached context"}]
-)
-# Check cache usage
-print(f"Cache read: {message.usage.cache_read_input_tokens}")
-print(f"Cache creation: {message.usage.cache_creation_input_tokens}")
-```
-
-## Batches API
-
-Process large volumes asynchronously at 50% cost reduction:
-
-```python
-import time
-
-batch = client.messages.batches.create(
-    requests=[
-        {
-            "custom_id": f"request-{i}",
-            "params": {
-                "model": "claude-sonnet-4-6",
-                "max_tokens": 1024,
-                "messages": [{"role": "user", "content": prompt}]
-            }
-        }
-        for i, prompt in enumerate(prompts)
-    ]
-)
-
-# Poll for completion
-while True:
-    status = client.messages.batches.retrieve(batch.id)
-    if status.processing_status == "ended":
-        break
-    time.sleep(30)
-
-# Get results
-for result in client.messages.batches.results(batch.id):
-    print(result.result.message.content[0].text)
-```
-
-## Claude Agent SDK
-
-Build multi-step agents:
-
-```python
-# Note: Agent SDK API surface may change — check official docs
-import anthropic
-
-# Define tools as functions
-tools = [{
-    "name": "search_codebase",
-    "description": "Search the codebase for relevant code",
-    "input_schema": {
-        "type": "object",
-        "properties": {"query": {"type": "string"}},
-        "required": ["query"]
-    }
-}]
-
-# Run an agentic loop with tool use
-client = anthropic.Anthropic()
-messages = [{"role": "user", "content": "Review the auth module for security issues"}]
-
-while True:
-    response = client.messages.create(
-        model="claude-sonnet-4-6",
-        max_tokens=4096,
-        tools=tools,
-        messages=messages,
-    )
-    if response.stop_reason == "end_turn":
-        break
-    # Handle tool calls and continue the loop
-    messages.append({"role": "assistant", "content": response.content})
-    # ... execute tools and append tool_result messages
-```
-
-## Cost Optimization
-
-| Strategy | Savings | When to Use |
-|----------|---------|-------------|
-| Prompt caching | Up to 90% on cached tokens | Repeated system prompts or context |
-| Batches API | 50% | Non-time-sensitive bulk processing |
-| Haiku instead of Sonnet | ~75% | Simple tasks, classification, extraction |
-| Shorter max_tokens | Variable | When you know output will be short |
-| Streaming | None (same cost) | Better UX, same price |
-
-## Error Handling
-
-```python
-import time
-
-from anthropic import APIError, RateLimitError, APIConnectionError
-
-try:
-    message = client.messages.create(...)
-except RateLimitError:
-    # Back off and retry
-    time.sleep(60)
-except APIConnectionError:
-    # Network issue, retry with backoff
-    pass
-except APIError as e:
-    print(f"API error {e.status_code}: {e.message}")
-```
-
-## Environment Setup
-
-```bash
-# Required
-export ANTHROPIC_API_KEY="your-api-key-here"
-
-# Optional: set default model
-export ANTHROPIC_MODEL="claude-sonnet-4-6"
-```
-
-Never hardcode API keys. Always use environment variables.

.agents/skills/claude-api/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Claude API"
-  short_description: "Claude API patterns for Python and TypeScript"
-  brand_color: "#D97706"
-  default_prompt: "Use $claude-api to build with Claude API and Anthropic SDK patterns."
-policy:
-  allow_implicit_invocation: true

.agents/skills/frontend-design/SKILL.md

@@ -1,144 +0,0 @@
----
-name: frontend-design
-description: Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build web components, pages, or applications and the visual direction matters as much as the code quality.
----
-
-# Frontend Design
-
-Use this when the task is not just "make it work" but "make it look designed."
-
-This skill is for product pages, dashboards, app shells, components, or visual systems that need a clear point of view instead of generic AI-looking UI.
-
-## When To Use
-
-- building a landing page, dashboard, or app surface from scratch
-- upgrading a bland interface into something intentional and memorable
-- translating a product concept into a concrete visual direction
-- implementing a frontend where typography, composition, and motion matter
-
-## Core Principle
-
-Pick a direction and commit to it.
-
-Safe-average UI is usually worse than a strong, coherent aesthetic with a few bold choices.
-
-## Design Workflow
-
-### 1. Frame the interface first
-
-Before coding, settle:
-
-- purpose
-- audience
-- emotional tone
-- visual direction
-- one thing the user should remember
-
-Possible directions:
-
-- brutally minimal
-- editorial
-- industrial
-- luxury
-- playful
-- geometric
-- retro-futurist
-- soft and organic
-- maximalist
-
-Do not mix directions casually. Choose one and execute it cleanly.
-
-### 2. Build the visual system
-
-Define:
-
-- type hierarchy
-- color variables
-- spacing rhythm
-- layout logic
-- motion rules
-- surface / border / shadow treatment
-
-Use CSS variables or the project's token system so the interface stays coherent as it grows.
-
-### 3. Compose with intention
-
-Prefer:
-
-- asymmetry when it sharpens hierarchy
-- overlap when it creates depth
-- strong whitespace when it clarifies focus
-- dense layouts only when the product benefits from density
-
-Avoid defaulting to a symmetrical card grid unless it is clearly the right fit.
-
-### 4. Make motion meaningful
-
-Use animation to:
-
-- reveal hierarchy
-- stage information
-- reinforce user action
-- create one or two memorable moments
-
-Do not scatter generic micro-interactions everywhere. One well-directed load sequence is usually stronger than twenty random hover effects.
-
-## Strong Defaults
-
-### Typography
-
-- pick fonts with character
-- pair a distinctive display face with a readable body face when appropriate
-- avoid generic defaults when the page is design-led
-
-### Color
-
-- commit to a clear palette
-- one dominant field with selective accents usually works better than evenly weighted rainbow palettes
-- avoid cliché purple-gradient-on-white unless the product genuinely calls for it
-
-### Background
-
-Use atmosphere:
-
-- gradients
-- meshes
-- textures
-- subtle noise
-- patterns
-- layered transparency
-
-Flat empty backgrounds are rarely the best answer for a product-facing page.
-
-### Layout
-
-- break the grid when the composition benefits from it
-- use diagonals, offsets, and grouping intentionally
-- keep reading flow obvious even when the layout is unconventional
-
-## Anti-Patterns
-
-Never default to:
-
-- interchangeable SaaS hero sections
-- generic card piles with no hierarchy
-- random accent colors without a system
-- placeholder-feeling typography
-- motion that exists only because animation was easy to add
-
-## Execution Rules
-
-- preserve the established design system when working inside an existing product
-- match technical complexity to the visual idea
-- keep accessibility and responsiveness intact
-- frontends should feel deliberate on desktop and mobile
-
-## Quality Gate
-
-Before delivering:
-
-- the interface has a clear visual point of view
-- typography and spacing feel intentional
-- color and motion support the product instead of decorating it randomly
-- the result does not read like generic AI UI
-- the implementation is production-grade, not just visually interesting

.agents/skills/frontend-design/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Frontend Design"
-  short_description: "Production-grade frontend interface design"
-  brand_color: "#0EA5E9"
-  default_prompt: "Use $frontend-design to build a distinctive production-grade interface."
-policy:
-  allow_implicit_invocation: true

.agents/skills/frontend-patterns/SKILL.md

@@ -17,6 +17,12 @@ Modern frontend patterns for React, Next.js, and performant user interfaces.
 - Handling client-side routing and navigation
 - Building accessible, responsive UI patterns
 
+## Privacy and Data Boundaries
+
+Frontend examples should use synthetic or domain-generic data. Do not collect, log, persist, or display credentials, access tokens, SSNs, health data, payment details, private emails, phone numbers, or other sensitive personal data unless the user explicitly requests a scoped implementation with appropriate validation, redaction, and access controls.
+
+Avoid adding analytics, tracking pixels, third-party scripts, or external data sinks without explicit approval. When handling user data, prefer least-privilege APIs, client-side redaction before logging, and server-side validation for every boundary.
+
 ## Component Patterns
 
 ### Composition Over Inheritance

.claude-plugin/PLUGIN_SCHEMA_NOTES.md

@@ -132,6 +132,27 @@ The test `plugin.json does NOT have explicit hooks declaration` in `tests/hooks/
 
 ---
 
+## The `mcpServers` Field: Keep the Empty Opt-Out
+
+ECC keeps `.mcp.json` at the repository root for Codex plugin installs and manual MCP setup.
+Claude Code also auto-discovers plugin-root `.mcp.json` files by convention, which would bundle the same MCP servers into Claude plugin installs.
+The Claude plugin slug is intentionally short (`ecc`), but this opt-out is still required because legacy installs and strict provider gateways have failed on generated names from longer plugin identifiers.
+
+Keep this field in `.claude-plugin/plugin.json`:
+
+```json
+{
+  "mcpServers": {}
+}
+```
+
+This explicit empty object prevents Claude plugin installs from auto-loading ECC's root MCP definitions.
+Without the opt-out, strict OpenAI-compatible gateways can reject plugin MCP tool names such as `mcp__plugin_everything-claude-code_github__create_pull_request_review` because they exceed 64 characters.
+
+Users who want the bundled MCP servers should configure them manually from `.mcp.json` or `mcp-configs/mcp-servers.json`.
+
+---
+
 ## Known Anti-Patterns
 
 These look correct but are rejected:
@@ -142,6 +163,7 @@ These look correct but are rejected:
 * Relying on inferred paths
 * Assuming marketplace behavior matches local validation
 * **Adding `"hooks": "./hooks/hooks.json"`** - auto-loaded by convention, causes duplicate error
+* Removing `"mcpServers": {}` - re-enables root `.mcp.json` auto-discovery for Claude plugin installs and can produce overlong MCP tool names
 
 Avoid cleverness. Be explicit.
 
@@ -170,7 +192,8 @@ Before submitting changes that touch `plugin.json`:
 1. Ensure all component fields are arrays
 2. Include a `version`
 3. Do NOT add `agents` or `hooks` fields (both are auto-loaded by convention)
-4. Run:
+4. Preserve `"mcpServers": {}` unless you are intentionally changing Claude plugin MCP bundling behavior
+5. Run:
 
 ```bash
 claude plugin validate .claude-plugin/plugin.json

.claude-plugin/marketplace.json

@@ -1,5 +1,5 @@
 {
-  "name": "everything-claude-code",
+  "name": "ecc",
   "owner": {
     "name": "Affaan Mustafa",
     "email": "me@affaanmustafa.com"
@@ -9,9 +9,9 @@
   },
   "plugins": [
     {
-      "name": "everything-claude-code",
+      "name": "ecc",
       "source": "./",
-      "description": "The most comprehensive Claude Code plugin — 48 agents, 184 skills, 79 legacy command shims, selective install profiles, and production-ready hooks for TDD, security scanning, code review, and continuous learning",
+      "description": "The most comprehensive Claude Code plugin — 53 agents, 203 skills, 69 legacy command shims, selective install profiles, and production-ready hooks for TDD, security scanning, code review, and continuous learning",
       "version": "2.0.0-rc.1",
       "author": {
         "name": "Affaan Mustafa",

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
-  "name": "everything-claude-code",
+  "name": "ecc",
   "version": "2.0.0-rc.1",
-  "description": "Battle-tested Claude Code plugin for engineering teams — 48 agents, 184 skills, 79 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use",
+  "description": "Battle-tested Claude Code plugin for engineering teams — 53 agents, 203 skills, 69 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use",
   "author": {
     "name": "Affaan Mustafa",
     "url": "https://x.com/affaanmustafa"
@@ -22,6 +22,11 @@
     "automation",
     "best-practices"
   ],
-  "skills": ["./skills/"],
-  "commands": ["./commands/"]
+  "mcpServers": {},
+  "skills": [
+    "./skills/"
+  ],
+  "commands": [
+    "./commands/"
+  ]
 }

.codex-plugin/README.md

@@ -12,7 +12,7 @@ This directory contains the **Codex plugin manifest** for Everything Claude Code
 
 ## What This Provides
 
-- **156 skills** from `./skills/` — reusable Codex workflows for TDD, security,
+- **200 skills** from `./skills/` — reusable Codex workflows for TDD, security,
   code review, architecture, and more
 - **6 MCP servers** — GitHub, Context7, Exa, Memory, Playwright, Sequential Thinking
 

.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "ecc",
   "version": "2.0.0-rc.1",
-  "description": "Battle-tested Codex workflows — 156 shared ECC skills, production-ready MCP configs, and selective-install-aligned conventions for TDD, security scanning, code review, and autonomous development.",
+  "description": "Battle-tested Codex workflows — 200 shared ECC skills, production-ready MCP configs, and selective-install-aligned conventions for TDD, security scanning, code review, and autonomous development.",
   "author": {
     "name": "Affaan Mustafa",
     "email": "me@affaanmustafa.com",
@@ -15,7 +15,7 @@
   "mcpServers": "./.mcp.json",
   "interface": {
     "displayName": "Everything Claude Code",
-    "shortDescription": "156 battle-tested ECC skills plus MCP configs for TDD, security, code review, and autonomous development.",
+    "shortDescription": "200 battle-tested ECC skills plus MCP configs for TDD, security, code review, and autonomous development.",
     "longDescription": "Everything Claude Code (ECC) is a community-maintained collection of Codex-ready skills and MCP configs evolved over 10+ months of intensive daily use. It covers TDD workflows, security scanning, code review, architecture decisions, operator workflows, and more — all in one installable plugin.",
     "developerName": "Affaan Mustafa",
     "category": "Productivity",

.codex/AGENTS.md

@@ -60,6 +60,12 @@ The sync script (`scripts/sync-ecc-to-codex.sh`) uses a Node-based TOML parser t
 - **`--update-mcp`** — explicitly replaces all ECC-managed servers with the latest recommended config (safely removes subtables like `[mcp_servers.supabase.env]`).
 - **User config is always preserved** — custom servers, args, env vars, and credentials outside ECC-managed sections are never touched.
 
+## External Action Boundaries
+
+Treat networked tools as read-only by default. Search, inspect, and draft freely within the user's requested scope, but require explicit user approval before posting, publishing, pushing, merging, opening paid jobs, dispatching remote agents, changing third-party resources, or modifying credentials.
+
+When approval is ambiguous, produce a local plan or draft artifact instead of taking the external action. Preserve user config and private state unless the user specifically asks for a scoped change.
+
 ## Multi-Agent Support
 
 Codex now supports multi-agent workflows behind the experimental `features.multi_agent` flag.

.github/workflows/ci.yml

@@ -45,7 +45,7 @@ jobs:
       # Package manager setup
       - name: Setup pnpm
         if: matrix.pm == 'pnpm' && matrix.node != '18.x'
-        uses: pnpm/action-setup@08c4be7e2e672a47d11bd04269e27e5f3e8529cb # v6.0.0
+        uses: pnpm/action-setup@91ab88e2619ed1f46221f0ba42d1492c02baf788 # v6.0.6
         with:
           # Keep an explicit pnpm major because this repo's packageManager is Yarn.
           version: 10
@@ -77,7 +77,7 @@ jobs:
 
       - name: Cache npm
         if: matrix.pm == 'npm'
-        uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.5
         with:
           path: ${{ steps.npm-cache-dir.outputs.dir }}
           key: ${{ runner.os }}-node-${{ matrix.node }}-npm-${{ hashFiles('**/package-lock.json') }}
@@ -94,7 +94,7 @@ jobs:
 
       - name: Cache pnpm
         if: matrix.pm == 'pnpm'
-        uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.5
         with:
           path: ${{ steps.pnpm-cache-dir.outputs.dir }}
           key: ${{ runner.os }}-node-${{ matrix.node }}-pnpm-${{ hashFiles('**/pnpm-lock.yaml') }}
@@ -115,7 +115,7 @@ jobs:
 
       - name: Cache yarn
         if: matrix.pm == 'yarn'
-        uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.5
         with:
           path: ${{ steps.yarn-cache-dir.outputs.dir }}
           key: ${{ runner.os }}-node-${{ matrix.node }}-yarn-${{ hashFiles('**/yarn.lock') }}
@@ -124,7 +124,7 @@ jobs:
 
       - name: Cache bun
         if: matrix.pm == 'bun'
-        uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.5
         with:
           path: ~/.bun/install/cache
           key: ${{ runner.os }}-bun-${{ hashFiles('**/bun.lockb') }}
@@ -220,6 +220,10 @@ jobs:
         run: node scripts/ci/check-unicode-safety.js
         continue-on-error: false
 
+      - name: Validate no personal paths
+        run: node scripts/ci/validate-no-personal-paths.js
+        continue-on-error: false
+
   security:
     name: Security Scan
     runs-on: ubuntu-latest

.github/workflows/reusable-test.yml

@@ -36,7 +36,7 @@ jobs:
 
       - name: Setup pnpm
         if: inputs.package-manager == 'pnpm' && inputs.node-version != '18.x'
-        uses: pnpm/action-setup@08c4be7e2e672a47d11bd04269e27e5f3e8529cb # v6.0.0
+        uses: pnpm/action-setup@91ab88e2619ed1f46221f0ba42d1492c02baf788 # v6.0.6
         with:
           # Keep an explicit pnpm major because this repo's packageManager is Yarn.
           version: 10
@@ -67,7 +67,7 @@ jobs:
 
       - name: Cache npm
         if: inputs.package-manager == 'npm'
-        uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.5
         with:
           path: ${{ steps.npm-cache-dir.outputs.dir }}
           key: ${{ runner.os }}-node-${{ inputs.node-version }}-npm-${{ hashFiles('**/package-lock.json') }}
@@ -84,7 +84,7 @@ jobs:
 
       - name: Cache pnpm
         if: inputs.package-manager == 'pnpm'
-        uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.5
         with:
           path: ${{ steps.pnpm-cache-dir.outputs.dir }}
           key: ${{ runner.os }}-node-${{ inputs.node-version }}-pnpm-${{ hashFiles('**/pnpm-lock.yaml') }}
@@ -105,7 +105,7 @@ jobs:
 
       - name: Cache yarn
         if: inputs.package-manager == 'yarn'
-        uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.5
         with:
           path: ${{ steps.yarn-cache-dir.outputs.dir }}
           key: ${{ runner.os }}-node-${{ inputs.node-version }}-yarn-${{ hashFiles('**/yarn.lock') }}
@@ -114,7 +114,7 @@ jobs:
 
       - name: Cache bun
         if: inputs.package-manager == 'bun'
-        uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.5
         with:
           path: ~/.bun/install/cache
           key: ${{ runner.os }}-bun-${{ hashFiles('**/bun.lockb') }}

.github/workflows/reusable-validate.yml

@@ -50,3 +50,6 @@ jobs:
 
       - name: Check unicode safety
         run: node scripts/ci/check-unicode-safety.js
+
+      - name: Validate no personal paths
+        run: node scripts/ci/validate-no-personal-paths.js

.kiro/skills/search-first/SKILL.md

@@ -21,6 +21,12 @@ Use this skill when:
 - The user asks "add X functionality" and you're about to write code
 - Before creating a new utility, helper, or abstraction
 
+## Scope and Approval Rules
+
+Default to read-only research: inspect the repo, package metadata, docs, and public examples before recommending a dependency or integration. Do not install packages, configure MCP servers, publish artifacts, open PRs, or make external write actions from this skill unless the user has explicitly approved that action in the current task.
+
+When a candidate requires credentials, paid services, network writes, or project-wide config changes, return a recommendation and approval checkpoint instead of applying it directly.
+
 ## Workflow
 
 ```
@@ -45,9 +51,9 @@ Use this skill when:
 │     │ as-is   │  │  /Wrap   │  │  Custom  │  │
 │     └─────────┘  └──────────┘  └─────────┘  │
 ├─────────────────────────────────────────────┤
-│  5. IMPLEMENT                               │
-│     Install package / Configure MCP /       │
-│     Write minimal custom code               │
+│  5. APPROVAL CHECKPOINT / IMPLEMENT         │
+│     Recommend package / MCP / custom code   │
+│     Apply only after explicit approval      │
 └─────────────────────────────────────────────┘
 ```
 
@@ -55,10 +61,10 @@ Use this skill when:
 
 | Signal | Action |
 |--------|--------|
-| Exact match, well-maintained, MIT/Apache | **Adopt** — install and use directly |
-| Partial match, good foundation | **Extend** — install + write thin wrapper |
-| Multiple weak matches | **Compose** — combine 2-3 small packages |
-| Nothing suitable found | **Build** — write custom, but informed by research |
+| Exact match, well-maintained, MIT/Apache | **Adopt** — recommend the package and request approval before install or config changes |
+| Partial match, good foundation | **Extend** — recommend the package plus a thin wrapper, then wait for approval before applying |
+| Multiple weak matches | **Compose** — propose 2-3 small packages and the integration plan before installing anything |
+| Nothing suitable found | **Build** — explain why custom code is warranted, then implement only within the approved task scope |
 
 ## How to Use
 
@@ -135,8 +141,8 @@ Combine for progressive discovery:
 Need: Check markdown files for broken links
 Search: npm "markdown dead link checker"
 Found: textlint-rule-no-dead-link (score: 9/10)
-Action: ADOPT — npm install textlint-rule-no-dead-link
-Result: Zero custom code, battle-tested solution
+Action: ADOPT — recommend `textlint-rule-no-dead-link` and ask before installing it
+Result: Zero custom code if approved, battle-tested solution
 ```
 
 ### Example 2: "Add HTTP client wrapper"
@@ -144,8 +150,8 @@ Result: Zero custom code, battle-tested solution
 Need: Resilient HTTP client with retries and timeout handling
 Search: npm "http client retry", PyPI "httpx retry"
 Found: got (Node) with retry plugin, httpx (Python) with built-in retry
-Action: ADOPT — use got/httpx directly with retry config
-Result: Zero custom code, production-proven libraries
+Action: ADOPT — recommend `got`/`httpx` directly with retry config and ask before changing dependencies
+Result: Zero custom code if approved, production-proven libraries
 ```
 
 ### Example 3: "Add config file linter"
@@ -153,8 +159,8 @@ Result: Zero custom code, production-proven libraries
 Need: Validate project config files against a schema
 Search: npm "config linter schema", "json schema validator cli"
 Found: ajv-cli (score: 8/10)
-Action: ADOPT + EXTEND — install ajv-cli, write project-specific schema
-Result: 1 package + 1 schema file, no custom validation logic
+Action: ADOPT + EXTEND — recommend `ajv-cli` plus a project-specific schema, then wait for approval before install/write
+Result: 1 package + 1 schema file if approved, no custom validation logic
 ```
 
 ## Anti-Patterns

.opencode/opencode.json

@@ -22,6 +22,11 @@
   "plugin": [
     "./plugins"
   ],
+  "skills": {
+    "paths": [
+      "../skills"
+    ]
+  },
   "agent": {
     "build": {
       "description": "Primary coding agent for development work",

.opencode/plugins/ecc-hooks.ts

@@ -43,6 +43,14 @@ export const ECCHooksPlugin: ECCHooksPluginFn = async ({
     return path.join(worktreePath, p)
   }
 
+  function hasProjectFile(relativePath: string): boolean {
+    try {
+      return fs.existsSync(resolvePath(relativePath))
+    } catch {
+      return false
+    }
+  }
+
   const pendingToolChanges = new Map<string, { path: string; type: "added" | "modified" }>()
   let writeCounter = 0
 
@@ -275,13 +283,8 @@ export const ECCHooksPlugin: ECCHooksPluginFn = async ({
       log("info", `[ECC] Session started - profile=${currentProfile}`)
 
       // Check for project-specific context files
-      try {
-        const hasClaudeMd = await $`test -f ${worktree}/CLAUDE.md && echo "yes"`.text()
-        if (hasClaudeMd.trim() === "yes") {
-          log("info", "[ECC] Found CLAUDE.md - loading project context")
-        }
-      } catch {
-        // No CLAUDE.md found
+      if (hasProjectFile("CLAUDE.md")) {
+        log("info", "[ECC] Found CLAUDE.md - loading project context")
       }
     },
 
@@ -400,7 +403,7 @@ export const ECCHooksPlugin: ECCHooksPluginFn = async ({
         ECC_PLUGIN: "true",
         ECC_HOOK_PROFILE: currentProfile,
         ECC_DISABLED_HOOKS: process.env.ECC_DISABLED_HOOKS || "",
-        PROJECT_ROOT: worktree || directory,
+        PROJECT_ROOT: worktreePath,
       }
 
       // Detect package manager
@@ -411,12 +414,9 @@ export const ECCHooksPlugin: ECCHooksPluginFn = async ({
         "package-lock.json": "npm",
       }
       for (const [lockfile, pm] of Object.entries(lockfiles)) {
-        try {
-          await $`test -f ${worktree}/${lockfile}`
+        if (hasProjectFile(lockfile)) {
           env.PACKAGE_MANAGER = pm
           break
-        } catch {
-          // Not found, try next
         }
       }
 
@@ -430,11 +430,8 @@ export const ECCHooksPlugin: ECCHooksPluginFn = async ({
       }
       const detected: string[] = []
       for (const [file, lang] of Object.entries(langDetectors)) {
-        try {
-          await $`test -f ${worktree}/${file}`
+        if (hasProjectFile(file)) {
           detected.push(lang)
-        } catch {
-          // Not found
         }
       }
       if (detected.length > 0) {

.qwen/QWEN.md

@@ -0,0 +1,25 @@
+# Qwen CLI Configuration
+
+This directory contains ECC's Qwen CLI install template.
+
+## Runtime Location
+
+The source `.qwen/` directory in this repository is copied into a user's home-level `~/.qwen/` install root when running:
+
+```bash
+./install.sh --target qwen --profile minimal
+```
+
+The managed install also writes `~/.qwen/ecc-install-state.json` so future ECC updates and uninstalls can distinguish ECC-owned files from user-owned Qwen configuration.
+
+## Installed Surface
+
+The Qwen target installs the same managed manifest modules used by other harness adapters:
+
+- `rules/`
+- `agents/`
+- `commands/`
+- `skills/`
+- `mcp-configs/`
+
+Hook runtime files are intentionally not selected for Qwen until the Qwen hook/event contract is verified.

AGENTS.md

@@ -1,6 +1,6 @@
 # Everything Claude Code (ECC) — Agent Instructions
 
-This is a **production-ready AI coding plugin** providing 48 specialized agents, 184 skills, 79 commands, and automated hook workflows for software development.
+This is a **production-ready AI coding plugin** providing 53 specialized agents, 203 skills, 69 commands, and automated hook workflows for software development.
 
 **Version:** 2.0.0-rc.1
 
@@ -145,9 +145,9 @@ Troubleshoot failures: check test isolation → verify mocks → fix implementat
 ## Project Structure
 
 ```
-agents/          — 48 specialized subagents
-skills/          — 184 workflow skills and domain knowledge
-commands/        — 79 slash commands
+agents/          — 53 specialized subagents
+skills/          — 203 workflow skills and domain knowledge
+commands/        — 69 slash commands
 hooks/           — Trigger-based automations
 rules/           — Always-follow guidelines (common + per-language)
 scripts/         — Cross-platform Node.js utilities

CONTRIBUTING.md

@@ -167,6 +167,8 @@ Short version:
 - [ ] Tested with Claude Code
 - [ ] Links to related skills
 - [ ] No sensitive data (API keys, tokens, paths)
+- [ ] Frontmatter declares `name:` matching the directory name
+- [ ] Frontmatter `description:` is an inline string or folded (`>`) scalar — not a literal block (`|`, `|-`, or `|+`), which preserves internal newlines and breaks flat-table renderers
 
 ### Example Skills
 

README.md

@@ -1,4 +1,4 @@
-**Language:** English | [Português (Brasil)](docs/pt-BR/README.md) | [简体中文](README.zh-CN.md) | [繁體中文](docs/zh-TW/README.md) | [日本語](docs/ja-JP/README.md) | [한국어](docs/ko-KR/README.md) | [Türkçe](docs/tr/README.md)
+**Language:** English | [Português (Brasil)](docs/pt-BR/README.md) | [简体中文](README.zh-CN.md) | [繁體中文](docs/zh-TW/README.md) | [日本語](docs/ja-JP/README.md) | [한국어](docs/ko-KR/README.md) | [Türkçe](docs/tr/README.md) | [Русский](docs/ru/README.md)
 
 # Everything Claude Code
 
@@ -25,10 +25,10 @@
 
 <div align="center">
 
-**Language / 语言 / 語言 / Dil**
+**Language / 语言 / 語言 / Dil / Язык**
 
 [**English**](README.md) | [Português (Brasil)](docs/pt-BR/README.md) | [简体中文](README.zh-CN.md) | [繁體中文](docs/zh-TW/README.md) | [日本語](docs/ja-JP/README.md) | [한국어](docs/ko-KR/README.md)
- | [Türkçe](docs/tr/README.md)
+ | [Türkçe](docs/tr/README.md) | [Русский](docs/ru/README.md)
 
 </div>
 
@@ -89,11 +89,12 @@ This repo is the raw code only. The guides explain everything.
 ### v2.0.0-rc.1 — Surface Refresh, Operator Workflows, and ECC 2.0 Alpha (Apr 2026)
 
 - **Dashboard GUI** — New Tkinter-based desktop application (`ecc_dashboard.py` or `npm run dashboard`) with dark/light theme toggle, font customization, and project logo in header and taskbar.
-- **Public surface synced to the live repo** — metadata, catalog counts, plugin manifests, and install-facing docs now match the actual OSS surface: 38 agents, 156 skills, and 72 legacy command shims.
+- **Public surface synced to the live repo** — metadata, catalog counts, plugin manifests, and install-facing docs now match the actual OSS surface: 53 agents, 203 skills, and 69 legacy command shims.
 - **Operator and outbound workflow expansion** — `brand-voice`, `social-graph-ranker`, `connections-optimizer`, `customer-billing-ops`, `ecc-tools-cost-audit`, `google-workspace-ops`, `project-flow-ops`, and `workspace-surface-audit` round out the operator lane.
 - **Media and launch tooling** — `manim-video`, `remotion-video-creation`, and upgraded social publishing surfaces make technical explainers and launch content part of the same system.
 - **Framework and product surface growth** — `nestjs-patterns`, richer Codex/OpenCode install surfaces, and expanded cross-harness packaging keep the repo usable beyond Claude Code alone.
 - **ECC 2.0 alpha is in-tree** — the Rust control-plane prototype in `ecc2/` now builds locally and exposes `dashboard`, `start`, `sessions`, `status`, `stop`, `resume`, and `daemon` commands. It is usable as an alpha, not yet a general release.
+- **Operator status snapshots** — `ecc status --markdown --write status.md` turns the local state store into a portable handoff covering readiness, active sessions, skill-run health, install health, pending governance events, and linked work items from Linear/GitHub/handoffs. Use `ecc work-items upsert ...` for manual entries, `ecc work-items sync-github --repo owner/repo` for PR/issue queue state, and `ecc status --exit-code` to fail automation when readiness needs attention.
 - **Ecosystem hardening** — AgentShield, ECC Tools cost controls, billing portal work, and website refreshes continue to ship around the core plugin instead of drifting into separate silos.
 
 ### v1.9.0 — Selective Install & Language Expansion (Mar 2026)
@@ -179,6 +180,44 @@ Most Claude Code users should use exactly one install path:
 
 If you already layered multiple installs and things look duplicated, skip straight to [Reset / Uninstall ECC](#reset--uninstall-ecc).
 
+### Low-context / no-hooks path
+
+If hooks feel too global or you only want ECC's rules, agents, commands, and core workflow skills, skip the plugin and use the minimal manual profile:
+
+```bash
+./install.sh --profile minimal --target claude
+```
+
+```powershell
+.\install.ps1 --profile minimal --target claude
+# or
+npx ecc-install --profile minimal --target claude
+```
+
+This profile intentionally excludes `hooks-runtime`.
+
+If you want the normal core profile but need hooks off, use:
+
+```bash
+./install.sh --profile core --without baseline:hooks --target claude
+```
+
+Add hooks later only if you want runtime enforcement:
+
+```bash
+./install.sh --target claude --modules hooks-runtime
+```
+
+### Find the right components first
+
+If you are not sure which ECC profile or component to install, ask the packaged advisor from any project:
+
+```bash
+npx ecc consult "security reviews" --target claude
+```
+
+It returns matching components, related profiles, and preview/install commands. Use the preview command before installing if you want to inspect the exact file plan.
+
 ### Step 1: Install the Plugin (Recommended)
 
 > NOTE: The plugin is convenient, but the OSS installer below is still the most reliable path if your Claude Code build has trouble resolving self-hosted marketplace entries.
@@ -188,7 +227,7 @@ If you already layered multiple installs and things look duplicated, skip straig
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # Install plugin
-/plugin install everything-claude-code@everything-claude-code
+/plugin install ecc@ecc
 ```
 
 ### Naming + Migration Note
@@ -196,18 +235,18 @@ If you already layered multiple installs and things look duplicated, skip straig
 ECC now has three public identifiers, and they are not interchangeable:
 
 - GitHub source repo: `affaan-m/everything-claude-code`
-- Claude marketplace/plugin identifier: `everything-claude-code@everything-claude-code`
+- Claude marketplace/plugin identifier: `ecc@ecc`
 - npm package: `ecc-universal`
 
-This is intentional. Anthropic marketplace/plugin installs are keyed by a canonical plugin identifier, so ECC standardized on `everything-claude-code@everything-claude-code` to keep the listing name, `/plugin install`, `/plugin list`, and repo docs aligned to one public install surface. Older posts may still show the old short-form nickname; that shorthand is deprecated. Separately, the npm package stayed on `ecc-universal`, so npm installs and marketplace installs intentionally use different names.
+This is intentional. Anthropic marketplace/plugin installs are keyed by a canonical plugin identifier, so ECC uses `ecc@ecc` to keep tool names and slash-command namespaces short enough for strict Desktop/API validators. Older posts may still show the former long marketplace identifier; treat that as a legacy alias only. Separately, the npm package stayed on `ecc-universal`, so npm installs and marketplace installs intentionally use different names.
 
-### Step 2: Install Rules (Required)
+### Step 2: Install Rules Only If You Need Them
 
 > WARNING: **Important:** Claude Code plugins cannot distribute `rules` automatically.
 >
 > If you already installed ECC via `/plugin install`, **do not run `./install.sh --profile full`, `.\install.ps1 --profile full`, or `npx ecc-install --profile full` afterward**. The plugin already loads ECC skills, commands, and hooks. Running the full installer after a plugin install copies those same surfaces into your user directories and can create duplicate skills plus duplicate runtime behavior.
 >
-> For plugin installs, manually copy only the `rules/` directories you want. Start with `rules/common` plus one language or framework pack you actually use. Do not copy every rules directory unless you explicitly want all of that context in Claude.
+> For plugin installs, manually copy only the `rules/` directories you want under `~/.claude/rules/ecc/`. Start with `rules/common` plus one language or framework pack you actually use. Do not copy every rules directory unless you explicitly want all of that context in Claude.
 >
 > Use the full installer only when you are doing a fully manual ECC install instead of the plugin path.
 >
@@ -221,10 +260,10 @@ cd everything-claude-code
 # Install dependencies (pick your package manager)
 npm install        # or: pnpm install | yarn install | bun install
 
-# Plugin install path: copy only rules
-mkdir -p ~/.claude/rules
-cp -R rules/common ~/.claude/rules/
-cp -R rules/typescript ~/.claude/rules/
+# Plugin install path: copy only ECC rules into an ECC-owned namespace
+mkdir -p ~/.claude/rules/ecc
+cp -R rules/common ~/.claude/rules/ecc/
+cp -R rules/typescript ~/.claude/rules/ecc/
 
 # Fully manual ECC install path (use this instead of /plugin install)
 # ./install.sh --profile full
@@ -233,10 +272,10 @@ cp -R rules/typescript ~/.claude/rules/
 ```powershell
 # Windows PowerShell
 
-# Plugin install path: copy only rules
-New-Item -ItemType Directory -Force -Path "$HOME/.claude/rules" | Out-Null
-Copy-Item -Recurse rules/common "$HOME/.claude/rules/"
-Copy-Item -Recurse rules/typescript "$HOME/.claude/rules/"
+# Plugin install path: copy only ECC rules into an ECC-owned namespace
+New-Item -ItemType Directory -Force -Path "$HOME/.claude/rules/ecc" | Out-Null
+Copy-Item -Recurse rules/common "$HOME/.claude/rules/ecc/"
+Copy-Item -Recurse rules/typescript "$HOME/.claude/rules/ecc/"
 
 # Fully manual ECC install path (use this instead of /plugin install)
 # .\install.ps1 --profile full
@@ -265,7 +304,7 @@ If you choose this path, stop there. Do not also run `/plugin install`.
 
 If ECC feels duplicated, intrusive, or broken, do not keep reinstalling it on top of itself.
 
-- **Plugin path:** remove the plugin from Claude Code, then delete the specific rule folders you manually copied under `~/.claude/rules/`.
+- **Plugin path:** remove the plugin from Claude Code, then delete the specific rule folders you manually copied under `~/.claude/rules/ecc/`.
 - **Manual installer / CLI path:** from the repo root, preview removal first:
 
 ```bash
@@ -302,17 +341,17 @@ If you stacked methods, clean up in this order:
 # Skills are the primary workflow surface.
 # Existing slash-style command names still work while ECC migrates off commands/.
 
-# Plugin install uses the namespaced form
+# Plugin install uses the canonical namespaced form
 /ecc:plan "Add user authentication"
 
 # Manual install keeps the shorter slash form:
 # /plan "Add user authentication"
 
 # Check available commands
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 
-**That's it!** You now have access to 48 agents, 184 skills, and 79 legacy command shims.
+**That's it!** You now have access to 53 agents, 203 skills, and 69 legacy command shims.
 
 ### Dashboard GUI
 
@@ -390,6 +429,12 @@ export ECC_HOOK_PROFILE=standard
 
 # Comma-separated hook IDs to disable
 export ECC_DISABLED_HOOKS="pre:bash:tmux-reminder,post:edit:typecheck"
+
+# Cap SessionStart additional context (default: 8000 chars)
+export ECC_SESSION_START_MAX_CHARS=4000
+
+# Disable SessionStart additional context entirely for low-context/local-model setups
+export ECC_SESSION_START_CONTEXT=off
 ```
 
 ---
@@ -404,7 +449,7 @@ everything-claude-code/
 |   |-- plugin.json         # Plugin metadata and component paths
 |   |-- marketplace.json    # Marketplace catalog for /plugin marketplace add
 |
-|-- agents/           # 36 specialized subagents for delegation
+|-- agents/           # 53 specialized subagents for delegation
 |   |-- planner.md           # Feature implementation planning
 |   |-- architect.md         # System design decisions
 |   |-- tdd-guide.md         # Test-driven development
@@ -499,17 +544,15 @@ everything-claude-code/
 |   |-- autonomous-loops/           # Autonomous loop patterns: sequential pipelines, PR loops, DAG orchestration (NEW)
 |   |-- plankton-code-quality/      # Write-time code quality enforcement with Plankton hooks (NEW)
 |
-|-- commands/         # Legacy slash-entry shims; prefer skills/
-|   |-- tdd.md              # /tdd - Test-driven development
+|-- commands/         # Maintained slash-entry compatibility; prefer skills/
 |   |-- 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
+|   |-- quality-gate.md     # /quality-gate - Verification gate
 |   |-- learn.md            # /learn - Extract patterns mid-session (Longform Guide)
 |   |-- learn-eval.md       # /learn-eval - Extract, evaluate, and save patterns (NEW)
 |   |-- 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)
@@ -526,15 +569,19 @@ everything-claude-code/
 |   |-- 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)
+|-- legacy-command-shims/   # Opt-in archive for retired shims such as /tdd and /eval
+|   |-- tdd.md              # /tdd - Prefer the tdd-workflow skill
+|   |-- e2e.md              # /e2e - Prefer the e2e-testing skill
+|   |-- eval.md             # /eval - Prefer the eval-harness skill
+|   |-- verify.md           # /verify - Prefer the verification-loop skill
+|   |-- orchestrate.md      # /orchestrate - Prefer dmux-workflows or multi-workflow
 |
-|-- rules/            # Always-follow guidelines (copy to ~/.claude/rules/)
+|-- rules/            # Always-follow guidelines (copy to ~/.claude/rules/ecc/)
 |   |-- README.md            # Structure overview and installation guide
 |   |-- common/              # Language-agnostic principles
 |   |   |-- coding-style.md    # Immutability, file organization
@@ -721,7 +768,7 @@ The easiest way to use this repo - install as a Claude Code plugin:
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # Install the plugin
-/plugin install everything-claude-code@everything-claude-code
+/plugin install ecc@ecc
 ```
 
 Or add directly to your `~/.claude/settings.json`:
@@ -737,7 +784,7 @@ Or add directly to your `~/.claude/settings.json`:
     }
   },
   "enabledPlugins": {
-    "everything-claude-code@everything-claude-code": true
+    "ecc@ecc": true
   }
 }
 ```
@@ -751,17 +798,17 @@ This gives you instant access to all commands, agents, skills, and hooks.
 > git clone https://github.com/affaan-m/everything-claude-code.git
 >
 > # Option A: User-level rules (applies to all projects)
-> 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
-> cp -r everything-claude-code/rules/python ~/.claude/rules/
-> cp -r everything-claude-code/rules/golang ~/.claude/rules/
-> cp -r everything-claude-code/rules/php ~/.claude/rules/
+> mkdir -p ~/.claude/rules/ecc
+> cp -r everything-claude-code/rules/common ~/.claude/rules/ecc/
+> cp -r everything-claude-code/rules/typescript ~/.claude/rules/ecc/   # pick your stack
+> cp -r everything-claude-code/rules/python ~/.claude/rules/ecc/
+> cp -r everything-claude-code/rules/golang ~/.claude/rules/ecc/
+> cp -r everything-claude-code/rules/php ~/.claude/rules/ecc/
 >
 > # 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
+> mkdir -p .claude/rules/ecc
+> cp -r everything-claude-code/rules/common .claude/rules/ecc/
+> cp -r everything-claude-code/rules/typescript .claude/rules/ecc/     # pick your stack
 > ```
 
 ---
@@ -778,26 +825,30 @@ git clone https://github.com/affaan-m/everything-claude-code.git
 cp everything-claude-code/agents/*.md ~/.claude/agents/
 
 # Copy rules directories (common + language-specific)
-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
-cp -r everything-claude-code/rules/python ~/.claude/rules/
-cp -r everything-claude-code/rules/golang ~/.claude/rules/
-cp -r everything-claude-code/rules/php ~/.claude/rules/
+mkdir -p ~/.claude/rules/ecc
+cp -r everything-claude-code/rules/common ~/.claude/rules/ecc/
+cp -r everything-claude-code/rules/typescript ~/.claude/rules/ecc/   # pick your stack
+cp -r everything-claude-code/rules/python ~/.claude/rules/ecc/
+cp -r everything-claude-code/rules/golang ~/.claude/rules/ecc/
+cp -r everything-claude-code/rules/php ~/.claude/rules/ecc/
 
 # Copy skills first (primary workflow surface)
 # Recommended (new users): core/general skills only
-cp -r everything-claude-code/.agents/skills/* ~/.claude/skills/
-cp -r everything-claude-code/skills/search-first ~/.claude/skills/
+mkdir -p ~/.claude/skills/ecc
+cp -r everything-claude-code/.agents/skills/* ~/.claude/skills/ecc/
+cp -r everything-claude-code/skills/search-first ~/.claude/skills/ecc/
 
 # Optional: add niche/framework-specific skills only when needed
 # for s in django-patterns django-tdd laravel-patterns springboot-patterns; do
-# cp -r everything-claude-code/skills/$s ~/.claude/skills/
+# cp -r everything-claude-code/skills/$s ~/.claude/skills/ecc/
 # done
 
-# Optional: keep legacy slash-command compatibility during migration
+# Optional: keep maintained slash-command compatibility during migration
 mkdir -p ~/.claude/commands
 cp everything-claude-code/commands/*.md ~/.claude/commands/
+
+# Retired shims live in legacy-command-shims/commands/.
+# Copy individual files from there only if you still need old names such as /tdd.
 ```
 
 #### Install hooks
@@ -824,7 +875,11 @@ Windows note: the Claude config directory is `%USERPROFILE%\\.claude`, not `~/cl
 
 #### Configure MCPs
 
-Copy desired MCP server definitions from `mcp-configs/mcp-servers.json` into your official Claude Code config in `~/.claude/settings.json`, or into a project-scoped `.mcp.json` if you want repo-local MCP access.
+Claude plugin installs intentionally do not auto-enable ECC's bundled MCP server definitions. This avoids overlong plugin MCP tool names on strict third-party gateways while keeping manual MCP setup available.
+
+Use Claude Code's `/mcp` command or CLI-managed MCP setup for live Claude Code server changes. Use `/mcp` for Claude Code runtime disables; Claude Code persists those choices in `~/.claude.json`.
+
+For repo-local MCP access, copy desired MCP server definitions from `mcp-configs/mcp-servers.json` into a project-scoped `.mcp.json`.
 
 If you already run your own copies of ECC-bundled MCPs, set:
 
@@ -832,7 +887,7 @@ If you already run your own copies of ECC-bundled MCPs, set:
 export ECC_DISABLED_MCPS="github,context7,exa,playwright,sequential-thinking,memory"
 ```
 
-ECC-managed install and Codex sync flows will skip or remove those bundled servers instead of re-adding duplicates.
+ECC-managed install and Codex sync flows will skip or remove those bundled servers instead of re-adding duplicates. `ECC_DISABLED_MCPS` is an ECC install/sync filter, not a live Claude Code toggle.
 
 **Important:** Replace `YOUR_*_HERE` placeholders with your actual API keys.
 
@@ -857,7 +912,7 @@ You are a senior code reviewer...
 
 ### Skills
 
-Skills are the primary workflow surface. They can be invoked directly, suggested automatically, and reused by agents. ECC still ships `commands/` during migration, but new workflow development should land in `skills/` first.
+Skills are the primary workflow surface. They can be invoked directly, suggested automatically, and reused by agents. ECC still ships maintained `commands/` during migration, while retired short-name shims live under `legacy-command-shims/` for explicit opt-in only. New workflow development should land in `skills/` first.
 
 ```markdown
 # TDD Workflow
@@ -903,16 +958,16 @@ See [`rules/README.md`](rules/README.md) for installation and structure details.
 
 ## Which Agent Should I Use?
 
-Not sure where to start? Use this quick reference. Skills are the canonical workflow surface; slash entries below are the compatibility form most users already know.
+Not sure where to start? Use this quick reference. Skills are the canonical workflow surface; maintained slash entries stay available for command-first workflows.
 
-| I want to... | Use this command | Agent used |
+| I want to... | Use this surface | Agent used |
 |--------------|-----------------|------------|
 | Plan a new feature | `/ecc:plan "Add auth"` | planner |
 | Design system architecture | `/ecc:plan` + architect agent | architect |
-| Write code with tests first | `/tdd` | tdd-guide |
+| Write code with tests first | `tdd-workflow` skill | 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 |
+| Run end-to-end tests | `e2e-testing` skill | e2e-runner |
 | Find security vulnerabilities | `/security-scan` | security-reviewer |
 | Remove dead code | `/refactor-clean` | refactor-cleaner |
 | Update documentation | `/update-docs` | doc-updater |
@@ -923,19 +978,19 @@ Not sure where to start? Use this quick reference. Skills are the canonical work
 
 ### Common Workflows
 
-Slash forms below are shown because they are still the fastest familiar entrypoint. Under the hood, ECC is shifting these workflows toward skills-first definitions.
+Slash forms below are shown where they remain part of the maintained command surface. Retired short-name shims such as `/tdd` and `/eval` live in `legacy-command-shims/` for explicit opt-in only.
 
 **Starting a new feature:**
 ```
 /ecc:plan "Add user authentication with OAuth"
                                               → planner creates implementation blueprint
-/tdd                                          → tdd-guide enforces write-tests-first
+tdd-workflow skill                            → 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
+tdd-workflow skill                            → tdd-guide: write a failing test that reproduces it
                                               → implement the fix, verify test passes
 /code-review                                  → code-reviewer: catch regressions
 ```
@@ -943,7 +998,7 @@ Slash forms below are shown because they are still the fastest familiar entrypoi
 **Preparing for production:**
 ```
 /security-scan                                → security-reviewer: OWASP Top 10 audit
-/e2e                                          → e2e-runner: critical user flow tests
+e2e-testing skill                             → e2e-runner: critical user flow tests
 /test-coverage                                → verify 80%+ coverage
 ```
 
@@ -955,7 +1010,7 @@ Slash forms below are shown because they are still the fastest familiar entrypoi
 <summary><b>How do I check which agents/commands are installed?</b></summary>
 
 ```bash
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 
 This shows all available agents, commands, and skills from the plugin.
@@ -995,15 +1050,9 @@ Official references:
 <details>
 <summary><b>My context window is shrinking / Claude is running out of context</b></summary>
 
-Too many MCP servers eat your context. Each MCP tool description consumes tokens from your 200k window, potentially reducing it to ~70k.
+Too many MCP servers eat your context. Each MCP tool description consumes tokens from your 200k window, potentially reducing it to ~70k. SessionStart context is capped at 8000 characters by default; lower it with `ECC_SESSION_START_MAX_CHARS=4000` or disable it with `ECC_SESSION_START_CONTEXT=off` for local-model or low-context setups.
 
-**Fix:** Disable unused MCPs per project:
-```json
-// In your project's .claude/settings.json
-{
-  "disabledMcpServers": ["supabase", "railway", "vercel"]
-}
-```
+**Fix:** Disable unused MCPs from Claude Code with `/mcp`. Claude Code writes those runtime choices to `~/.claude.json`; `.claude/settings.json` and `.claude/settings.local.json` are not reliable toggles for already-loaded MCP servers.
 
 Keep under 10 MCPs enabled and under 80 tools active.
 </details>
@@ -1018,8 +1067,8 @@ Yes. Use Option 2 (manual installation) and copy only what you need:
 cp everything-claude-code/agents/*.md ~/.claude/agents/
 
 # Just rules
-mkdir -p ~/.claude/rules/
-cp -r everything-claude-code/rules/common ~/.claude/rules/
+mkdir -p ~/.claude/rules/ecc/
+cp -r everything-claude-code/rules/common ~/.claude/rules/ecc/
 ```
 
 Each component is fully independent.
@@ -1034,6 +1083,8 @@ Yes. ECC is cross-platform:
 - **OpenCode**: Full plugin support in `.opencode/`. See [OpenCode Support](#opencode-support).
 - **Codex**: First-class support for both macOS app and CLI, with adapter drift guards and SessionStart fallback. See PR [#257](https://github.com/affaan-m/everything-claude-code/pull/257).
 - **Antigravity**: Tightly integrated setup for workflows, skills, and flattened rules in `.agent/`. See [Antigravity Guide](docs/ANTIGRAVITY-GUIDE.md).
+- **JoyCode / CodeBuddy**: Project-local selective install adapters for commands, agents, skills, and flattened rules. See [JoyCode Adapter Guide](docs/JOYCODE-GUIDE.md).
+- **Qwen CLI**: Home-directory selective install adapter for commands, agents, skills, rules, and Qwen config. See [Qwen CLI Adapter Guide](docs/QWEN-GUIDE.md).
 - **Non-native harnesses**: Manual fallback path for Grok and similar interfaces. See [Manual Adaptation Guide](docs/MANUAL-ADAPTATION-GUIDE.md).
 - **Claude Code**: Native — this is the primary target.
 </details>
@@ -1098,7 +1149,7 @@ These are not bundled with ECC and are not audited by this repo, but they are wo
 
 ## Cursor IDE Support
 
-ECC provides **full Cursor IDE support** with hooks, rules, agents, skills, commands, and MCP configs adapted for Cursor's native format.
+ECC provides Cursor IDE support with hooks, rules, agents, skills, commands, and MCP configs adapted for Cursor's project layout.
 
 ### Quick Start (Cursor)
 
@@ -1121,11 +1172,17 @@ ECC provides **full Cursor IDE support** with hooks, rules, agents, skills, comm
 | Hook Events | 15 | sessionStart, beforeShellExecution, afterFileEdit, beforeMCPExecution, beforeSubmitPrompt, and 10 more |
 | Hook Scripts | 16 | Thin Node.js scripts delegating to `scripts/hooks/` via shared adapter |
 | Rules | 34 | 9 common (alwaysApply) + 25 language-specific (TypeScript, Python, Go, Swift, PHP) |
-| Agents | Shared | Via AGENTS.md at root (read by Cursor natively) |
-| Skills | Shared + Bundled | Via AGENTS.md at root and `.cursor/skills/` for translated additions |
+| Agents | 48 | `.cursor/agents/ecc-*.md` when installed; prefixed to avoid collisions with user or marketplace agents |
+| Skills | Shared + Bundled | `.cursor/skills/` for translated additions |
 | Commands | Shared | `.cursor/commands/` if installed |
 | MCP Config | Shared | `.cursor/mcp.json` if installed |
 
+### Cursor Loading Notes
+
+ECC does not install root `AGENTS.md` into `.cursor/`. Cursor treats nested `AGENTS.md` files as directory context, so copying ECC's repo identity into a host project would pollute that project.
+
+Cursor-native loading behavior can vary by Cursor build. ECC installs agents as `.cursor/agents/ecc-*.md`; if your Cursor build does not expose project agents, those files still work as explicit reference definitions instead of hidden global prompt context.
+
 ### Hook Architecture (DRY Adapter Pattern)
 
 Cursor has **more hook events than Claude Code** (20 vs 8). The `.cursor/hooks/adapter.js` module transforms Cursor's stdin JSON to Claude Code's format, allowing existing `scripts/hooks/*.js` to be reused without duplication.
@@ -1193,7 +1250,7 @@ Codex macOS app:
 |-----------|-------|---------|
 | Config | 1 | `.codex/config.toml` — top-level approvals/sandbox/web_search, MCP servers, notifications, profiles |
 | AGENTS.md | 2 | Root (universal) + `.codex/AGENTS.md` (Codex-specific supplement) |
-| Skills | 30 | `.agents/skills/` — SKILL.md + agents/openai.yaml per skill |
+| Skills | 32 | `.agents/skills/` — SKILL.md + agents/openai.yaml per skill |
 | MCP Servers | 6 | GitHub, Context7, Exa, Memory, Playwright, Sequential Thinking (7 with Supabase via `--update-mcp` sync) |
 | Profiles | 2 | `strict` (read-only sandbox) and `yolo` (full auto-approve) |
 | Agent Roles | 3 | `.codex/agents/` — explorer, reviewer, docs-researcher |
@@ -1202,14 +1259,17 @@ Codex macOS app:
 
 Skills at `.agents/skills/` are auto-loaded by Codex:
 
+Canonical Anthropic skills such as `claude-api`, `frontend-design`, and `skill-creator` are intentionally not re-bundled here. Install those from [`anthropics/skills`](https://github.com/anthropics/skills) when you want the official versions.
+
 | Skill | Description |
 |-------|-------------|
+| agent-introspection-debugging | Debug agent behavior, routing, and prompt boundaries |
+| agent-sort | Sort agent catalogs and assignment surfaces |
 | api-design | REST API design patterns |
 | article-writing | Long-form writing from notes and voice references |
 | backend-patterns | API design, database, caching |
 | brand-voice | Source-derived writing style profiles from real content |
 | bun-runtime | Bun as runtime, package manager, bundler, and test runner |
-| claude-api | Anthropic Claude API patterns for Python and TypeScript |
 | coding-standards | Universal coding standards |
 | content-engine | Platform-native social content and repurposing |
 | crosspost | Multi-platform content distribution across X, LinkedIn, Threads |
@@ -1228,6 +1288,7 @@ Skills at `.agents/skills/` are auto-loaded by Codex:
 | market-research | Source-attributed market and competitor research |
 | mcp-server-patterns | Build MCP servers with Node/TypeScript SDK |
 | nextjs-turbopack | Next.js 16+ and Turbopack incremental bundling |
+| product-capability | Translate product goals into scoped capability maps |
 | security-review | Comprehensive security checklist |
 | strategic-compact | Context management |
 | tdd-workflow | Test-driven development with 80%+ coverage |
@@ -1278,9 +1339,9 @@ The configuration is automatically detected from `.opencode/opencode.json`.
 
 | Feature | Claude Code | OpenCode | Status |
 |---------|-------------|----------|--------|
-| Agents | PASS: 48 agents | PASS: 12 agents | **Claude Code leads** |
-| Commands | PASS: 79 commands | PASS: 31 commands | **Claude Code leads** |
-| Skills | PASS: 184 skills | PASS: 37 skills | **Claude Code leads** |
+| Agents | PASS: 53 agents | PASS: 12 agents | **Claude Code leads** |
+| Commands | PASS: 69 commands | PASS: 31 commands | **Claude Code leads** |
+| Skills | PASS: 203 skills | PASS: 37 skills | **Claude Code leads** |
 | Hooks | PASS: 8 event types | PASS: 11 events | **OpenCode has more!** |
 | Rules | PASS: 29 rules | PASS: 13 instructions | **Claude Code leads** |
 | MCP Servers | PASS: 14 servers | PASS: Full | **Full parity** |
@@ -1300,21 +1361,17 @@ OpenCode's plugin system is MORE sophisticated than Claude Code with 20+ event t
 
 **Additional OpenCode events**: `file.edited`, `file.watcher.updated`, `message.updated`, `lsp.client.diagnostics`, `tui.toast.show`, and more.
 
-### Available Slash Entry Shims (31+)
+### Maintained Slash Entries
 
 | 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 |
+| `/quality-gate` | Run the maintained verification gate |
 | `/update-docs` | Update documentation |
 | `/update-codemaps` | Update codemaps |
 | `/test-coverage` | Analyze coverage |
@@ -1387,9 +1444,9 @@ ECC is the **first plugin to maximize every major AI coding tool**. Here's how e
 
 | Feature | Claude Code | Cursor IDE | Codex CLI | OpenCode |
 |---------|------------|------------|-----------|----------|
-| **Agents** | 48 | Shared (AGENTS.md) | Shared (AGENTS.md) | 12 |
-| **Commands** | 79 | Shared | Instruction-based | 31 |
-| **Skills** | 184 | Shared | 10 (native format) | 37 |
+| **Agents** | 53 | Shared (AGENTS.md) | Shared (AGENTS.md) | 12 |
+| **Commands** | 69 | Shared | Instruction-based | 31 |
+| **Skills** | 203 | Shared | 10 (native format) | 37 |
 | **Hook Events** | 8 types | 15 types | None yet | 11 types |
 | **Hook Scripts** | 20+ scripts | 16 scripts (DRY adapter) | N/A | Plugin hooks |
 | **Rules** | 34 (common + lang) | 34 (YAML frontmatter) | Instruction-based | 13 instructions |
@@ -1475,7 +1532,8 @@ The `strategic-compact` skill (included in this plugin) suggests `/compact` at l
 
 - Keep under 10 MCPs enabled per project
 - Keep under 80 tools active
-- Use `disabledMcpServers` in project config to disable unused ones
+- Use `/mcp` to disable unused Claude Code MCP servers; those runtime choices persist in `~/.claude.json`
+- Use `ECC_DISABLED_MCPS` only to filter ECC-generated MCP configs during install/sync flows
 
 ### Agent Teams Cost Warning
 

README.zh-CN.md

@@ -102,12 +102,12 @@
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # 安装插件
-/plugin install everything-claude-code@everything-claude-code
+/plugin install ecc@ecc
 ```
 
-> 安装名称说明：较早的帖子里可能还会出现旧的短别名。那个旧缩写现在已经废弃。Anthropic 的 marketplace/plugin 安装是按规范化插件标识符寻址的，因此 ECC 统一为 `everything-claude-code@everything-claude-code`，这样市场条目、安装命令、`/plugin list` 输出和仓库文档都使用同一个公开名称，不再出现两个名字指向同一插件的混乱。
+> 安装名称说明：较早的帖子里可能还会出现较长的旧标识符。Anthropic 的 marketplace/plugin 安装是按规范化插件标识符寻址的，因此 ECC 现在统一为 `ecc@ecc`，让工具名和 slash command 命名空间保持简短。
 
-### 第二步：安装规则（必需）
+### 第二步：仅在需要时安装规则
 
 > WARNING: **重要提示：** Claude Code 插件无法自动分发 `rules`。
 >
@@ -157,10 +157,10 @@ Copy-Item -Recurse rules/typescript "$HOME/.claude/rules/"
 # /plan "添加用户认证"
 
 # 查看可用命令
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 
-**完成！** 你现在可以使用 48 个代理、184 个技能和 79 个命令。
+**完成！** 你现在可以使用 53 个代理、203 个技能和 69 个命令。
 
 ### multi-* 命令需要额外配置
 
@@ -330,17 +330,15 @@ everything-claude-code/
 |   |-- autonomous-loops/           # 自主循环模式：顺序流水线、PR 循环、DAG 编排（新增）
 |   |-- plankton-code-quality/      # 基于 Plankton 钩子的实时代码质量管控（新增）
 |
-|-- commands/         # 传统斜杠命令兼容层；优先使用 skills/
-|   |-- tdd.md              # /tdd - 测试驱动开发
+|-- commands/         # 维护中的斜杠命令兼容层；优先使用 skills/
 |   |-- plan.md             # /plan - 实现规划
-|   |-- e2e.md              # /e2e - 生成端到端测试
 |   |-- code-review.md      # /code-review - 代码质量审查
 |   |-- build-fix.md        # /build-fix - 修复构建错误
+|   |-- quality-gate.md     # /quality-gate - 验证门禁
 |   |-- refactor-clean.md   # /refactor-clean - 清理无效代码
 |   |-- learn.md            # /learn - 会话中提取模式（长文本指南）
 |   |-- learn-eval.md       # /learn-eval - 提取、评估并保存模式（新增）
 |   |-- checkpoint.md       # /checkpoint - 保存验证状态（长文本指南）
-|   |-- verify.md           # /verify - 运行验证循环（长文本指南）
 |   |-- setup-pm.md         # /setup-pm - 配置包管理器
 |   |-- go-review.md        # /go-review - Go 代码审查（新增）
 |   |-- go-test.md          # /go-test - Go TDD 工作流（新增）
@@ -357,13 +355,17 @@ everything-claude-code/
 |   |-- multi-backend.md    # /multi-backend - 后端多服务编排（新增）
 |   |-- multi-frontend.md   # /multi-frontend - 前端多服务编排（新增）
 |   |-- multi-workflow.md   # /multi-workflow - 通用多服务工作流（新增）
-|   |-- orchestrate.md      # /orchestrate - 多智能体协同调度
 |   |-- sessions.md         # /sessions - 会话历史管理
-|   |-- eval.md             # /eval - 按标准评估
 |   |-- test-coverage.md    # /test-coverage - 测试覆盖率分析
 |   |-- update-docs.md      # /update-docs - 更新文档
 |   |-- update-codemaps.md  # /update-codemaps - 更新代码映射
 |   |-- python-review.md    # /python-review - Python 代码审查（新增）
+|-- legacy-command-shims/   # 已退役短命令的按需归档，例如 /tdd 和 /eval
+|   |-- tdd.md              # /tdd - 优先使用 tdd-workflow 技能
+|   |-- e2e.md              # /e2e - 优先使用 e2e-testing 技能
+|   |-- eval.md             # /eval - 优先使用 eval-harness 技能
+|   |-- verify.md           # /verify - 优先使用 verification-loop 技能
+|   |-- orchestrate.md      # /orchestrate - 优先使用 dmux-workflows 或 multi-workflow
 |
 |-- rules/            # 必须遵守的规范（复制到 ~/.claude/rules/）
 |   |-- README.md            # 结构概览与安装指南
@@ -544,7 +546,7 @@ Claude Code v2.1+ 会**按照约定自动加载**已安装插件中的 `hooks/ho
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # 安装插件
-/plugin install everything-claude-code@everything-claude-code
+/plugin install ecc@ecc
 ```
 
 或直接添加到你的 `~/.claude/settings.json`：
@@ -560,7 +562,7 @@ Claude Code v2.1+ 会**按照约定自动加载**已安装插件中的 `hooks/ho
     }
   },
   "enabledPlugins": {
-    "everything-claude-code@everything-claude-code": true
+    "ecc@ecc": true
   }
 }
 ```
@@ -618,9 +620,12 @@ cp -r everything-claude-code/skills/search-first ~/.claude/skills/
 # cp -r everything-claude-code/skills/$s ~/.claude/skills/
 # done
 
-# 可选：迁移期间保留传统斜杠命令兼容
+# 可选：迁移期间保留维护中的斜杠命令兼容
 mkdir -p ~/.claude/commands
 cp everything-claude-code/commands/*.md ~/.claude/commands/
+
+# 已退役短命令位于 legacy-command-shims/commands/。
+# 仅在仍需要 /tdd 等旧名称时，单独复制对应文件。
 ```
 
 #### 将钩子配置添加到 settings.json

agent.yaml

@@ -28,7 +28,6 @@ skills:
   - canary-watch
   - carrier-relationship-management
   - ck
-  - claude-api
   - claude-devfleet
   - click-path-audit
   - clickhouse-io
@@ -144,21 +143,16 @@ skills:
   - visa-doc-translate
   - x-api
 commands:
-  - agent-sort
   - aside
+  - auto-update
   - build-fix
   - checkpoint
-  - claw
   - code-review
-  - context-budget
   - cpp-build
   - cpp-review
   - cpp-test
-  - devfleet
-  - docs
-  - e2e
-  - eval
   - evolve
+  - fastapi-review
   - feature-dev
   - flutter-build
   - flutter-review
@@ -191,12 +185,10 @@ commands:
   - multi-frontend
   - multi-plan
   - multi-workflow
-  - orchestrate
   - plan
   - pm2
   - projects
   - promote
-  - prompt-optimize
   - prp-commit
   - prp-implement
   - prp-plan
@@ -208,7 +200,6 @@ commands:
   - refactor-clean
   - resume-session
   - review-pr
-  - rules-distill
   - rust-build
   - rust-review
   - rust-test
@@ -218,11 +209,9 @@ commands:
   - setup-pm
   - skill-create
   - skill-health
-  - tdd
   - test-coverage
   - update-codemaps
   - update-docs
-  - verify
 tags:
   - agent-harness
   - developer-tools

agents/a11y-architect.md

@@ -3,7 +3,6 @@ name: a11y-architect
 description: Accessibility Architect specializing in WCAG 2.2 compliance for Web and Native platforms. Use PROACTIVELY when designing UI components, establishing design systems, or auditing code for inclusive user experiences.
 model: sonnet
 tools: ["Read", "Write", "Edit", "Bash", "Grep", "Glob"]
-model: opus
 ---
 
 You are a Senior Accessibility Architect. Your goal is to ensure that every digital product is Perceivable, Operable, Understandable, and Robust (POUR) for all users, including those with visual, auditory, motor, or cognitive disabilities.

agents/fastapi-reviewer.md

@@ -0,0 +1,70 @@
+---
+name: fastapi-reviewer
+description: Reviews FastAPI applications for async correctness, dependency injection, Pydantic schemas, security, OpenAPI quality, testing, and production readiness.
+tools: ["Read", "Grep", "Glob", "Bash"]
+model: sonnet
+---
+
+You are a senior FastAPI reviewer focused on production Python APIs.
+
+## Review Scope
+
+- FastAPI app construction, routing, middleware, and exception handling.
+- Pydantic request, update, and response models.
+- Async database and HTTP patterns.
+- Dependency injection for database sessions, auth, pagination, and settings.
+- Authentication, authorization, CORS, rate limits, logging, and secret handling.
+- Test dependency overrides and client setup.
+- OpenAPI metadata and generated docs.
+
+## Out of Scope
+
+- Non-FastAPI frameworks unless they directly interact with the FastAPI app.
+- Broad Python style review already covered by `python-reviewer`.
+- Dependency additions without a concrete problem and maintenance rationale.
+
+## Review Workflow
+
+1. Locate the app entry point, usually `main.py`, `app.py`, or `app/main.py`.
+2. Identify routers, schemas, dependencies, database session setup, and tests.
+3. Run available local checks when safe, such as `pytest`, `ruff`, `mypy`, or `uv run pytest`.
+4. Review the changed files first, then inspect adjacent definitions needed to prove findings.
+5. Report only actionable issues with file and line references when available.
+
+## Finding Priorities
+
+### Critical
+
+- Hardcoded secrets or tokens.
+- SQL built through string interpolation.
+- Passwords, token hashes, or internal auth fields exposed in response models.
+- Auth dependencies that can be bypassed or do not validate expiry/signature.
+
+### High
+
+- Blocking database or HTTP clients inside async routes.
+- Database sessions created inline in handlers instead of dependencies.
+- Test overrides targeting the wrong dependency.
+- `allow_origins=["*"]` combined with credentialed CORS.
+- Missing request validation for write endpoints.
+
+### Medium
+
+- Missing pagination on list endpoints.
+- OpenAPI docs missing response models or error response descriptions.
+- Duplicated route logic that should move into a service/dependency.
+- Missing timeout settings for external HTTP clients.
+
+## Output Format
+
+```text
+[SEVERITY] Short issue title
+File: path/to/file.py:42
+Issue: What is wrong and why it matters.
+Fix: Concrete change to make.
+```
+
+End with:
+
+- `Tests checked:` commands run or why they were skipped.
+- `Residual risk:` anything important that could not be verified.

agents/network-config-reviewer.md

@@ -0,0 +1,97 @@
+---
+name: network-config-reviewer
+description: Reviews router and switch configurations for security, correctness, stale references, risky change-window commands, and missing operational guardrails.
+tools: ["Read", "Grep"]
+model: sonnet
+---
+
+You are a senior network configuration reviewer. You audit proposed or existing
+router and switch configuration and return prioritized findings with evidence.
+
+## Scope
+
+- Cisco IOS and IOS-XE style running configuration.
+- Interface, VLAN, ACL, VTY, AAA, SNMP, NTP, logging, routing, and banner blocks.
+- Proposed change snippets that will be pasted into a change window.
+- Read-only review only. Do not apply configuration or suggest live testing that
+  removes protections.
+
+## Review Workflow
+
+1. Identify the device role, platform, and change intent if they are present.
+2. Parse configuration sections: interfaces, routing, ACLs, line vty, AAA, SNMP,
+   logging, NTP, and banners.
+3. Check the proposed change first, then adjacent existing config needed to prove
+   a finding.
+4. Report only findings with enough evidence to act on.
+5. Separate hard blockers from best-practice improvements.
+
+## Severity Guide
+
+### Critical
+
+- Plaintext or default credentials.
+- `snmp-server community public` or `private`, especially with write access.
+- Telnet-only management or internet-facing VTY access with no source restriction.
+- Proposed destructive commands such as `reload`, `erase`, `format`, broad
+  `no interface`, or removing an entire routing process without rollback context.
+
+### High
+
+- SSH v1, weak enable password usage, missing AAA where the environment expects it.
+- ACLs referenced by interfaces or routing policy but not defined.
+- Route-maps, prefix-lists, or community-lists referenced by BGP but not defined.
+- Subnet overlaps or duplicate interface IPs.
+
+### Medium
+
+- No NTP, timestamps, remote logging, or saved rollback evidence.
+- Management-plane access not limited to a management subnet.
+- Missing descriptions on important uplinks, trunks, or routed links.
+
+### Low
+
+- Naming, comment, and documentation cleanup.
+- Suggested monitoring additions that are not required for the change to be safe.
+
+## Output Format
+
+```text
+## Network Configuration Review: <hostname or unknown device>
+
+### Critical
+[CRITICAL-1] <finding>
+File/section: <line or block>
+Evidence: <specific config snippet or command>
+Risk: <what can break or be exposed>
+Fix: <safe remediation or change-window prerequisite>
+
+### High
+...
+
+### Summary
+| Severity | Count |
+| --- | ---: |
+| Critical | 0 |
+| High | 0 |
+| Medium | 0 |
+| Low | 0 |
+
+Verdict: PASS | WARNING | BLOCK
+Tests checked: <what was inspected>
+Residual risk: <what could not be verified>
+```
+
+Use `BLOCK` for any Critical finding or proposed destructive change without a
+rollback plan. Use `WARNING` for High or Medium findings that do not block a
+maintenance window by themselves. Use `PASS` only when no actionable findings are
+present.
+
+## Safety Rules
+
+- Do not recommend removing ACLs, disabling firewall rules, or opening VTY access
+  as a diagnostic shortcut.
+- Prefer read-only confirmation commands such as `show running-config`,
+  `show ip access-lists`, `show ip route`, `show logging`, and `show interfaces`.
+- If a command changes device state, label it as a proposed fix and require a
+  maintenance window, rollback plan, and verification step.

agents/network-troubleshooter.md

@@ -0,0 +1,119 @@
+---
+name: network-troubleshooter
+description: Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.
+tools: ["Read", "Bash", "Grep"]
+model: sonnet
+---
+
+You are a senior network troubleshooting agent. You diagnose symptoms
+systematically and produce a concise root cause summary with evidence.
+
+## Scope
+
+- Connectivity, packet loss, slow links, DNS failures, route reachability, BGP
+  neighbor state, VLAN reachability, and ACL/firewall symptoms.
+- Router, switch, Linux host, and homelab environments.
+- Read-only diagnosis. Do not apply configuration changes while diagnosing.
+
+## Workflow
+
+1. Characterize the symptom.
+   - What fails?
+   - Who is affected?
+   - When did it start?
+   - What changed recently?
+2. Pick the starting layer, then work downward or upward as evidence requires.
+3. Ask for missing command output only when it changes the diagnosis.
+4. Confirm that the suspected cause explains all observed symptoms.
+5. End with a root cause summary and verification plan.
+
+## Layer Checks
+
+### Layer 1 and 2
+
+Use for link-down, packet loss, CRCs, drops, and VLAN mismatch symptoms.
+
+```text
+show interfaces <interface> status
+show interfaces <interface>
+show vlan brief
+show spanning-tree vlan <id>
+```
+
+Look for down/down state, CRC counters increasing, duplex mismatch, wrong access
+VLAN, blocked spanning-tree state, or trunk VLANs missing from the allowed list.
+
+### Layer 3
+
+Use for gateway, routing, and reachability symptoms.
+
+```text
+show ip interface brief
+show ip route <destination>
+ping <destination> source <interface-or-ip>
+traceroute <destination> source <interface-or-ip>
+```
+
+Look for missing connected routes, wrong next hop, asymmetric routing, stale static
+routes, or a default route that points to the wrong upstream.
+
+### DNS
+
+Use when IP connectivity works but names fail.
+
+```text
+dig @<local-dns> <name>
+dig @<known-good-resolver> <name>
+nslookup <name> <local-dns>
+```
+
+If public DNS works but local DNS fails, focus on the resolver, DHCP DNS option,
+firewall rules to UDP/TCP 53, or local zones.
+
+### Policy And Firewall
+
+Use read-only counters and logs. Do not remove policy to test.
+
+```text
+show ip access-lists <name>
+show running-config interface <interface>
+show logging | include <interface>|ACL|DENY|DROP
+```
+
+If a deny counter increments for the failing flow, propose a narrow allow rule and
+verification step instead of disabling the ACL.
+
+## Output Format
+
+```text
+## Diagnosis: <one-line likely root cause>
+
+Symptom: <reported failure>
+Affected scope: <host, VLAN, subnet, site, or unknown>
+Layer: <where the fault was found>
+
+Evidence:
+- `<command>` -> <what it proved>
+- `<command>` -> <what it ruled out>
+
+Root cause:
+<specific explanation>
+
+Recommended fix:
+1. <safe action or config change to schedule>
+2. <rollback or maintenance note if relevant>
+
+Verification:
+- `<command>` should show <expected result>
+
+Residual risk:
+<what still needs device access, logs, or timing evidence>
+```
+
+## Guardrails
+
+- Prefer evidence over guesses.
+- Never recommend temporarily removing ACLs, firewall rules, authentication, or
+  management-plane restrictions.
+- If a live command changes state, label it clearly as a remediation step, not a
+  diagnostic command.

agents/swift-build-resolver.md

@@ -0,0 +1,161 @@
+---
+name: swift-build-resolver
+description: Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
+tools: ["Read", "Write", "Edit", "Bash", "Grep", "Glob"]
+model: sonnet
+---
+
+# Swift Build Error Resolver
+
+You are an expert Swift build error resolution specialist. Your mission is to fix Swift compilation errors, Xcode build failures, and dependency problems with **minimal, surgical changes**.
+
+## Core Responsibilities
+
+1. Diagnose `swift build` / `xcodebuild` errors
+2. Fix type checker and protocol conformance errors
+3. Resolve Swift Concurrency and `Sendable` issues
+4. Handle SPM dependency and version resolution failures
+5. Fix Xcode project configuration and code signing issues
+
+## Diagnostic Commands
+
+Run these in order:
+
+```bash
+swift build 2>&1
+if command -v swiftlint >/dev/null 2>&1; then swiftlint lint --quiet 2>&1; else echo "[info] swiftlint not installed - skipping lint"; fi
+swift package resolve 2>&1
+swift package show-dependencies 2>&1
+swift test 2>&1
+```
+
+For Xcode projects:
+
+```bash
+xcodebuild -list 2>&1
+xcrun simctl list devices available 2>&1 | head -20   # find an available simulator
+xcodebuild -scheme <Scheme> -destination 'generic/platform=iOS Simulator' build 2>&1 | tail -50
+xcodebuild -showBuildSettings 2>&1 | grep -E 'SWIFT_VERSION|CODE_SIGN|PRODUCT_BUNDLE_IDENTIFIER'
+```
+
+## Resolution Workflow
+
+```text
+1. swift build           -> Parse error message and error code
+2. Read affected file    -> Understand type and protocol context
+3. Apply minimal fix     -> Only what's needed
+4. swift build           -> Verify fix
+5. swiftlint lint        -> Check for warnings (if swiftlint is installed)
+6. swift test            -> Ensure nothing broke
+```
+
+## Common Fix Patterns
+
+| Error | Cause | Fix |
+|-------|-------|-----|
+| `cannot find type 'X' in scope` | Missing import or typo | Add `import Module` or fix name |
+| `value of type 'X' has no member 'Y'` | Wrong type or missing extension | Fix type or add missing method |
+| `cannot convert value of type 'X' to expected type 'Y'` | Type mismatch | Add conversion, cast, or fix type annotation |
+| `type 'X' does not conform to protocol 'Y'` | Missing required members | Implement missing protocol requirements |
+| `missing return in closure expected to return 'X'` | Incomplete closure body | Add explicit return statement |
+| `expression is 'async' but is not marked with 'await'` | Missing `await` | Add `await` keyword |
+| `non-sendable type 'X' passed in implicitly asynchronous call` | Sendable violation | Add `Sendable` conformance or restructure |
+| `actor-isolated property cannot be referenced from non-isolated context` | Actor isolation mismatch | Add `await`, mark caller as `async`, or use `nonisolated` |
+| `reference to captured var 'X' in concurrently-executing code` | Captured mutable state | Use `let` copy before closure or actor |
+| `ambiguous use of 'X'` | Multiple matching declarations | Use fully qualified name or explicit type annotation |
+| `circular reference` | Recursive type or protocol | Break cycle with indirect enum or protocol |
+| `cannot assign to property: 'X' is a 'let' constant` | Mutating immutable value | Change `let` to `var` or restructure |
+| `initializer requires that 'X' conform to 'Decodable'` | Missing Codable conformance | Add `Codable` conformance or custom init |
+| `@MainActor function cannot be called from non-isolated context` | Main actor isolation | Add `await` and make caller `async`, or use `MainActor.run {}` |
+
+## SPM Troubleshooting
+
+```bash
+# Check resolved dependency versions
+cat Package.resolved | head -40
+
+# Clear package caches
+swift package reset
+swift package resolve
+
+# Show full dependency tree
+swift package show-dependencies --format json
+
+# Update a specific dependency
+swift package update <PackageName>
+
+# Check for version conflicts
+swift package resolve 2>&1 | grep -i "conflict\\|error"
+
+# Verify Package.swift syntax
+swift package dump-package
+```
+
+## Xcode Build Troubleshooting
+
+```bash
+# Clean build folder
+xcodebuild clean -scheme <Scheme>
+
+# List available schemes and destinations
+xcodebuild -list
+xcrun simctl list devices available
+
+# Check Swift version
+xcrun --find swift
+swift --version
+grep 'swift-tools-version' Package.swift
+
+# Code signing issues
+security find-identity -v -p codesigning
+xcodebuild -showBuildSettings | grep CODE_SIGN
+
+# Module map / framework issues
+xcodebuild -scheme <Scheme> build 2>&1 | grep -E 'module|framework|import'
+```
+
+## Swift Version and Toolchain Issues
+
+```bash
+# Check active toolchain
+xcrun --find swift
+swift --version
+
+# Check swift-tools-version in Package.swift
+head -1 Package.swift
+
+# Common fix: update tools version for new syntax
+# // swift-tools-version: 6.0  (requires Xcode 16+)
+```
+
+## Key Principles
+
+- **Surgical fixes only** - don't refactor, just fix the error
+- **Never** add `// swiftlint:disable` without explicit approval
+- **Never** use force unwrap (`!`) to silence optionals - handle properly with `guard let` or `if let`
+- **Never** use `@unchecked Sendable` to silence concurrency errors without verifying thread safety
+- **Always** run `swift build` after every fix attempt
+- Fix root cause over suppressing symptoms
+- Prefer the simplest fix that preserves the original intent
+
+## Stop Conditions
+
+Stop and report if:
+- Same error persists after 3 fix attempts
+- Fix introduces more errors than it resolves
+- Error requires architectural changes beyond scope
+- Concurrency error requires redesigning actor isolation model
+- Build failure is caused by missing provisioning profile or certificate (user action required)
+
+## Output Format
+
+```text
+[FIXED] Sources/App/Services/UserService.swift:42
+Error: type 'UserService' does not conform to protocol 'Sendable'
+Fix: Converted mutable properties to let constants and added Sendable conformance
+Remaining errors: 3
+```
+
+Final: `Build Status: SUCCESS/FAILED | Errors Fixed: N | Files Modified: list`
+
+For detailed Swift patterns and rules, see rules: `swift/coding-style`, `swift/patterns`, `swift/security`. See also skill: `swift-concurrency-6-2`, `swift-actor-persistence`.

agents/swift-reviewer.md

@@ -0,0 +1,107 @@
+---
+name: swift-reviewer
+description: Expert Swift code reviewer specializing in protocol-oriented design, value semantics, ARC memory management, Swift Concurrency, and idiomatic patterns. Use for all Swift code changes. MUST BE USED for Swift projects.
+tools: ["Read", "Grep", "Glob", "Bash"]
+model: sonnet
+---
+
+You are a senior Swift code reviewer ensuring high standards of safety, idiomatic patterns, and performance.
+
+When invoked:
+1. Run `swift build`, `swiftlint lint --quiet` (if available), and `swift test` - if any fail, stop and report
+2. Run `git diff HEAD~1 -- '*.swift'` (or `git diff main...HEAD -- '*.swift'` for PR review) to see recent Swift file changes
+3. Focus on modified `.swift` files
+4. If the project has CI or merge requirements, note that review assumes a green CI and resolved merge conflicts where applicable; call out if the diff suggests otherwise.
+5. Begin review
+
+## Review Priorities
+
+### CRITICAL - Safety
+
+- **Force unwrapping**: `value!` in production code paths - use `guard let`, `if let`, or `??`
+- **Force try**: `try!` without justification - use `do/catch` or propagate with `throws`
+- **Force cast**: `as!` without a preceding type check - use `as?` with conditional binding
+- **Hardcoded secrets**: API keys, passwords, tokens in source - use Keychain or environment variables
+- **UserDefaults for secrets**: Sensitive data in `UserDefaults` - use Keychain Services
+- **ATS disabled**: App Transport Security exceptions without justification
+- **SQL/command injection**: String interpolation in queries or shell commands - use parameterized queries
+- **Path traversal**: User-controlled paths without validation and prefix check
+- **Insecure deserialization**: Decoding untrusted data without validation or size limits
+
+### CRITICAL - Error Handling
+
+- **Silenced errors**: Empty `catch {}` blocks or `try?` discarding meaningful errors
+- **Missing error context**: Rethrowing without wrapping in a domain-specific error
+- **`fatalError()` for recoverable conditions**: Use `throw` for errors that callers can handle
+- **`assert` for required invariants**: `assert` is stripped in release builds (debug-only) - use `precondition` when the check must hold in release, or `throw` for public API boundaries
+- **`precondition` / `fatalError` in library code**: `precondition` crashes in both debug and release; `fatalError` crashes unconditionally in all builds - use `throw` for recoverable errors at public API boundaries
+
+### HIGH - Concurrency
+
+- **Data races**: Mutable shared state without actor isolation or synchronization
+- **`@Sendable` violations**: Non-`Sendable` types crossing isolation boundaries
+- **Blocking the main actor**: Synchronous I/O or `Thread.sleep` on `@MainActor` - use `Task.sleep` and async I/O
+- **Unstructured `Task {}` without cancellation**: Fire-and-forget tasks leaking - use structured concurrency (`async let`, `TaskGroup`)
+- **Actor reentrancy issues**: Assumptions about state consistency across `await` suspension points
+- **Missing `@MainActor`**: UI updates performed off the main actor
+
+### HIGH - Memory Management
+
+- **Strong reference cycles**: Closures capturing `self` strongly in long-lived contexts - use `[weak self]` or `[unowned self]`
+- **Delegates as strong references**: Delegate properties without `weak` - causes retain cycles
+- **Closure capture lists missing**: Escaping closures without explicit capture semantics
+- **Large value type copies**: Oversized structs copied on every assignment - consider `class` or `Cow`-like patterns
+
+### HIGH - Code Quality
+
+- **Large functions**: Over 50 lines
+- **Deep nesting**: More than 4 levels
+- **Wildcard switch on evolving enums**: `default:` hiding new cases - use `@unknown default`
+- **Dead code**: Unused functions, imports, or variables
+- **Non-exhaustive matching**: Catch-all where explicit handling is needed
+
+### HIGH - Protocol-Oriented Design
+
+- **Class inheritance where protocols suffice**: Prefer protocol conformance with default extensions
+- **`Any` / `AnyObject` abuse**: Use constrained generics or `any Protocol` / `some Protocol`
+- **Missing protocol conformance**: Types that should conform to `Equatable`, `Hashable`, `Codable`, or `Sendable`
+- **Existential over generic**: `any Protocol` parameter when `some Protocol` or generic constraint is more efficient
+
+### MEDIUM - Performance
+
+- **Unnecessary allocation in hot paths**: Creating objects inside tight loops
+- **Missing `reserveCapacity`**: Growing arrays when final size is known
+- **String interpolation in loops**: Repeated `String` allocation - use `append` or preallocate
+- **Unnecessary `@objc` bridging**: Swift-to-Objective-C overhead where pure Swift suffices
+- **N+1 queries**: Database or network calls inside loops - batch operations
+
+### MEDIUM - Best Practices
+
+- **`var` when `let` suffices**: Prefer immutable bindings
+- **`class` when `struct` suffices**: Prefer value types for data models
+- **`print()` in production code**: Use `os.Logger` or structured logging
+- **Missing access control**: Types and members defaulting to `internal` when `private` or `fileprivate` is appropriate
+- **SwiftLint warnings unaddressed**: Suppressed with `// swiftlint:disable` without justification
+- **Public API without documentation**: `public` items missing `///` doc comments
+- **Magic numbers/strings**: Use named constants or enums
+- **Stringly-typed APIs**: Use enums or dedicated types instead of raw strings
+
+## Diagnostic Commands
+
+```bash
+swift build
+if command -v swiftlint >/dev/null 2>&1; then swiftlint lint --quiet; else echo "[info] swiftlint not installed - skipping lint (install via 'brew install swiftlint')"; fi
+swift test
+swift package resolve
+if command -v swift-format >/dev/null 2>&1; then swift-format lint -r . 2>&1 | head -30; else echo "[info] swift-format not installed - skipping format check"; fi
+```
+
+## Approval Criteria
+
+- **Approve**: No CRITICAL or HIGH issues
+- **Warning**: MEDIUM issues only
+- **Block**: CRITICAL or HIGH issues found
+
+For detailed Swift patterns and rules, see rules: `swift/coding-style`, `swift/patterns`, `swift/security`, `swift/testing`. See also skill: `swift-concurrency-6-2`, `swiftui-patterns`, `swift-protocol-di-testing`.
+
+Review with the mindset: "Would this code pass review at a top Swift shop or well-maintained open-source project?"

commands/auto-update.md

@@ -0,0 +1,28 @@
+---
+description: Pull the latest ECC repo changes and reinstall the current managed targets.
+disable-model-invocation: true
+---
+
+# Auto Update
+
+Update ECC from its upstream repo and regenerate the current context's managed install using the original install-state request.
+
+## Usage
+
+```bash
+# Preview the update without mutating anything
+ECC_ROOT="${CLAUDE_PLUGIN_ROOT:-$(node -e "var r=(()=>{var e=process.env.CLAUDE_PLUGIN_ROOT;if(e&&e.trim())return e.trim();var p=require('path'),f=require('fs'),h=require('os').homedir(),d=p.join(h,'.claude'),q=p.join('scripts','lib','utils.js');if(f.existsSync(p.join(d,q)))return d;for(var s of [['ecc'],['ecc@ecc'],['marketplace','ecc'],['everything-claude-code'],['everything-claude-code@everything-claude-code'],['marketplace','everything-claude-code']]){var l=p.join(d,'plugins',...s);if(f.existsSync(p.join(l,q)))return l}try{for(var g of ['ecc','everything-claude-code']){var b=p.join(d,'plugins','cache',g);for(var o of f.readdirSync(b,{withFileTypes:true})){if(!o.isDirectory())continue;for(var v of f.readdirSync(p.join(b,o.name),{withFileTypes:true})){if(!v.isDirectory())continue;var c=p.join(b,o.name,v.name);if(f.existsSync(p.join(c,q)))return c}}}}catch(x){}return d})();console.log(r)")}"
+node "$ECC_ROOT/scripts/auto-update.js" --dry-run
+
+# Update only Cursor-managed files in the current project
+node "$ECC_ROOT/scripts/auto-update.js" --target cursor
+
+# Override the ECC repo root explicitly
+node "$ECC_ROOT/scripts/auto-update.js" --repo-root /path/to/everything-claude-code
+```
+
+## Notes
+
+- This command uses the recorded install-state request and reruns `install-apply.js` after pulling the latest repo changes.
+- Reinstall is intentional: it handles upstream renames and deletions that `repair.js` cannot safely reconstruct from stale operations alone.
+- Use `--dry-run` first if you want to see the reconstructed reinstall plan before mutating anything.

commands/build-fix.md

@@ -1,3 +1,7 @@
+---
+description: Detect the project build system and incrementally fix build/type errors with minimal safe changes.
+---
+
 # Build and Fix
 
 Incrementally fix build and type errors with minimal, safe changes.

commands/checkpoint.md

@@ -1,3 +1,7 @@
+---
+description: Create, verify, or list workflow checkpoints after running verification checks.
+---
+
 # Checkpoint Command
 
 Create or verify a checkpoint in your workflow.

commands/cpp-build.md

@@ -165,7 +165,7 @@ The agent will stop and report if:
 
 - `/cpp-test` - Run tests after build succeeds
 - `/cpp-review` - Review code quality
-- `/verify` - Full verification loop
+- `verification-loop` skill - Full verification loop
 
 ## Related
 

commands/cpp-test.md

@@ -243,7 +243,7 @@ genhtml coverage.info --output-directory coverage_html
 
 - `/cpp-build` - Fix build errors
 - `/cpp-review` - Review code after implementation
-- `/verify` - Run full verification loop
+- `verification-loop` skill - Run full verification loop
 
 ## Related
 

commands/fastapi-review.md

@@ -0,0 +1,39 @@
+---
+description: Review a FastAPI application for architecture, async correctness, dependency injection, Pydantic schemas, security, performance, and testability.
+---
+
+# FastAPI Review
+
+Invoke the `fastapi-reviewer` agent for a focused FastAPI review.
+
+## Usage
+
+```text
+/fastapi-review [file-or-directory]
+```
+
+## Review Areas
+
+- App factory, router boundaries, middleware, and exception handlers.
+- Pydantic request and response schema separation.
+- Dependency injection for database sessions, auth, pagination, and settings.
+- Async database and external HTTP patterns.
+- CORS, auth, rate limits, logging, and secret handling.
+- OpenAPI metadata and documented response models.
+- Test client setup and dependency overrides.
+
+## Expected Output
+
+```text
+[SEVERITY] Short issue title
+File: path/to/file.py:42
+Issue: What is wrong and why it matters.
+Fix: Concrete change to make.
+```
+
+## Related
+
+- Agent: `fastapi-reviewer`
+- Skill: `fastapi-patterns`
+- Command: `/python-review`
+- Skill: `security-scan`

commands/flutter-build.md

@@ -156,7 +156,7 @@ The agent will stop and report if:
 
 - `/flutter-test` — Run tests after build succeeds
 - `/flutter-review` — Review code quality
-- `/verify` — Full verification loop
+- `verification-loop` skill — Full verification loop
 
 ## Related
 

commands/flutter-test.md

@@ -134,7 +134,7 @@ Test Status: PASS ✓
 
 - `/flutter-build` — Fix build errors before running tests
 - `/flutter-review` — Review code after tests pass
-- `/tdd` — Test-driven development workflow
+- `tdd-workflow` skill — Test-driven development workflow
 
 ## Related
 

commands/gan-build.md

@@ -1,3 +1,7 @@
+---
+description: Run a generator/evaluator build loop for implementation tasks with bounded iterations and scoring.
+---
+
 Parse the following from $ARGUMENTS:
 1. `brief` — the user's one-line description of what to build
 2. `--max-iterations N` — (optional, default 15) maximum generator-evaluator cycles

commands/gan-design.md

@@ -1,3 +1,7 @@
+---
+description: Run a generator/evaluator design loop for frontend or visual work with bounded iterations and scoring.
+---
+
 Parse the following from $ARGUMENTS:
 1. `brief` — the user's description of the design to create
 2. `--max-iterations N` — (optional, default 10) maximum design-evaluate cycles

commands/go-build.md

@@ -175,7 +175,7 @@ The agent will stop and report if:
 
 - `/go-test` - Run tests after build succeeds
 - `/go-review` - Review code quality
-- `/verify` - Full verification loop
+- `verification-loop` skill - Full verification loop
 
 ## Related
 

commands/go-test.md

@@ -260,7 +260,7 @@ go test -race -cover ./...
 
 - `/go-build` - Fix build errors
 - `/go-review` - Review code after implementation
-- `/verify` - Run full verification loop
+- `verification-loop` skill - Run full verification loop
 
 ## Related
 

commands/harness-audit.md

@@ -1,3 +1,7 @@
+---
+description: Run a deterministic repository harness audit and return a prioritized scorecard.
+---
+
 # Harness Audit Command
 
 Run a deterministic repository harness audit and return a prioritized scorecard.

commands/jira.md

@@ -55,7 +55,7 @@ Dependencies:
 
 Recommended Next Steps:
 - /plan to create implementation plan
-- /tdd to implement with tests first
+- `tdd-workflow` skill to implement with tests first
 ```
 
 ### `/jira comment <TICKET-KEY>`
@@ -95,7 +95,7 @@ If credentials are missing, stop and direct the user to set them up.
 
 After analyzing a ticket:
 - Use `/plan` to create an implementation plan from the requirements
-- Use `/tdd` to implement with test-driven development
+- Use the `tdd-workflow` skill to implement with test-driven development
 - Use `/code-review` after implementation
 - Use `/jira comment` to post progress back to the ticket
 - Use `/jira transition` to move the ticket when work is complete

commands/kotlin-build.md

@@ -166,7 +166,7 @@ The agent will stop and report if:
 
 - `/kotlin-test` - Run tests after build succeeds
 - `/kotlin-review` - Review code quality
-- `/verify` - Full verification loop
+- `verification-loop` skill - Full verification loop
 
 ## Related
 

commands/kotlin-test.md

@@ -304,7 +304,7 @@ open build/reports/kover/html/index.html
 
 - `/kotlin-build` - Fix build errors
 - `/kotlin-review` - Review code after implementation
-- `/verify` - Run full verification loop
+- `verification-loop` skill - Run full verification loop
 
 ## Related
 

commands/learn.md

@@ -1,3 +1,7 @@
+---
+description: Extract reusable patterns from the current session and save them as candidate skills or guidance.
+---
+
 # /learn - Extract Reusable Patterns
 
 Analyze the current session and extract any patterns worth saving as skills.

commands/loop-start.md

@@ -1,3 +1,7 @@
+---
+description: Start a managed autonomous loop pattern with safety defaults and explicit stop conditions.
+---
+
 # Loop Start Command
 
 Start a managed autonomous loop pattern with safety defaults.

commands/loop-status.md

@@ -1,7 +1,23 @@
+---
+description: Inspect active loop state, progress, failure signals, and recommended intervention.
+---
+
 # Loop Status Command
 
 Inspect active loop state, progress, and failure signals.
 
+This slash command can only run after the current session dequeues it. If you
+need to inspect a wedged or sibling session, run the packaged CLI from another
+terminal:
+
+```bash
+npx --package ecc-universal ecc loop-status --json
+```
+
+The CLI scans local Claude transcript JSONL files under
+`~/.claude/projects/**` and reports stale `ScheduleWakeup` calls or `Bash`
+tool calls that have no matching `tool_result`.
+
 ## Usage
 
 `/loop-status [--watch]`
@@ -14,9 +30,46 @@ Inspect active loop state, progress, and failure signals.
 - estimated time/cost drift
 - recommended intervention (continue/pause/stop)
 
+## Cross-Session CLI
+
+- `ecc loop-status --json` emits machine-readable status for recent local
+  Claude transcripts.
+- `ecc loop-status --home <dir>` scans a different home directory when
+  inspecting another local profile or mounted workspace.
+- `ecc loop-status --transcript <session.jsonl>` inspects one transcript
+  directly.
+- `ecc loop-status --bash-timeout-seconds 1800` adjusts the stale Bash
+  threshold.
+- `ecc loop-status --exit-code` exits `2` when stale loop or tool signals are
+  found, or `1` when transcripts cannot be scanned.
+- `--exit-code` with `--watch` requires `--watch-count` so watchdog scripts do
+  not wait forever for a process exit.
+- `ecc loop-status --watch` refreshes status until interrupted.
+- `ecc loop-status --watch --watch-count 3 --exit-code` refreshes a bounded
+  number of times, then exits with the highest status seen.
+- `ecc loop-status --watch --watch-count 3` emits a bounded watch stream for
+  scripts and handoffs.
+- `ecc loop-status --watch --write-dir ~/.claude/loops` maintains
+  `index.json` and per-session JSON snapshots for sibling terminals or
+  watchdog scripts.
+
 ## Watch Mode
 
-When `--watch` is present, refresh status periodically and surface state changes.
+When `--watch` is present, refresh status periodically. With `--json`, each
+refresh is emitted as one JSON object per line so another terminal or script can
+consume the stream.
+
+## Snapshot Files
+
+Use `--write-dir <dir>` when a separate process needs to inspect loop state
+without waiting for the current Claude session to dequeue `/loop-status`. The
+CLI writes:
+
+- `index.json` with one row per inspected session.
+- `<session-id>.json` with the full status payload for that session.
+
+These files are snapshots of local transcript analysis. They do not control or
+timeout Claude Code runtime tool calls.
 
 ## Arguments
 

commands/model-route.md

@@ -1,3 +1,7 @@
+---
+description: Recommend the best model tier for the current task based on complexity, risk, and budget.
+---
+
 # Model Route Command
 
 Recommend the best model tier for the current task by complexity and budget.

commands/multi-backend.md

@@ -1,3 +1,7 @@
+---
+description: Run a backend-focused multi-model workflow for APIs, algorithms, data, and business logic.
+---
+
 # Backend - Backend-Focused Development
 
 Backend-focused workflow (Research → Ideation → Plan → Execute → Optimize → Review), Codex-led.

commands/multi-execute.md

@@ -1,3 +1,7 @@
+---
+description: Execute a multi-model implementation plan while preserving Claude as the only filesystem writer.
+---
+
 # Execute - Multi-Model Collaborative Execution
 
 Multi-model collaborative execution - Get prototype from plan → Claude refactors and implements → Multi-model audit and delivery.

commands/multi-frontend.md

@@ -1,3 +1,7 @@
+---
+description: Run a frontend-focused multi-model workflow for components, layouts, animation, and UI polish.
+---
+
 # Frontend - Frontend-Focused Development
 
 Frontend-focused workflow (Research → Ideation → Plan → Execute → Optimize → Review), Gemini-led.

commands/multi-plan.md

@@ -1,3 +1,7 @@
+---
+description: Create a multi-model implementation plan without modifying production code.
+---
+
 # Plan - Multi-Model Collaborative Planning
 
 Multi-model collaborative planning - Context retrieval + Dual-model analysis → Generate step-by-step implementation plan.

commands/multi-workflow.md

@@ -1,3 +1,7 @@
+---
+description: Run a full multi-model development workflow with research, planning, execution, optimization, and review.
+---
+
 # Workflow - Multi-Model Collaborative Development
 
 Multi-model collaborative development workflow (Research → Ideation → Plan → Execute → Optimize → Review), with intelligent routing: Frontend → Gemini, Backend → Codex.

commands/plan.md

@@ -4,7 +4,9 @@ description: Restate requirements, assess risks, and create step-by-step impleme
 
 # Plan Command
 
-This command invokes the **planner** agent to create a comprehensive implementation plan before writing any code.
+This command creates a comprehensive implementation plan before writing any code.
+
+Run inline by default. Do not call the Task tool or any subagent by default. This keeps `/plan` usable from plugin installs that ship commands without agent files.
 
 ## What This Command Does
 
@@ -24,7 +26,7 @@ Use `/plan` when:
 
 ## How It Works
 
-The planner agent will:
+The assistant will:
 
 1. **Analyze the request** and restate requirements in clear terms
 2. **Break down into phases** with specific, actionable steps
@@ -38,7 +40,7 @@ The planner agent will:
 ```
 User: /plan I need to add real-time notifications when markets resolve
 
-Agent (planner):
+Assistant:
 # Implementation Plan: Real-Time Market Resolution Notifications
 
 ## Requirements Restatement
@@ -93,7 +95,7 @@ Agent (planner):
 
 ## Important Notes
 
-**CRITICAL**: The planner agent will **NOT** write any code until you explicitly confirm the plan with "yes" or "proceed" or similar affirmative response.
+**CRITICAL**: This command will **NOT** write any code until you explicitly confirm the plan with "yes" or "proceed" or similar affirmative response.
 
 If you want changes, respond with:
 - "modify: [your changes]"
@@ -103,15 +105,17 @@ If you want changes, respond with:
 ## Integration with Other Commands
 
 After planning:
-- Use `/tdd` to implement with test-driven development
+- Use the `tdd-workflow` skill to implement with test-driven development
 - Use `/build-fix` if build errors occur
 - Use `/code-review` to review completed implementation
 
 > **Need deeper planning?** Use `/prp-plan` for artifact-producing planning with PRD integration, codebase analysis, and pattern extraction. Use `/prp-implement` to execute those plans with rigorous validation loops.
 
-## Related Agents
+## Optional Planner Agent
 
-This command invokes the `planner` agent provided by ECC.
+ECC also provides a `planner` agent for manual installs that include agent files. Use it only when the local runtime already exposes that subagent and the user explicitly asks you to delegate planning.
+
+If the `planner` subagent is unavailable, continue planning inline instead of surfacing an "Agent type 'planner' not found" error.
 
 For manual installs, the source file lives at:
 `agents/planner.md`

commands/pm2.md

@@ -1,3 +1,7 @@
+---
+description: Analyze a project and generate PM2 service commands for detected frontend, backend, or database services.
+---
+
 # PM2 Init
 
 Auto-analyze project and generate PM2 service commands.

commands/python-review.md

@@ -171,7 +171,7 @@ Run: `black app/routes/user.py app/services/auth.py`
 
 ## Integration with Other Commands
 
-- Use `/tdd` first to ensure tests pass
+- Use the `tdd-workflow` skill first to ensure tests pass
 - Use `/code-review` for non-Python specific concerns
 - Use `/python-review` before committing
 - Use `/build-fix` if static analysis tools fail

commands/quality-gate.md

@@ -1,3 +1,7 @@
+---
+description: Run the ECC quality pipeline for a file or project scope and report remediation steps.
+---
+
 # Quality Gate Command
 
 Run the ECC quality pipeline on demand for a file or project scope.

commands/refactor-clean.md

@@ -1,3 +1,7 @@
+---
+description: Safely identify and remove dead code with verification after each change.
+---
+
 # Refactor Clean
 
 Safely identify and remove dead code with test verification at every step.

commands/rust-build.md

@@ -179,7 +179,7 @@ The agent will stop and report if:
 
 - `/rust-test` - Run tests after build succeeds
 - `/rust-review` - Review code quality
-- `/verify` - Full verification loop
+- `verification-loop` skill - Full verification loop
 
 ## Related
 

commands/rust-test.md

@@ -300,7 +300,7 @@ cargo test --no-fail-fast
 
 - `/rust-build` - Fix build errors
 - `/rust-review` - Review code after implementation
-- `/verify` - Run full verification loop
+- `verification-loop` skill - Run full verification loop
 
 ## Related
 

commands/test-coverage.md

@@ -1,3 +1,7 @@
+---
+description: Analyze coverage, identify gaps, and generate missing tests toward the target threshold.
+---
+
 # Test Coverage
 
 Analyze test coverage, identify gaps, and generate missing tests to reach 80%+ coverage.

commands/update-codemaps.md

@@ -1,3 +1,7 @@
+---
+description: Scan project structure and generate token-lean architecture codemaps.
+---
+
 # Update Codemaps
 
 Analyze the codebase structure and generate token-lean architecture documentation.

commands/update-docs.md

@@ -1,3 +1,7 @@
+---
+description: Sync documentation from source-of-truth files such as scripts, schemas, routes, and exports.
+---
+
 # Update Documentation
 
 Sync documentation with the codebase, generating from source-of-truth files.

docs/ARCHITECTURE-IMPROVEMENTS.md

@@ -110,7 +110,7 @@ This document captures architect-level improvements for the Everything Claude Co
 
 ### 5.1 Hook Runtime Consistency
 
-**Issue:** Most hooks invoke Node scripts via `run-with-flags.js`; one path uses `run-with-flags-shell.sh` + `observe.sh`. The mixed runtime is documented but could be simplified over time.
+**Issue:** Hooks should keep a consistent Node-mode dispatch surface. Continuous-learning observation now dispatches through `run-with-flags.js` and `observe-runner.js`, which delegates to the existing `observe.sh` implementation without exposing a shell-mode hook entry.
 
 **Recommendation:**
 

docs/HERMES-SETUP.md

@@ -83,14 +83,27 @@ These stay local and should be configured per operator:
 ## Suggested Bring-Up Order
 
 0. Run `ecc migrate audit --source ~/.hermes` first to inventory the legacy workspace and see which parts already map onto ECC2.
-0.5. Generate and review artifacts with `ecc migrate plan` / `ecc migrate scaffold`, scaffold reusable legacy skills with `ecc migrate import-skills --output-dir migration-artifacts/skills`, scaffold legacy tool translation templates with `ecc migrate import-tools --output-dir migration-artifacts/tools`, scaffold legacy bridge plugins with `ecc migrate import-plugins --output-dir migration-artifacts/plugins`, preview recurring jobs with `ecc migrate import-schedules --dry-run`, preview gateway dispatch with `ecc migrate import-remote --dry-run`, preview safe env/service context with `ecc migrate import-env --dry-run`, then import sanitized workspace memory with `ecc migrate import-memory`.
-1. Install ECC and verify the baseline harness setup.
+0.5. Plan and scaffold migration artifacts before importing anything:
+   - generate reviewable plans with `ecc migrate plan` and `ecc migrate scaffold`
+   - scaffold reusable legacy skills with `ecc migrate import-skills --output-dir migration-artifacts/skills`
+   - scaffold tool translation templates with `ecc migrate import-tools --output-dir migration-artifacts/tools`
+   - scaffold bridge plugin templates with `ecc migrate import-plugins --output-dir migration-artifacts/plugins`
+   - preview recurring jobs with `ecc migrate import-schedules --dry-run`
+   - preview gateway dispatch with `ecc migrate import-remote --dry-run`
+   - preview safe env/service context with `ecc migrate import-env --dry-run`
+   - import sanitized workspace memory with `ecc migrate import-memory`
+1. Install ECC and verify the baseline harness setup with `node tests/run-all.js`; the expected result is a zero-failure test summary.
 2. Install Hermes and point it at ECC-imported skills.
 3. Register the MCP servers you actually use every day.
 4. Authenticate Google Drive first, then GitHub, then distribution channels.
 5. Start with a small cron surface: readiness check, content accountability, inbox triage, revenue monitor.
 6. Only then add heavier personal workflows like health, relationship graphing, or outbound sequencing.
 
+## Related Docs
+
+- [Hermes/OpenClaw migration guide](HERMES-OPENCLAW-MIGRATION.md)
+- [Cross-harness architecture](architecture/cross-harness.md)
+
 ## Why Hermes x ECC
 
 This stack is useful when you want:

docs/JOYCODE-GUIDE.md

@@ -0,0 +1,55 @@
+# JoyCode Adapter Guide
+
+JoyCode can consume ECC through the selective installer. The adapter installs shared ECC commands, agents, skills, and flattened rules into a project-local `.joycode/` directory.
+
+## Install
+
+Preview the install plan:
+
+```bash
+node scripts/install-plan.js --target joycode --profile full
+```
+
+Apply it to the current project:
+
+```bash
+node scripts/install-apply.js --target joycode --profile full
+```
+
+For a smaller install, select modules explicitly:
+
+```bash
+node scripts/install-apply.js --target joycode --modules rules-core,commands-core,workflow-quality
+```
+
+## Layout
+
+The project adapter writes managed files under:
+
+```text
+.joycode/
+  agents/
+  commands/
+  rules/
+  skills/
+  mcp-configs/
+  scripts/
+  ecc-install-state.json
+```
+
+Rules are flattened into namespaced filenames so a JoyCode project does not receive nested rule directories such as `rules/common/coding-style.md`. Commands, agents, and skills keep the same structure they use elsewhere in ECC.
+The full profile also includes shared MCP and setup helper files that other ECC project-local adapters use.
+
+## Uninstall
+
+Use ECC's managed uninstall path instead of deleting files by hand:
+
+```bash
+node scripts/uninstall.js --target joycode
+```
+
+The uninstall command reads `.joycode/ecc-install-state.json` and removes only files that ECC installed. User-created JoyCode files are preserved.
+
+## Source PR
+
+This adapter salvages the useful project-local JoyCode intent from stale PR #1429 while replacing the standalone shell installer with ECC's current install-state and uninstall machinery.

docs/QWEN-GUIDE.md

@@ -0,0 +1,54 @@
+# Qwen CLI Adapter Guide
+
+ECC can install its managed command, agent, skill, rule, and MCP surfaces into the Qwen CLI home directory.
+
+## Install
+
+From the ECC repository root:
+
+```bash
+./install.sh --target qwen --profile minimal
+```
+
+Preview a larger install before copying files:
+
+```bash
+./install.sh --target qwen --profile full --dry-run
+```
+
+The Qwen adapter writes into `~/.qwen/` and records managed file ownership in `~/.qwen/ecc-install-state.json`.
+
+## Installed Layout
+
+The managed install can populate:
+
+```text
+~/.qwen/
+  QWEN.md
+  agents/
+  commands/
+  mcp-configs/
+  rules/
+  skills/
+  ecc-install-state.json
+```
+
+The installer preserves the source layout for rules, so language rule sets stay under paths such as `~/.qwen/rules/common/` and `~/.qwen/rules/typescript/`.
+
+## Updating
+
+Rerun the same install command after pulling ECC updates. The installer uses the install-state file to update ECC-managed files without claiming unrelated user files in `~/.qwen/`.
+
+## Uninstalling
+
+Use the managed uninstall path rather than deleting the whole Qwen directory:
+
+```bash
+node scripts/uninstall.js --target qwen
+```
+
+That removes files recorded in `~/.qwen/ecc-install-state.json` and leaves unrelated Qwen configuration alone.
+
+## Scope
+
+This target is intentionally narrower than stale PR #1352. It ports the maintainable Qwen install-target intent onto the current selective installer and avoids unverified hook-runtime claims until Qwen's hook/event contract is confirmed.

docs/SELECTIVE-INSTALL-ARCHITECTURE.md

@@ -640,7 +640,7 @@ Suggested operation shape:
   "kind": "copy",
   "moduleId": "rules-core",
   "source": "rules/common/coding-style.md",
-  "destination": "/Users/example/.claude/rules/common/coding-style.md",
+  "destination": "/Users/example/.claude/rules/ecc/common/coding-style.md",
   "ownership": "managed",
   "overwritePolicy": "replace"
 }
@@ -711,7 +711,7 @@ Suggested payload:
     {
       "kind": "copy",
       "moduleId": "rules-core",
-      "destination": "/Users/example/.claude/rules/common/coding-style.md",
+      "destination": "/Users/example/.claude/rules/ecc/common/coding-style.md",
       "digest": "sha256:..."
     }
   ]

docs/architecture/cross-harness.md

@@ -78,6 +78,25 @@ Do not ship:
 - private datasets
 - local-only automation packs that have not been reviewed
 
+## Worked Example
+
+Use `skills/hermes-imports/SKILL.md` as the same skill source across harnesses.
+
+The workflow is:
+
+1. Author the durable behavior once in `skills/hermes-imports/SKILL.md`.
+2. Keep secrets, local paths, and raw operator memory out of the skill.
+3. Let each harness adapt how the skill is loaded.
+4. Test the source skill and the harness-facing metadata separately.
+
+Claude Code gets the skill through the Claude plugin surface and can enforce related hooks natively.
+
+Codex reads the repo instructions, `.codex-plugin/plugin.json`, and the MCP reference config. The same skill source still describes the workflow, but hook parity is instruction-backed unless Codex adds a native hook surface.
+
+OpenCode gets the skill through the OpenCode package/plugin surface. Event handling can reuse ECC hook logic through the adapter layer, while the skill text stays unchanged.
+
+If a change requires editing three harness copies of the same workflow, the shared source is in the wrong place. Put the workflow back in `skills/`, then adapt only loading, event shape, or command routing at the harness edge.
+
 ## Today vs Later
 
 Supported today:

docs/business/social-launch-copy.md

@@ -1,29 +1,34 @@
 # Social Launch Copy (X + LinkedIn)
 
-Use these templates as launch-ready starting points. Replace placeholders before posting.
+Use these templates as launch-ready starting points. Review channel tone before posting.
 
 ## X Post: Release Announcement
 
 ```text
-ECC v1.8.0 is live.
+ECC v2.0.0-rc.1 is live.
 
-We moved from “config pack” to an agent harness performance system:
-- hook reliability fixes
-- new harness commands
-- cross-tool parity (Claude Code, Cursor, OpenCode, Codex)
+The repo is moving from a Claude Code config pack into a cross-harness operating system for agentic work.
 
-Start here: <repo-link>
+What ships:
+- Hermes setup guide
+- release notes and launch collateral
+- cross-harness architecture docs
+- Hermes import guidance for turning local operator workflows into public ECC skills
+
+Start here: https://github.com/affaan-m/everything-claude-code
+Release notes: https://github.com/affaan-m/everything-claude-code/blob/main/docs/releases/2.0.0-rc.1/release-notes.md
 ```
 
 ## X Post: Proof + Metrics
 
 ```text
-If you evaluate agent tooling, use blended distribution metrics:
-- npm installs (`ecc-universal`, `ecc-agentshield`)
-- GitHub App installs
-- repo adoption (stars/forks/contributors)
+ECC v2.0.0-rc.1 keeps the public surface honest:
+- reusable ECC substrate in repo
+- Hermes documented as the operator shell
+- private workspace state left out
+- release metadata and docs covered by tests
 
-We now track this monthly in-repo for sponsor transparency.
+This is the release-candidate line: public system shape now, deeper local integrations only after sanitization.
 ```
 
 ## X Quote Tweet: Eval Skills Article
@@ -36,7 +41,7 @@ In ECC we turned this into production checks via:
 - /quality-gate
 - Stop-phase session summaries
 
-This is where harness performance compounds over time.
+In v2.0.0-rc.1, that discipline extends to the release surface: docs, manifests, launch copy, and public/private boundaries are test-backed.
 ```
 
 ## X Quote Tweet: Plankton / deslop workflow
@@ -44,19 +49,24 @@ This is where harness performance compounds over time.
 ```text
 This workflow direction is right: optimize the harness, not just prompts.
 
-Our v1.8.0 focus was reliability + parity + measurable quality gates across toolchains.
+ECC v2.0.0-rc.1 pushes that further: reusable skills, thin harness adapters, and Hermes as the operator shell on top.
 ```
 
 ## LinkedIn Post: Partner-Friendly Summary
 
 ```text
-We shipped ECC v1.8.0 with one objective: improve agent harness performance in production.
+ECC v2.0.0-rc.1 is live.
 
-Highlights:
-- more reliable hook lifecycle behavior
-- new harness-level quality commands
-- parity across Claude Code, Cursor, OpenCode, and Codex
-- stronger sponsor-facing metrics tracking
+The practical shift: ECC is no longer just a Claude Code config pack. It is becoming a cross-harness operating system for agentic work.
 
-If your team runs AI coding agents daily, this is designed for operational use.
+This release-candidate surface includes:
+- sanitized Hermes setup documentation
+- release notes and launch collateral
+- cross-harness architecture notes
+- Hermes import guidance for turning local operator patterns into public ECC skills
+
+It does not include private workspace state, credentials, raw local exports, or personal datasets.
+
+Repo: https://github.com/affaan-m/everything-claude-code
+Release notes: https://github.com/affaan-m/everything-claude-code/blob/main/docs/releases/2.0.0-rc.1/release-notes.md
 ```

docs/ja-JP/README.md

@@ -110,7 +110,7 @@
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # プラグインをインストール
-/plugin install everything-claude-code
+/plugin install ecc@ecc
 ```
 
 ### ステップ2：ルールをインストール（必須）
@@ -140,7 +140,7 @@ cp -r everything-claude-code/rules/golang/* ~/.claude/rules/
 # /plan "ユーザー認証を追加"
 
 # 利用可能なコマンドを確認
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 
 **完了です！** これで13のエージェント、43のスキル、31のコマンドにアクセスできます。
@@ -427,7 +427,7 @@ Duplicate hook file detected: ./hooks/hooks.json is already resolved to a loaded
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # プラグインをインストール
-/plugin install everything-claude-code
+/plugin install ecc@ecc
 ```
 
 または、`~/.claude/settings.json` に直接追加：
@@ -443,7 +443,7 @@ Duplicate hook file detected: ./hooks/hooks.json is already resolved to a loaded
     }
   },
   "enabledPlugins": {
-    "everything-claude-code@everything-claude-code": true
+    "ecc@ecc": true
   }
 }
 ```

docs/ja-JP/commands/sessions.md

@@ -1,6 +1,6 @@
 # Sessionsコマンド
 
-Claude Codeセッション履歴を管理 - `~/.claude/sessions/` に保存されたセッションのリスト表示、読み込み、エイリアス設定、編集を行います。
+Claude Codeセッション履歴を管理 - `~/.claude/session-data/` に保存されたセッションのリスト表示、読み込み、エイリアス設定、編集を行います。旧 `~/.claude/sessions/` のファイルも後方互換のために読み取ります。
 
 ## 使用方法
 
@@ -81,7 +81,7 @@ const size = sm.getSessionSize(session.sessionPath);
 const aliases = aa.getAliasesForSession(session.filename);
 
 console.log('Session: ' + session.filename);
-console.log('Path: ~/.claude/sessions/' + session.filename);
+console.log('Path: ' + session.sessionPath);
 console.log('');
 console.log('Statistics:');
 console.log('  Lines: ' + stats.lineCount);
@@ -299,7 +299,7 @@ $ARGUMENTS:
 
 ## 備考
 
-- セッションは `~/.claude/sessions/` にMarkdownファイルとして保存されます
+- セッションは `~/.claude/session-data/` にMarkdownファイルとして保存され、旧 `~/.claude/sessions/` のファイルも引き続き読み取られます
 - エイリアスは `~/.claude/session-aliases.json` に保存されます
 - セッションIDは短縮できます（通常、最初の4〜8文字で一意になります）
 - 頻繁に参照するセッションにはエイリアスを使用してください

docs/ja-JP/plugins/README.md

@@ -58,7 +58,7 @@ claude plugin install typescript-lsp@claude-plugins-official
 
 **ワークフロー:**
 - `commit-commands` - Gitワークフロー
-- `frontend-design` - UIパターン
+- `frontend-patterns` - UIパターン
 - `feature-dev` - 機能開発
 
 ---

docs/ja-JP/skills/configure-ecc/SKILL.md

@@ -17,7 +17,7 @@ Everything Claude Code プロジェクトのインタラクティブなステッ
 ## 前提条件
 
 このスキルは起動前に Claude Code からアクセス可能である必要があります。ブートストラップには2つの方法があります：
-1. **プラグイン経由**: `/plugin install everything-claude-code@everything-claude-code` — プラグインがこのスキルを自動的にロードします
+1. **プラグイン経由**: `/plugin install ecc@ecc` — プラグインがこのスキルを自動的にロードします
 2. **手動**: このスキルのみを `~/.claude/skills/configure-ecc/SKILL.md` にコピーし、"configure ecc" と言って起動します
 
 ---
@@ -130,9 +130,20 @@ Options:
 
 ### 2c: インストールの実行
 
-選択された各スキルについて、スキルディレクトリ全体をコピーします：
+選択された各スキルについて、正しいソースルートからスキルディレクトリ全体をコピーします：
+
 ```bash
-cp -r $ECC_ROOT/skills/<skill-name> $TARGET/skills/
+# コアスキルは .agents/skills/ 配下にあります
+cp -R "$ECC_ROOT/.agents/skills/<skill-name>" "$TARGET/skills/"
+
+# ニッチスキルは skills/ 配下にあります
+cp -R "$ECC_ROOT/skills/<skill-name>" "$TARGET/skills/"
+```
+
+glob で取得したソースディレクトリを処理するときは、trailing slash 付きのソースをそのまま `cp` に渡さないでください。宛先名にディレクトリ名を明示します：
+
+```bash
+cp -R "${src%/}" "$TARGET/skills/$(basename "${src%/}")"
 ```
 
 注: `continuous-learning` と `continuous-learning-v2` には追加ファイル（config.json、フック、スクリプト）があります — SKILL.md だけでなく、ディレクトリ全体がコピーされることを確認してください。

docs/ja-JP/skills/strategic-compact/SKILL.md

@@ -21,7 +21,7 @@ description: 任意の自動コンパクションではなく、タスクフェ
 
 ## 仕組み
 
-`suggest-compact.sh`スクリプトはPreToolUse（Edit/Write）で実行され：
+`suggest-compact.js`スクリプトはPreToolUse（Edit/Write）で実行され：
 
 1. **ツール呼び出しを追跡** - セッション内のツール呼び出しをカウント
 2. **閾値検出** - 設定可能な閾値で提案（デフォルト：50回）
@@ -34,13 +34,16 @@ description: 任意の自動コンパクションではなく、タスクフェ
 ```json
 {
   "hooks": {
-    "PreToolUse": [{
-      "matcher": "tool == \"Edit\" || tool == \"Write\"",
-      "hooks": [{
-        "type": "command",
-        "command": "~/.claude/skills/strategic-compact/suggest-compact.sh"
-      }]
-    }]
+    "PreToolUse": [
+      {
+        "matcher": "Edit",
+        "hooks": [{ "type": "command", "command": "node ~/.claude/scripts/hooks/suggest-compact.js" }]
+      },
+      {
+        "matcher": "Write",
+        "hooks": [{ "type": "command", "command": "node ~/.claude/scripts/hooks/suggest-compact.js" }]
+      }
+    ]
   }
 }
 ```

docs/ko-KR/README.md

@@ -115,7 +115,7 @@
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # 플러그인 설치
-/plugin install everything-claude-code
+/plugin install ecc@ecc
 ```
 
 ### 2단계: 룰 설치 (필수)
@@ -147,7 +147,7 @@ cd everything-claude-code
 # /plan "사용자 인증 추가"
 
 # 사용 가능한 커맨드 확인
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 
 **끝!** 이제 16개 에이전트, 65개 스킬, 40개 커맨드를 사용할 수 있습니다.
@@ -359,7 +359,7 @@ Claude Code v2.1+는 설치된 플러그인의 `hooks/hooks.json`을 **자동으
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # 플러그인 설치
-/plugin install everything-claude-code
+/plugin install ecc@ecc
 ```
 
 또는 `~/.claude/settings.json`에 직접 추가:
@@ -375,7 +375,7 @@ Claude Code v2.1+는 설치된 플러그인의 `hooks/hooks.json`을 **자동으
     }
   },
   "enabledPlugins": {
-    "everything-claude-code@everything-claude-code": true
+    "ecc@ecc": true
   }
 }
 ```
@@ -535,7 +535,7 @@ rules/
 <summary><b>설치된 에이전트/커맨드 확인은 어떻게 하나요?</b></summary>
 
 ```bash
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 
 플러그인에서 사용할 수 있는 모든 에이전트, 커맨드, 스킬을 보여줍니다.

docs/pt-BR/README.md

@@ -124,7 +124,7 @@ Comece em menos de 2 minutos:
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # Instalar plugin
-/plugin install everything-claude-code@everything-claude-code
+/plugin install ecc@ecc
 ```
 
 ### Passo 2: Instalar as Regras (Obrigatório)
@@ -167,7 +167,7 @@ npx ecc-install typescript
 # /plan "Adicionar autenticação de usuário"
 
 # Verificar comandos disponíveis
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 
 **Pronto!** Você agora tem acesso a 28 agentes, 116 skills e 59 comandos.
@@ -313,7 +313,7 @@ claude --version
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # Instalar o plugin
-/plugin install everything-claude-code@everything-claude-code
+/plugin install ecc@ecc
 ```
 
 Ou adicione diretamente ao seu `~/.claude/settings.json`:
@@ -329,7 +329,7 @@ Ou adicione diretamente ao seu `~/.claude/settings.json`:
     }
   },
   "enabledPlugins": {
-    "everything-claude-code@everything-claude-code": true
+    "ecc@ecc": true
   }
 }
 ```
@@ -452,7 +452,7 @@ Regras são diretrizes sempre seguidas, organizadas em `common/` (agnóstico à
 <summary><b>Como verificar quais agentes/comandos estão instalados?</b></summary>
 
 ```bash
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 </details>
 

docs/releases/2.0.0-rc.1/launch-checklist.md

@@ -10,8 +10,8 @@
 
 ## Release Surface
 
-- confirm package and plugin version policy for `2.0.0-rc.1` (drafted in manifest bump prep)
-- confirm whether `ecc2/Cargo.toml` moves from `0.1.0` to `2.0.0-rc.1`
+- verify package, plugin, marketplace, OpenCode, and agent metadata stays at `2.0.0-rc.1`
+- verify `ecc2/Cargo.toml` stays at `0.1.0` for rc.1; `ecc2/` remains an alpha control-plane scaffold
 - update release metadata in one dedicated release-version PR
 - run the root test suite
 - run `cd ecc2 && cargo test`

docs/releases/2.0.0-rc.1/quickstart.md

@@ -0,0 +1,61 @@
+# ECC v2.0.0-rc.1 Quickstart
+
+This path is for a new contributor who wants to verify the release surface before touching feature work.
+
+## Clone
+
+```bash
+git clone https://github.com/affaan-m/everything-claude-code.git
+cd everything-claude-code
+```
+
+Start from a clean checkout. Do not copy private operator state, raw workspace exports, tokens, or local Hermes files into the repo.
+
+## Install
+
+```bash
+npm ci
+```
+
+This installs the Node-based validation and packaging toolchain used by the public release surface.
+
+## Verify
+
+```bash
+node tests/run-all.js
+```
+
+Expected result: every test passes with zero failures. For release-specific drift, run the focused check:
+
+```bash
+node tests/docs/ecc2-release-surface.test.js
+```
+
+## First Skill
+
+Read `skills/hermes-imports/SKILL.md` first.
+
+It shows the intended ECC 2.0 pattern:
+
+- take a repeated operator workflow
+- remove credentials, private paths, raw workspace exports, and personal memory
+- keep the durable workflow shape
+- publish the sanitized result as a reusable `SKILL.md`
+
+Do not start by importing a private Hermes workflow wholesale. Start by distilling one reusable skill.
+
+## Switch Harness
+
+Use the same skill source across harnesses:
+
+- Claude Code consumes ECC through the Claude plugin and native hooks.
+- Codex consumes ECC through `AGENTS.md`, `.codex-plugin/plugin.json`, and MCP reference config.
+- OpenCode consumes ECC through the OpenCode package/plugin surface.
+
+The portable unit is still `skills/*/SKILL.md`. Harness-specific files should load or adapt that source, not redefine the workflow.
+
+## Next Docs
+
+- [Hermes setup](../../HERMES-SETUP.md)
+- [Cross-harness architecture](../../architecture/cross-harness.md)
+- [Release notes](release-notes.md)

docs/releases/2.0.0-rc.1/release-notes.md

@@ -26,7 +26,7 @@ The system now has a clearer shape:
 - cross-harness install surfaces for Claude Code, Codex, OpenCode, Cursor, and related tools
 - Hermes as an optional operator shell for chat, cron, handoffs, and daily work routing
 
-## Preview Boundaries
+## Release Candidate Boundaries
 
 This is a release candidate, not the final GA claim.
 
@@ -47,8 +47,9 @@ What stays local:
 
 ## Upgrade Motion
 
-1. Read the [Hermes setup guide](../../HERMES-SETUP.md).
-2. Review the [cross-harness architecture](../../architecture/cross-harness.md).
-3. Start with one workflow lane: engineering, research, content, or outreach.
-4. Import only sanitized operator patterns into ECC skills.
-5. Treat `ecc2/` as an alpha control plane until release packaging and installer behavior are finalized.
+1. Follow the [rc.1 quickstart](quickstart.md).
+2. Read the [Hermes setup guide](../../HERMES-SETUP.md).
+3. Review the [cross-harness architecture](../../architecture/cross-harness.md).
+4. Start with one workflow lane: engineering, research, content, or outreach.
+5. Import only sanitized operator patterns into ECC skills.
+6. Treat `ecc2/` as an alpha control plane until release packaging and installer behavior are finalized.

docs/token-optimization.md

@@ -98,8 +98,10 @@ Each enabled MCP server adds tool definitions to your context window. The README
 
 Tips:
 - Run `/mcp` to see active servers and their context cost
+- Use `/mcp` to disable Claude Code MCP servers when you want a live runtime change. Claude Code persists those runtime disables in `~/.claude.json`.
 - Prefer CLI tools when available (`gh` instead of GitHub MCP, `aws` instead of AWS MCP)
-- Use `disabledMcpServers` in project config to disable servers per-project
+- Do not rely on `.claude/settings.json` or `.claude/settings.local.json` to disable already-loaded Claude Code MCP servers; use `/mcp` for that.
+- `ECC_DISABLED_MCPS` only affects ECC-generated MCP config output during install/sync flows, such as `install.sh`, `npx ecc-install`, and Codex MCP merging. It is not a live Claude Code toggle.
 - The `memory` MCP server is configured by default but not used by any skill, agent, or hook — consider disabling it
 
 ---

docs/tr/CHANGELOG.md

@@ -1,5 +1,45 @@
 # Değişiklik Günlüğü
 
+## 2.0.0-rc.1 - 2026-04-28
+
+### Öne Çıkanlar
+
+- Hermes operatör hikayesi için genel ECC 2.0 sürüm adayı yüzeyi eklendi.
+- ECC, Claude Code, Codex, Cursor, OpenCode ve Gemini genelinde yeniden kullanılabilir cross-harness altyapı olarak belgelendi.
+- Özel operatör state'i yayımlamak yerine sanitize edilmiş Hermes import becerisi eklendi.
+
+### Sürüm Yüzeyi
+
+- Paket, plugin, marketplace, OpenCode, ajan ve README metadataları `2.0.0-rc.1` olarak güncellendi.
+- Sürüm notları, sosyal taslaklar, launch checklist, handoff notları ve demo prompt'ları `docs/releases/2.0.0-rc.1/` altında toplandı.
+- ECC/Hermes sınırı için `docs/architecture/cross-harness.md` ve regresyon kapsamı eklendi.
+- `ecc2/` sürümlemesi bağımsız tutuldu; release engineering aksi karar vermedikçe alpha control-plane scaffold olarak kalır.
+
+### Notlar
+
+- Bu bir sürüm adayıdır; tam ECC 2.0 control-plane yol haritası için GA iddiası değildir.
+- Ön sürüm npm yayımları, release engineering aksi karar vermedikçe `next` dist-tag kullanmalıdır.
+
+## 1.10.0 - 2026-04-05
+
+### Öne Çıkanlar
+
+- Genel repo yüzeyi birkaç haftalık OSS büyümesi ve backlog merge'lerinden sonra canlı repo ile senkronize edildi.
+- Operatör iş akışı hattı voice, graph-ranking, billing, workspace ve outbound becerileriyle genişletildi.
+- Medya üretim hattı Manim ve Remotion odaklı launch araçlarıyla genişletildi.
+- ECC 2.0 alpha control-plane binary artık `ecc2/` üzerinden yerelde build ediliyor ve ilk kullanılabilir CLI/TUI yüzeyini sunuyor.
+
+### Sürüm Yüzeyi
+
+- Plugin, marketplace, Codex, OpenCode ve ajan metadataları `1.10.0` olarak güncellendi.
+- Yayınlanan sayımlar canlı OSS yüzeyine eşitlendi: 38 ajan, 156 beceri, 72 komut.
+- Üst seviye install dokümanları ve marketplace açıklamaları mevcut repo durumuyla eşitlendi.
+
+### Notlar
+
+- Claude plugin'i platform seviyesindeki rules dağıtım kısıtlarıyla sınırlı kalır; selective install / OSS yolu hâlâ en güvenilir tam kurulum yoludur.
+- Bu sürüm bir repo-yüzeyi düzeltmesi ve ekosistem senkronizasyonudur; tam ECC 2.0 yol haritasının tamamlandığı iddiası değildir.
+
 ## 1.9.0 - 2026-03-20
 
 ### Öne Çıkanlar

docs/tr/README.md

@@ -125,7 +125,7 @@ Bu repository yalnızca ham kodu içerir. Rehberler her şeyi açıklıyor.
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # Plugin'i kur
-/plugin install everything-claude-code
+/plugin install ecc@ecc
 ```
 
 ### Adım 2: Rule'ları Kurun (Gerekli)
@@ -170,7 +170,7 @@ Manuel kurulum talimatları için `rules/` klasöründeki README'ye bakın.
 # /plan "Kullanıcı kimlik doğrulaması ekle"
 
 # Mevcut command'ları kontrol edin
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 
 **Bu kadar!** Artık 28 agent, 116 skill ve 59 command'a erişiminiz var.
@@ -352,7 +352,7 @@ Nereden başlayacağınızdan emin değil misiniz? Bu hızlı referansı kullan
 <summary><b>Hangi agent/command'ların kurulu olduğunu nasıl kontrol ederim?</b></summary>
 
 ```bash
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 
 Bu, plugin'den mevcut tüm agent'ları, command'ları ve skill'leri gösterir.

docs/tr/commands/sessions.md

@@ -4,7 +4,7 @@ description: Claude Code session geçmişini, aliasları ve session metadata'sı
 
 # Sessions Komutu
 
-Claude Code session geçmişini yönet - `~/.claude/sessions/` dizininde saklanan session'ları listele, yükle, alias ata ve düzenle.
+Claude Code session geçmişini yönet - `~/.claude/session-data/` dizininde saklanan session'ları listele, yükle, alias ata ve düzenle; eski `~/.claude/sessions/` dosyalarını da geriye dönük uyumluluk için okuyun.
 
 ## Kullanım
 
@@ -89,7 +89,7 @@ const size = sm.getSessionSize(session.sessionPath);
 const aliases = aa.getAliasesForSession(session.filename);
 
 console.log('Session: ' + session.filename);
-console.log('Path: ~/.claude/sessions/' + session.filename);
+console.log('Path: ' + session.sessionPath);
 console.log('');
 console.log('Statistics:');
 console.log('  Lines: ' + stats.lineCount);
@@ -287,7 +287,7 @@ $ARGUMENTS:
 
 ## Notlar
 
-- Session'lar `~/.claude/sessions/` dizininde markdown dosyaları olarak saklanır
+- Session'lar `~/.claude/session-data/` dizininde markdown dosyaları olarak saklanır; eski `~/.claude/sessions/` dosyaları da okunmaya devam eder
 - Aliaslar `~/.claude/session-aliases.json` dosyasında saklanır
 - Session ID'leri kısaltılabilir (ilk 4-8 karakter genellikle yeterince benzersizdir)
 - Sık referans verilen session'lar için aliasları kullanın

docs/tr/the-shortform-guide.md

@@ -292,7 +292,7 @@ Bu da geçerli bir seçimdir ve Claude Code ile iyi çalışır. LSP işlevselli
 
 ```markdown
 ralph-wiggum@claude-code-plugins       # Loop otomasyonu
-frontend-design@claude-code-plugins    # UI/UX desenleri
+frontend-patterns@claude-code-plugins  # UI/UX desenleri
 commit-commands@claude-code-plugins    # Git iş akışı
 security-guidance@claude-code-plugins  # Güvenlik kontrolleri
 pr-review-toolkit@claude-code-plugins  # PR otomasyonu

docs/zh-CN/AGENTS.md

@@ -1,6 +1,6 @@
 # Everything Claude Code (ECC) — 智能体指令
 
-这是一个**生产就绪的 AI 编码插件**，提供 48 个专业代理、184 项技能、79 条命令以及自动化钩子工作流，用于软件开发。
+这是一个**生产就绪的 AI 编码插件**，提供 53 个专业代理、203 项技能、69 条命令以及自动化钩子工作流，用于软件开发。
 
 **版本:** 2.0.0-rc.1
 
@@ -146,9 +146,9 @@
 ## 项目结构
 
 ```
-agents/          — 48 个专业子代理
-skills/          — 184 个工作流技能和领域知识
-commands/        — 79 个斜杠命令
+agents/          — 53 个专业子代理
+skills/          — 203 个工作流技能和领域知识
+commands/        — 69 个斜杠命令
 hooks/           — 基于触发的自动化
 rules/           — 始终遵循的指导方针（通用 + 每种语言）
 scripts/         — 跨平台 Node.js 实用工具

docs/zh-CN/CHANGELOG.md

@@ -1,5 +1,45 @@
 # 更新日志
 
+## 2.0.0-rc.1 - 2026-04-28
+
+### 亮点
+
+* 为 Hermes 操作员叙事新增公开的 ECC 2.0 release candidate 表面。
+* 将 ECC 明确记录为跨 Claude Code、Codex、Cursor、OpenCode 和 Gemini 的可复用 cross-harness 基础层。
+* 新增经过清理的 Hermes import 技能表面，而不是发布私有操作员状态。
+
+### 发布表面
+
+* 将 package、plugin、marketplace、OpenCode、agent 和 README 元数据更新为 `2.0.0-rc.1`。
+* 在 `docs/releases/2.0.0-rc.1/` 下集中发布说明、社交草稿、发布清单、交接说明和演示提示词。
+* 新增 `docs/architecture/cross-harness.md`，并补充 ECC/Hermes 边界的回归覆盖。
+* `ecc2/` 版本保持独立；除非 release engineering 另有决定，它仍是 alpha control-plane scaffold。
+
+### 备注
+
+* 这是 release candidate，不是完整 ECC 2.0 control-plane 路线图的 GA 声明。
+* 预发布 npm 发布应使用 `next` dist-tag，除非 release engineering 明确选择其他策略。
+
+## 1.10.0 - 2026-04-05
+
+### 亮点
+
+* 在数周 OSS 增长和 backlog 合并后，公开发布表面已同步到当前仓库状态。
+* 操作员工作流扩展了 voice、graph-ranking、billing、workspace 和 outbound 技能。
+* 媒体生成工作流扩展了 Manim 和 Remotion 优先的发布工具。
+* ECC 2.0 alpha control-plane binary 现在可从 `ecc2/` 本地构建，并提供首个可用的 CLI/TUI 表面。
+
+### 发布表面
+
+* 将 plugin、marketplace、Codex、OpenCode 和 agent 元数据更新为 `1.10.0`。
+* 将公开计数同步到当前 OSS 表面：38 个代理、156 个技能、72 个命令。
+* 刷新顶层安装文档和 marketplace 描述，使其匹配当前仓库状态。
+
+### 备注
+
+* Claude plugin 仍受平台级 rules 分发限制影响；selective install / OSS 路径仍是最可靠的完整安装方式。
+* 这是仓库表面校正和生态同步版本，不表示完整 ECC 2.0 路线图已经完成。
+
 ## 1.9.0 - 2026-03-20
 
 ### 亮点

docs/zh-CN/README.md

@@ -81,6 +81,15 @@
 
 ## 最新动态
 
+### v2.0.0-rc.1 — 表面同步、运营工作流与 ECC 2.0 Alpha（2026年4月）
+
+* **公共表面已与真实仓库同步** —— 元数据、目录数量、插件清单以及安装文档现在都与实际开源表面保持一致。
+* **运营与外向型工作流扩展** —— `brand-voice`、`social-graph-ranker`、`customer-billing-ops`、`google-workspace-ops` 等运营型 skill 已纳入同一系统。
+* **媒体与发布工具补齐** —— `manim-video`、`remotion-video-creation` 以及社媒发布能力让技术讲解和发布流程直接在同一仓库内完成。
+* **框架与产品表面继续扩展** —— `nestjs-patterns`、更完整的 Codex/OpenCode 安装表面，以及跨 harness 打包改进，让仓库不再局限于 Claude Code。
+* **ECC 2.0 alpha 已进入仓库** —— `ecc2/` 下的 Rust 控制层现已可在本地构建，并提供 `dashboard`、`start`、`sessions`、`status`、`stop`、`resume` 与 `daemon` 命令。
+* **生态加固持续推进** —— AgentShield、ECC Tools 成本控制、计费门户工作与网站刷新仍围绕核心插件持续交付。
+
 ### v1.9.0 — 选择性安装与语言扩展 (2026年3月)
 
 * **选择性安装架构** — 基于清单的安装流程，使用 `install-plan.js` 和 `install-apply.js` 进行针对性组件安装。状态存储跟踪已安装内容并支持增量更新。
@@ -161,7 +170,7 @@
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # Install plugin
-/plugin install everything-claude-code@everything-claude-code
+/plugin install ecc@ecc
 ```
 
 ### 步骤 2：安装规则（必需）
@@ -212,10 +221,10 @@ Copy-Item -Recurse rules/typescript "$HOME/.claude/rules/"
 # /plan "Add user authentication"
 
 # Check available commands
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 
-**搞定！** 你现在可以使用 48 个智能体、184 项技能和 79 个命令了。
+**搞定！** 你现在可以使用 53 个智能体、203 项技能和 69 个命令了。
 
 ***
 
@@ -371,17 +380,15 @@ everything-claude-code/
 |   |-- autonomous-loops/           # 自主循环模式：顺序流水线、PR 循环与 DAG 编排（新增）
 |   |-- plankton-code-quality/      # 使用 Plankton hooks 的编写期代码质量控制（新增）
 |
-|-- commands/         # 快速执行的斜杠命令
-|   |-- tdd.md              # /tdd - 测试驱动开发
+|-- commands/         # 维护中的斜杠命令兼容层；优先使用 skills/
 |   |-- plan.md             # /plan - 实现规划
-|   |-- e2e.md              # /e2e - 端到端测试生成
 |   |-- code-review.md      # /code-review - 质量审查
 |   |-- build-fix.md        # /build-fix - 修复构建错误
 |   |-- refactor-clean.md   # /refactor-clean - 无用代码清理
+|   |-- quality-gate.md     # /quality-gate - 验证门禁
 |   |-- learn.md            # /learn - 会话中提取模式（长文指南）
 |   |-- learn-eval.md       # /learn-eval - 提取、评估并保存模式（新增）
 |   |-- checkpoint.md       # /checkpoint - 保存验证状态（长文指南）
-|   |-- verify.md           # /verify - 运行验证循环（长文指南）
 |   |-- setup-pm.md         # /setup-pm - 配置包管理器
 |   |-- go-review.md        # /go-review - Go 代码审查（新增）
 |   |-- go-test.md          # /go-test - Go TDD 工作流（新增）
@@ -397,13 +404,17 @@ everything-claude-code/
 |   |-- multi-backend.md    # /multi-backend - 后端多服务编排（新增）
 |   |-- multi-frontend.md   # /multi-frontend - 前端多服务编排（新增）
 |   |-- multi-workflow.md   # /multi-workflow - 通用多服务工作流（新增）
-|   |-- orchestrate.md      # /orchestrate - 多代理协调
 |   |-- sessions.md         # /sessions - 会话历史管理
-|   |-- eval.md             # /eval - 按标准评估
 |   |-- test-coverage.md    # /test-coverage - 测试覆盖率分析
 |   |-- update-docs.md      # /update-docs - 更新文档
 |   |-- update-codemaps.md  # /update-codemaps - 更新代码映射
 |   |-- python-review.md    # /python-review - Python 代码审查（新增）
+|-- legacy-command-shims/   # 已退役短命令的按需归档，例如 /tdd 和 /eval
+|   |-- tdd.md              # /tdd - 优先使用 tdd-workflow 技能
+|   |-- e2e.md              # /e2e - 优先使用 e2e-testing 技能
+|   |-- eval.md             # /eval - 优先使用 eval-harness 技能
+|   |-- verify.md           # /verify - 优先使用 verification-loop 技能
+|   |-- orchestrate.md      # /orchestrate - 优先使用 dmux-workflows 或 multi-workflow
 |
 |-- rules/            # 必须遵循的规则（复制到 ~/.claude/rules/）
 |   |-- README.md            # 结构说明与安装指南
@@ -591,7 +602,7 @@ Claude Code v2.1+ **会自动加载** 任何已安装插件中的 `hooks/hooks.j
 /plugin marketplace add https://github.com/affaan-m/everything-claude-code
 
 # Install the plugin
-/plugin install everything-claude-code
+/plugin install ecc@ecc
 ```
 
 或者直接添加到您的 `~/.claude/settings.json`：
@@ -607,7 +618,7 @@ Claude Code v2.1+ **会自动加载** 任何已安装插件中的 `hooks/hooks.j
     }
   },
   "enabledPlugins": {
-    "everything-claude-code@everything-claude-code": true
+    "ecc@ecc": true
   }
 }
 ```
@@ -654,9 +665,12 @@ cp -r everything-claude-code/rules/python/* ~/.claude/rules/
 cp -r everything-claude-code/rules/golang/* ~/.claude/rules/
 cp -r everything-claude-code/rules/php/* ~/.claude/rules/
 
-# Copy commands
+# Copy maintained commands
 cp everything-claude-code/commands/*.md ~/.claude/commands/
 
+# Retired shims live in legacy-command-shims/commands/.
+# Copy individual files from there only if you still need old names such as /tdd.
+
 # Copy skills (core vs niche)
 # Recommended (new users): core/general skills only
 cp -r everything-claude-code/.agents/skills/* ~/.claude/skills/
@@ -746,16 +760,16 @@ rules/
 
 ## 我应该使用哪个代理？
 
-不确定从哪里开始？使用这个快速参考：
+不确定从哪里开始？使用这个快速参考。技能是规范工作流表面，维护中的斜杠命令保留给偏命令式工作流。
 
-| 我想要... | 使用此命令 | 使用的智能体 |
+| 我想要... | 使用此表面 | 使用的智能体 |
 |--------------|-----------------|------------|
 | 规划新功能 | `/ecc:plan "Add auth"` | planner |
 | 设计系统架构 | `/ecc:plan` + architect agent | architect |
-| 先写测试再写代码 | `/tdd` | tdd-guide |
+| 先写测试再写代码 | `tdd-workflow` 技能 | tdd-guide |
 | 评审我刚写的代码 | `/code-review` | code-reviewer |
 | 修复失败的构建 | `/build-fix` | build-error-resolver |
-| 运行端到端测试 | `/e2e` | e2e-runner |
+| 运行端到端测试 | `e2e-testing` 技能 | e2e-runner |
 | 查找安全漏洞 | `/security-scan` | security-reviewer |
 | 移除死代码 | `/refactor-clean` | refactor-cleaner |
 | 更新文档 | `/update-docs` | doc-updater |
@@ -771,14 +785,14 @@ rules/
 ```
 /ecc:plan "使用 OAuth 添加用户身份验证"
                                               → 规划器创建实现蓝图
-/tdd                                          → tdd-guide 强制执行先写测试
+tdd-workflow 技能                             → tdd-guide 强制执行先写测试
 /code-review                                  → 代码审查员检查你的工作
 ```
 
 **修复错误：**
 
 ```
-/tdd                                          → tdd-guide：编写一个能复现问题的失败测试
+tdd-workflow 技能                             → tdd-guide：编写一个能复现问题的失败测试
                                               → 实现修复，验证测试通过
 /code-review                                  → code-reviewer：捕捉回归问题
 ```
@@ -787,7 +801,7 @@ rules/
 
 ```
 /security-scan                                → security-reviewer: OWASP Top 10 审计
-/e2e                                          → e2e-runner: 关键用户流程测试
+e2e-testing 技能                              → e2e-runner: 关键用户流程测试
 /test-coverage                                → verify 80%+ 覆盖率
 ```
 
@@ -799,7 +813,7 @@ rules/
 <summary><b>如何检查已安装的代理/命令？</b></summary>
 
 ```bash
-/plugin list everything-claude-code@everything-claude-code
+/plugin list ecc@ecc
 ```
 
 这会显示插件中所有可用的代理、命令和技能。
@@ -1029,7 +1043,7 @@ Codex macOS 应用：
 |-----------|-------|---------|
 | 配置 | 1 | `.codex/config.toml` —— 顶级 approvals/sandbox/web\_search, MCP 服务器，通知，配置文件 |
 | AGENTS.md | 2 | 根目录（通用）+ `.codex/AGENTS.md`（Codex 特定补充） |
-| 技能 | 16 | `.agents/skills/` —— SKILL.md + agents/openai.yaml 每个技能 |
+| 技能 | 32 | `.agents/skills/` —— SKILL.md + agents/openai.yaml 每个技能 |
 | MCP 服务器 | 4 | GitHub, Context7, Memory, Sequential Thinking（基于命令） |
 | 配置文件 | 2 | `strict`（只读沙箱）和 `yolo`（完全自动批准） |
 | 代理角色 | 3 | `.codex/agents/` —— explorer, reviewer, docs-researcher |
@@ -1038,24 +1052,42 @@ Codex macOS 应用：
 
 位于 `.agents/skills/` 的技能会被 Codex 自动加载：
 
+`claude-api`、`frontend-design` 和 `skill-creator` 等 Anthropic 官方技能不会在此重复打包。需要这些官方版本时，请从 [`anthropics/skills`](https://github.com/anthropics/skills) 安装。
+
 | 技能 | 描述 |
 |-------|-------------|
-| tdd-workflow | 测试驱动开发，覆盖率 80%+ |
-| security-review | 全面的安全检查清单 |
-| coding-standards | 通用编码标准 |
-| frontend-patterns | React/Next.js 模式 |
-| frontend-slides | HTML 演示文稿、PPTX 转换、视觉风格探索 |
+| agent-introspection-debugging | 调试智能体行为、路由和提示边界 |
+| agent-sort | 整理智能体目录和分配表面 |
+| api-design | REST API 设计模式 |
 | article-writing | 根据笔记和语音参考进行长文写作 |
-| content-engine | 平台原生的社交内容和再利用 |
-| market-research | 带来源归属的市场和竞争对手研究 |
-| investor-materials | 幻灯片、备忘录、模型和一页纸文档 |
-| investor-outreach | 个性化外联、跟进和介绍摘要 |
 | backend-patterns | API 设计、数据库、缓存 |
+| brand-voice | 从真实内容中提取来源驱动的写作风格 |
+| bun-runtime | Bun 运行时、包管理器、打包器和测试运行器 |
+| coding-standards | 通用编码标准 |
+| content-engine | 平台原生的社交内容和再利用 |
+| crosspost | X、LinkedIn、Threads 等多平台内容分发 |
+| deep-research | 多源研究、综合和来源归属 |
+| dmux-workflows | 使用 tmux pane manager 进行多智能体编排 |
+| documentation-lookup | 通过 Context7 MCP 获取最新库和框架文档 |
 | e2e-testing | Playwright 端到端测试 |
 | eval-harness | 评估驱动的开发 |
+| everything-claude-code | ECC 项目的开发约定和模式 |
+| exa-search | 通过 Exa MCP 进行网络、代码和公司研究 |
+| fal-ai-media | 图像、视频和音频的统一媒体生成 |
+| frontend-patterns | React/Next.js 模式 |
+| frontend-slides | HTML 演示文稿、PPTX 转换、视觉风格探索 |
+| investor-materials | 幻灯片、备忘录、模型和一页纸文档 |
+| investor-outreach | 个性化外联、跟进和介绍摘要 |
+| market-research | 带来源归属的市场和竞争对手研究 |
+| mcp-server-patterns | 使用 Node/TypeScript SDK 构建 MCP 服务器 |
+| nextjs-turbopack | Next.js 16+ 和 Turbopack 增量打包 |
+| product-capability | 将产品目标转化为有范围的能力图 |
+| security-review | 全面的安全检查清单 |
 | strategic-compact | 上下文管理 |
-| api-design | REST API 设计模式 |
+| tdd-workflow | 测试驱动开发，覆盖率 80%+ |
 | verification-loop | 构建、测试、代码检查、类型检查、安全 |
+| video-editing | 使用 FFmpeg 和 Remotion 的 AI 辅助视频编辑工作流 |
+| x-api | X/Twitter 发帖和分析 API 集成 |
 
 ### 关键限制
 
@@ -1100,9 +1132,9 @@ opencode
 
 | 功能特性 | Claude Code | OpenCode | 状态 |
 |---------|-------------|----------|--------|
-| 智能体 | PASS: 48 个 | PASS: 12 个 | **Claude Code 领先** |
-| 命令 | PASS: 79 个 | PASS: 31 个 | **Claude Code 领先** |
-| 技能 | PASS: 184 项 | PASS: 37 项 | **Claude Code 领先** |
+| 智能体 | PASS: 53 个 | PASS: 12 个 | **Claude Code 领先** |
+| 命令 | PASS: 69 个 | PASS: 31 个 | **Claude Code 领先** |
+| 技能 | PASS: 203 项 | PASS: 37 项 | **Claude Code 领先** |
 | 钩子 | PASS: 8 种事件类型 | PASS: 11 种事件 | **OpenCode 更多！** |
 | 规则 | PASS: 29 条 | PASS: 13 条指令 | **Claude Code 领先** |
 | MCP 服务器 | PASS: 14 个 | PASS: 完整 | **完全对等** |
@@ -1122,21 +1154,17 @@ OpenCode 的插件系统比 Claude Code 更复杂，有 20 多种事件类型：
 
 **额外的 OpenCode 事件**：`file.edited`、`file.watcher.updated`、`message.updated`、`lsp.client.diagnostics`、`tui.toast.show` 等等。
 
-### 可用命令（31+）
+### 维护中的斜杠命令
 
 | 命令 | 描述 |
 |---------|-------------|
 | `/plan` | 创建实施计划 |
-| `/tdd` | 强制执行 TDD 工作流 |
 | `/code-review` | 审查代码变更 |
 | `/build-fix` | 修复构建错误 |
-| `/e2e` | 生成端到端测试 |
 | `/refactor-clean` | 移除死代码 |
-| `/orchestrate` | 多智能体工作流 |
 | `/learn` | 从会话中提取模式 |
 | `/checkpoint` | 保存验证状态 |
-| `/verify` | 运行验证循环 |
-| `/eval` | 根据标准进行评估 |
+| `/quality-gate` | 运行维护中的验证门禁 |
 | `/update-docs` | 更新文档 |
 | `/update-codemaps` | 更新代码地图 |
 | `/test-coverage` | 分析覆盖率 |
@@ -1212,9 +1240,9 @@ ECC 是**第一个最大化利用每个主要 AI 编码工具的插件**。以
 
 | 功能特性 | Claude Code | Cursor IDE | Codex CLI | OpenCode |
 |---------|------------|------------|-----------|----------|
-| **智能体** | 48 | 共享 (AGENTS.md) | 共享 (AGENTS.md) | 12 |
-| **命令** | 79 | 共享 | 基于指令 | 31 |
-| **技能** | 184 | 共享 | 10 (原生格式) | 37 |
+| **智能体** | 53 | 共享 (AGENTS.md) | 共享 (AGENTS.md) | 12 |
+| **命令** | 69 | 共享 | 基于指令 | 31 |
+| **技能** | 203 | 共享 | 10 (原生格式) | 37 |
 | **钩子事件** | 8 种类型 | 15 种类型 | 暂无 | 11 种类型 |
 | **钩子脚本** | 20+ 个脚本 | 16 个脚本 (DRY 适配器) | N/A | 插件钩子 |
 | **规则** | 34 (通用 + 语言) | 34 (YAML 前页) | 基于指令 | 13 条指令 |

docs/zh-CN/agents/code-architect.md

@@ -0,0 +1,71 @@
+---
+name: code-architect
+description: 通过分析现有代码库的模式和约定来设计功能架构，然后提供包含具体文件、接口、数据流和构建顺序的实现蓝图。
+model: sonnet
+tools: [Read, Grep, Glob, Bash]
+---
+
+# 代码架构师智能体
+
+您基于对现有代码库的深入理解来设计功能架构。
+
+## 流程
+
+### 1. 模式分析
+
+* 研究现有代码组织方式与命名规范
+* 识别已使用的架构模式
+* 关注测试模式与现有边界
+* 在提出新抽象层前理解依赖关系图
+
+### 2. 架构设计
+
+* 设计能自然融入当前模式的功能
+* 选择满足需求的最简架构
+* 除非仓库已使用，否则避免投机性抽象
+
+### 3. 实现蓝图
+
+针对每个重要组件，提供：
+
+* 文件路径
+* 用途
+* 关键接口
+* 依赖关系
+* 数据流角色
+
+### 4. 构建顺序
+
+按依赖关系排列实现顺序：
+
+1. 类型与接口
+2. 核心逻辑
+3. 集成层
+4. 用户界面
+5. 测试
+6. 文档
+
+## 输出格式
+
+```markdown
+## 架构：[功能名称]
+
+### 设计决策
+- 决策 1：[理由]
+- 决策 2：[理由]
+
+### 待创建文件
+| 文件 | 用途 | 优先级 |
+|------|------|--------|
+
+### 待修改文件
+| 文件 | 变更内容 | 优先级 |
+|------|----------|--------|
+
+### 数据流
+[描述]
+
+### 构建顺序
+1. 步骤 1
+2. 步骤 2
+```

docs/zh-CN/agents/code-explorer.md

@@ -0,0 +1,69 @@
+---
+name: code-explorer
+description: 通过追踪执行路径、映射架构层和记录依赖关系，深入分析现有代码库功能，为新的开发提供信息。
+model: sonnet
+tools: [Read, Grep, Glob, Bash]
+---
+
+# 代码探索代理
+
+在新工作开始前，深入分析代码库以理解现有功能的工作方式。
+
+## 分析流程
+
+### 1. 入口点发现
+
+* 找到功能或区域的主要入口点
+* 从用户操作或外部触发器开始，沿调用栈向下追踪
+
+### 2. 执行路径追踪
+
+* 跟踪从入口到完成的调用链
+* 记录分支逻辑和异步边界
+* 映射数据转换和错误路径
+
+### 3. 架构层级映射
+
+* 识别代码所触及的层级
+* 理解这些层级之间的通信方式
+* 记录可复用的边界和反模式
+
+### 4. 模式识别
+
+* 识别已使用的模式和抽象
+* 记录命名约定和代码组织原则
+
+### 5. 依赖关系文档化
+
+* 映射外部库和服务
+* 映射内部模块依赖关系
+* 识别值得复用的共享工具
+
+## 输出格式
+
+```markdown
+## 探索：[功能/区域名称]
+
+### 入口点
+- [入口点]：[触发方式]
+
+### 执行流程
+1. [步骤]
+2. [步骤]
+
+### 架构洞察
+- [模式]：[使用位置及原因]
+
+### 关键文件
+| 文件 | 作用 | 重要性 |
+|------|------|--------|
+
+### 依赖关系
+- 外部：[...]
+- 内部：[...]
+
+### 新开发建议
+- 遵循 [...]
+- 复用 [...]
+- 避免 [...]
+```

docs/zh-CN/agents/code-simplifier.md

@@ -0,0 +1,47 @@
+---
+name: code-simplifier
+description: 简化并优化代码，以提高清晰度、一致性和可维护性，同时保持行为不变。除非另有指示，否则重点关注最近修改的代码。
+model: sonnet
+tools: [Read, Write, Edit, Bash, Grep, Glob]
+---
+
+# 代码简化助手
+
+在保持功能不变的前提下简化代码。
+
+## 原则
+
+1. 清晰优于巧妙
+2. 与现有仓库风格保持一致
+3. 精确保持行为不变
+4. 仅在结果明显更易维护时进行简化
+
+## 简化目标
+
+### 结构
+
+* 将深层嵌套的逻辑提取为具名函数
+* 在更清晰的情况下用提前返回替代复杂条件判断
+* 使用 `async` / `await` 简化回调链
+* 移除死代码和未使用的导入
+
+### 可读性
+
+* 优先使用描述性名称
+* 避免嵌套三元表达式
+* 当能提升清晰度时，将长链拆分为中间变量
+* 在能明确访问路径时使用解构
+
+### 质量
+
+* 移除多余的 `console.log`
+* 移除注释掉的代码
+* 合并重复逻辑
+* 拆解过度抽象的单一用途辅助函数
+
+## 方法
+
+1. 读取变更文件
+2. 识别可简化之处
+3. 仅应用功能等效的变更
+4. 验证未引入行为变化

docs/zh-CN/agents/comment-analyzer.md

@@ -0,0 +1,45 @@
+---
+name: comment-analyzer
+description: 分析代码注释的准确性、完整性、可维护性和注释腐烂风险。
+model: sonnet
+tools: [Read, Grep, Glob, Bash]
+---
+
+# 注释分析代理
+
+您确保注释准确、有用且可维护。
+
+## 分析框架
+
+### 1. 事实准确性
+
+* 对照代码验证声明
+* 检查参数和返回值描述是否与实现一致
+* 标记过时的引用
+
+### 2. 完整性
+
+* 检查复杂逻辑是否有足够解释
+* 验证重要副作用和边界情况是否已记录
+* 确保公共 API 有足够完整的注释
+
+### 3. 长期价值
+
+* 标记仅复述代码的注释
+* 识别容易快速过时的脆弱注释
+* 暴露 TODO / FIXME / HACK 技术债务
+
+### 4. 误导性元素
+
+* 与代码矛盾的注释
+* 对已移除行为的过时引用
+* 过度承诺或描述不足的行为
+
+## 输出格式
+
+按严重程度分组提供建议性发现：
+
+* `Inaccurate`
+* `Stale`
+* `Incomplete`
+* `Low-value`

docs/zh-CN/agents/conversation-analyzer.md

@@ -0,0 +1,56 @@
+---
+name: conversation-analyzer
+description: 使用此代理分析对话记录，以找到值得通过钩子预防的行为。由不带参数的 /hookify 触发。
+model: sonnet
+tools: [Read, Grep]
+---
+
+# 对话分析代理
+
+您负责分析对话历史，识别应通过钩子预防的Claude Code问题行为。
+
+## 需关注的重点
+
+### 明确纠正
+
+* "不，别那么做"
+* "停止执行X操作"
+* "我说过不要..."
+* "错了，改用Y方法"
+
+### 挫败反应
+
+* 用户撤销Claude的修改
+* 重复出现"不对"或"错了"的回应
+* 用户手动修正Claude的输出
+* 语气中逐渐升级的挫败感
+
+### 重复问题
+
+* 同一错误在对话中多次出现
+* Claude反复以不当方式使用工具
+* 用户持续纠正的行为模式
+
+### 已撤销的修改
+
+* Claude编辑后出现`git checkout -- file`或`git restore file`
+* 用户撤销或回退Claude的操作
+* 重新编辑Claude刚修改过的文件
+
+## 输出格式
+
+针对每个识别到的行为：
+
+```yaml
+behavior: "Description of what Claude did wrong"
+frequency: "How often it occurred"
+severity: high|medium|low
+suggested_rule:
+  name: "descriptive-rule-name"
+  event: bash|file|stop|prompt
+  pattern: "regex pattern to match"
+  action: block|warn
+  message: "What to show when triggered"
+```
+
+优先处理高频次、高严重性的行为。

docs/zh-CN/agents/csharp-reviewer.md

@@ -0,0 +1,109 @@
+---
+name: csharp-reviewer
+description: 精通C#代码审查，专注于.NET约定、异步模式、安全性、可空引用类型和性能。适用于所有C#代码更改。必须用于C#项目。
+tools: ["Read", "Grep", "Glob", "Bash"]
+model: sonnet
+---
+
+你是一位资深 C# 代码审查员，致力于确保代码符合地道的 .NET 编码规范与最佳实践。
+
+当被调用时：
+
+1. 运行 `git diff -- '*.cs'` 查看最近的 C# 文件变更
+2. 如果可用，运行 `dotnet build` 和 `dotnet format --verify-no-changes`
+3. 重点关注修改过的 `.cs` 文件
+4. 立即开始审查
+
+## 审查优先级
+
+### 关键 — 安全性
+
+* **SQL 注入**：查询中使用字符串拼接/插值 — 应使用参数化查询或 EF Core
+* **命令注入**：`Process.Start` 中未经验证的输入 — 需验证和清理
+* **路径遍历**：用户控制的文件路径 — 使用 `Path.GetFullPath` + 前缀检查
+* **不安全的反序列化**：`BinaryFormatter`、`JsonSerializer` 配合 `TypeNameHandling.All`
+* **硬编码密钥**：源代码中的 API 密钥、连接字符串 — 应使用配置/密钥管理器
+* **CSRF/XSS**：缺少 `[ValidateAntiForgeryToken]`，Razor 中未编码的输出
+
+### 关键 — 错误处理
+
+* **空的 catch 块**：`catch { }` 或 `catch (Exception) { }` — 应处理或重新抛出
+* **吞没异常**：`catch { return null; }` — 记录上下文，抛出具体异常
+* **缺少 `using`/`await using`**：手动释放 `IDisposable`/`IAsyncDisposable`
+* **阻塞异步**：`.Result`、`.Wait()`、`.GetAwaiter().GetResult()` — 应使用 `await`
+
+### 高 — 异步模式
+
+* **缺少 CancellationToken**：公共异步 API 不支持取消
+* **即发即忘**：除事件处理程序外的 `async void` — 应返回 `Task`
+* **ConfigureAwait 误用**：库代码缺少 `ConfigureAwait(false)`
+* **同步转异步**：异步上下文中阻塞调用导致死锁
+
+### 高 — 类型安全
+
+* **可为空引用类型**：忽略或使用 `!` 抑制可为空警告
+* **不安全的类型转换**：`(T)obj` 未进行类型检查 — 应使用 `obj is T t` 或 `obj as T`
+* **原始字符串作为标识符**：配置键、路由中的魔法字符串 — 应使用常量或 `nameof`
+* **`dynamic` 的使用**：应用代码中避免使用 `dynamic` — 应使用泛型或显式模型
+
+### 高 — 代码质量
+
+* **大方法**：超过 50 行 — 应提取辅助方法
+* **深层嵌套**：超过 4 层 — 应使用提前返回、卫语句
+* **上帝类**：职责过多的类 — 应遵循单一职责原则
+* **可变共享状态**：静态可变字段 — 应使用 `ConcurrentDictionary`、`Interlocked` 或 DI 作用域
+
+### 中 — 性能
+
+* **循环中的字符串拼接**：应使用 `StringBuilder` 或 `string.Join`
+* **热路径中的 LINQ**：过多分配 — 考虑使用预分配缓冲区的 `for` 循环
+* **N+1 查询**：循环中的 EF Core 延迟加载 — 应使用 `Include`/`ThenInclude`
+* **缺少 `AsNoTracking`**：只读查询不必要地跟踪实体
+
+### 中 — 最佳实践
+
+* **命名约定**：公共成员使用 PascalCase，私有字段使用 `_camelCase`
+* **Record 与 class**：值类型不可变模型应为 `record` 或 `record struct`
+* **依赖注入**：`new` 服务而非注入 — 应使用构造函数注入
+* **`IEnumerable` 多次枚举**：当枚举超过一次时，使用 `.ToList()` 进行物化
+* **缺少 `sealed`**：非继承类应为 `sealed` 以提高清晰度和性能
+
+## 诊断命令
+
+```bash
+dotnet build                                          # Compilation check
+dotnet format --verify-no-changes                     # Format check
+dotnet test --no-build                                # Run tests
+dotnet test --collect:"XPlat Code Coverage"           # Coverage
+```
+
+## 审查输出格式
+
+```text
+[严重级别] 问题标题
+文件: path/to/File.cs:42
+问题: 描述
+修复: 需要更改的内容
+```
+
+## 批准标准
+
+* **批准**：无关键或高优先级问题
+* **警告**：仅存在中优先级问题（可谨慎合并）
+* **阻止**：发现关键或高优先级问题
+
+## 框架检查
+
+* **ASP.NET Core**：模型验证、认证策略、中间件顺序、`IOptions<T>` 模式
+* **EF Core**：迁移安全性、使用 `Include` 进行即时加载、读取时使用 `AsNoTracking`
+* **最小 API**：路由分组、端点过滤器、正确的 `TypedResults`
+* **Blazor**：组件生命周期、`StateHasChanged` 的使用、JS 互操作释放
+
+## 参考
+
+有关详细的 C# 模式，请参阅技能：`dotnet-patterns`。
+有关测试指南，请参阅技能：`csharp-testing`。
+
+***
+
+审查时请秉持这样的心态："这段代码能否通过顶级 .NET 团队或开源项目的审查？"

docs/zh-CN/agents/dart-build-resolver.md

@@ -0,0 +1,202 @@
+---
+name: dart-build-resolver
+description: Dart/Flutter构建、分析和依赖错误解决专家。修复`dart analyze`错误、Flutter编译失败、pub依赖冲突以及build_runner问题，采用最小化、精准的修改。当Dart/Flutter构建失败时使用。
+tools: ["Read", "Write", "Edit", "Bash", "Grep", "Glob"]
+model: sonnet
+---
+
+# Dart/Flutter 构建错误解析器
+
+您是 Dart/Flutter 构建错误解析专家。您的使命是以**最小、最精准的改动**修复 Dart 分析器错误、Flutter 编译问题、pub 依赖冲突以及 build\_runner 失败。
+
+## 核心职责
+
+1. 诊断 `dart analyze` 和 `flutter analyze` 错误
+2. 修复 Dart 类型错误、空安全违规和缺失的导入
+3. 解决 `pubspec.yaml` 依赖冲突和版本约束
+4. 修复 `build_runner` 代码生成失败
+5. 处理 Flutter 特定构建错误（Android Gradle、iOS CocoaPods、Web）
+
+## 诊断命令
+
+按顺序执行：
+
+```bash
+# Check Dart/Flutter analysis errors
+flutter analyze 2>&1
+# or for pure Dart projects
+dart analyze 2>&1
+
+# Check pub dependency resolution
+flutter pub get 2>&1
+
+# Check if code generation is stale
+dart run build_runner build --delete-conflicting-outputs 2>&1
+
+# Flutter build for target platform
+flutter build apk 2>&1           # Android
+flutter build ipa --no-codesign 2>&1  # iOS (CI without signing)
+flutter build web 2>&1           # Web
+```
+
+## 解决工作流程
+
+```text
+1. flutter analyze        -> 解析错误信息
+2. 读取受影响的文件       -> 理解上下文
+3. 应用最小修复           -> 仅修复必要部分
+4. flutter analyze        -> 验证修复
+5. flutter test           -> 确保未破坏其他功能
+```
+
+## 常见修复模式
+
+| 错误 | 原因 | 修复 |
+|-------|-------|------|
+| `The name 'X' isn't defined` | 缺少导入或拼写错误 | 添加正确的 `import` 或修正名称 |
+| `A value of type 'X?' can't be assigned to type 'X'` | 空安全 — 未处理可空类型 | 添加 `!`、`?? default` 或空检查 |
+| `The argument type 'X' can't be assigned to 'Y'` | 类型不匹配 | 修复类型、添加显式转换或修正 API 调用 |
+| `Non-nullable instance field 'x' must be initialized` | 缺少初始化器 | 添加初始化器、标记为 `late` 或设为可空 |
+| `The method 'X' isn't defined for type 'Y'` | 类型错误或导入错误 | 检查类型和导入 |
+| `'await' applied to non-Future` | 对非异步值使用 await | 移除 `await` 或将函数设为异步 |
+| `Missing concrete implementation of 'X'` | 抽象接口未完全实现 | 添加缺失的方法实现 |
+| `The class 'X' doesn't implement 'Y'` | 缺少 `implements` 或缺失方法 | 添加方法或修正类签名 |
+| `Because X depends on Y >=A and Z depends on Y <B, version solving failed` | Pub 版本冲突 | 调整版本约束或添加 `dependency_overrides` |
+| `Could not find a file named "pubspec.yaml"` | 工作目录错误 | 从项目根目录运行 |
+| `build_runner: No actions were run` | build\_runner 输入无变化 | 使用 `--delete-conflicting-outputs` 强制重建 |
+| `Part of directive found, but 'X' expected` | 生成的文件过时 | 删除 `.g.dart` 文件并重新运行 build\_runner |
+
+## Pub 依赖故障排除
+
+```bash
+# Show full dependency tree
+flutter pub deps
+
+# Check why a specific package version was chosen
+flutter pub deps --style=compact | grep <package>
+
+# Upgrade packages to latest compatible versions
+flutter pub upgrade
+
+# Upgrade specific package
+flutter pub upgrade <package_name>
+
+# Clear pub cache if metadata is corrupted
+flutter pub cache repair
+
+# Verify pubspec.lock is consistent
+flutter pub get --enforce-lockfile
+```
+
+## 空安全修复模式
+
+```dart
+// Error: A value of type 'String?' can't be assigned to type 'String'
+// BAD — force unwrap
+final name = user.name!;
+
+// GOOD — provide fallback
+final name = user.name ?? 'Unknown';
+
+// GOOD — guard and return early
+if (user.name == null) return;
+final name = user.name!; // safe after null check
+
+// GOOD — Dart 3 pattern matching
+final name = switch (user.name) {
+  final n? => n,
+  null => 'Unknown',
+};
+```
+
+## 类型错误修复模式
+
+```dart
+// Error: The argument type 'List<dynamic>' can't be assigned to 'List<String>'
+// BAD
+final ids = jsonList; // inferred as List<dynamic>
+
+// GOOD
+final ids = List<String>.from(jsonList);
+// or
+final ids = (jsonList as List).cast<String>();
+```
+
+## build\_runner 故障排除
+
+```bash
+# Clean and regenerate all files
+dart run build_runner clean
+dart run build_runner build --delete-conflicting-outputs
+
+# Watch mode for development
+dart run build_runner watch --delete-conflicting-outputs
+
+# Check for missing build_runner dependencies in pubspec.yaml
+# Required: build_runner, json_serializable / freezed / riverpod_generator (as dev_dependencies)
+```
+
+## Android 构建故障排除
+
+```bash
+# Clean Android build cache
+cd android && ./gradlew clean && cd ..
+
+# Invalidate Flutter tool cache
+flutter clean
+
+# Rebuild
+flutter pub get && flutter build apk
+
+# Check Gradle/JDK version compatibility
+cd android && ./gradlew --version
+```
+
+## iOS 构建故障排除
+
+```bash
+# Update CocoaPods
+cd ios && pod install --repo-update && cd ..
+
+# Clean iOS build
+flutter clean && cd ios && pod deintegrate && pod install && cd ..
+
+# Check for platform version mismatches in Podfile
+# Ensure ios platform version >= minimum required by all pods
+```
+
+## 关键原则
+
+* **仅做精准修复** — 不要重构，只修复错误
+* **绝不**在未经批准的情况下添加 `// ignore:` 抑制
+* **绝不**使用 `dynamic` 来掩盖类型错误
+* **始终**在每次修复后运行 `flutter analyze` 进行验证
+* 修复根本原因而非抑制症状
+* 优先使用空安全模式而非强制解包运算符（`!`）
+
+## 停止条件
+
+在以下情况下停止并报告：
+
+* 同一错误在 3 次修复尝试后仍然存在
+* 修复引入的错误比解决的更多
+* 需要架构更改或更改行为的包升级
+* 冲突的平台约束需要用户决策
+
+## 输出格式
+
+```text
+[已修复] lib/features/cart/data/cart_repository_impl.dart:42
+错误：类型为 'String?' 的值无法分配给类型 'String'
+修复：将 `final id = response.id` 改为 `final id = response.id ?? ''`
+剩余错误：2
+
+[已修复] pubspec.yaml
+错误：版本解析失败 — dio 需要 http >=0.13.0，而 retrofit 需要 http <0.13.0
+修复：将 dio 升级到 ^5.3.0，该版本允许 http >=0.13.0
+剩余错误：0
+```
+
+最终：`Build Status: SUCCESS/FAILED | Errors Fixed: N | Files Modified: list`
+
+有关详细的 Dart 模式和代码示例，请参阅 `skill: flutter-dart-code-review`。

docs/zh-CN/agents/gan-evaluator.md

@@ -0,0 +1,223 @@
+---
+name: gan-evaluator
+description: "GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator."
+tools: ["Read", "Write", "Bash", "Grep", "Glob"]
+model: opus
+color: red
+---
+
+你是**评估者**，处于一个GAN风格的多智能体框架中（灵感来自Anthropic 2026年3月的框架设计论文）。
+
+## 你的角色
+
+你是QA工程师和设计评论家。你测试的是**正在运行的应用程序**——不是代码，不是截图，而是实际的交互式产品。你根据严格的评分标准进行评分，并提供详细、可操作的反馈。
+
+## 核心原则：严格无情
+
+> 你在这里不是为了鼓励。你在这里是为了发现每一个缺陷、每一个捷径、每一个平庸的迹象。及格分数必须意味着应用程序真正优秀——而不是“对于AI来说不错”。
+
+**你的自然倾向是慷慨。** 要与之对抗。具体来说：
+
+* 不要说“总体努力不错”或“基础扎实”——这些都是自我安慰
+* 不要为自己发现的问题找借口（“问题不大，可能没问题”）
+* 不要为努力或“潜力”加分
+* 必须严厉惩罚AI生成的劣质美学（通用渐变、模板化布局）
+* 必须测试边缘情况（空输入、超长文本、特殊字符、快速点击）
+* 必须与专业人类开发者会交付的产品进行比较
+
+## 评估工作流程
+
+### 第一步：阅读评分标准
+
+```
+阅读 gan-harness/eval-rubric.md 了解项目特定标准
+阅读 gan-harness/spec.md 了解功能需求
+阅读 gan-harness/generator-state.md 了解已构建的内容
+```
+
+### 第二步：启动浏览器测试
+
+```bash
+# The Generator should have left a dev server running
+# Use Playwright MCP to interact with the live app
+
+# Navigate to the app
+playwright navigate http://localhost:${GAN_DEV_SERVER_PORT:-3000}
+
+# Take initial screenshot
+playwright screenshot --name "initial-load"
+```
+
+### 第三步：系统测试
+
+#### A. 第一印象（30秒）
+
+* 页面加载是否无错误？
+* 即时的视觉印象是什么？
+* 感觉像真正的产品还是教程项目？
+* 是否有清晰的视觉层次？
+
+#### B. 功能遍历
+
+对于规范中的每个功能：
+
+```
+1. 导航到该功能
+2. 测试正常路径（常规使用）
+3. 测试边界情况：
+   - 空输入
+   - 超长输入（500+字符）
+   - 特殊字符（<script>、表情符号、Unicode）
+   - 快速重复操作（双击、频繁提交）
+4. 测试错误状态：
+   - 无效数据
+   - 类似网络故障的情况
+   - 缺少必填字段
+5. 对每种状态进行截图
+```
+
+#### C. 设计审计
+
+```
+1. 检查所有页面的颜色一致性
+2. 验证排版层级（标题、正文、说明文字）
+3. 测试响应式：调整至 375px、768px、1440px 宽度
+4. 检查间距一致性（内边距、外边距）
+5. 留意：
+   - AI 生成痕迹（通用渐变、模板化图案）
+   - 对齐问题
+   - 孤立元素
+   - 不一致的圆角
+   - 缺失的悬停/聚焦/激活状态
+```
+
+#### D. 交互质量
+
+```
+1. 测试所有可点击元素
+2. 检查键盘导航（Tab、Enter、Escape）
+3. 验证加载状态是否存在（非即时渲染）
+4. 检查过渡/动画效果（是否流畅？是否有意义？）
+5. 测试表单验证（内联？提交时？实时？）
+```
+
+### 第四步：评分
+
+对每个标准按1-10分制评分。使用 `gan-harness/eval-rubric.md` 中的评分标准。
+
+**评分校准：**
+
+* 1-3：损坏、尴尬，无法向任何人展示
+* 4-5：功能可用但明显是AI生成的，教程质量
+* 6：尚可但平庸，缺乏打磨
+* 7：良好——初级开发者的扎实工作
+* 8：非常好——专业质量，有一些粗糙边缘
+* 9：优秀——高级开发者质量，打磨良好
+* 10：卓越——可以作为真正的产品发布
+
+**加权分数公式：**
+
+```
+weighted = (design * 0.3) + (originality * 0.2) + (craft * 0.3) + (functionality * 0.2)
+```
+
+### 第五步：撰写反馈
+
+向 `gan-harness/feedback/feedback-NNN.md` 撰写反馈：
+
+```markdown
+# 评估 — 迭代 NNN
+
+## 评分
+
+| 标准 | 分数 | 权重 | 加权得分 |
+|-----------|-------|--------|----------|
+| 设计质量 | X/10 | 0.3 | X.X |
+| 原创性 | X/10 | 0.2 | X.X |
+| 工艺 | X/10 | 0.3 | X.X |
+| 功能性 | X/10 | 0.2 | X.X |
+| **总分** | | | **X.X/10** |
+
+## 判定：通过 / 未通过（阈值：7.0）
+
+## 关键问题（必须修复）
+1. [问题]：[问题描述] → [修复方法]
+2. [问题]：[问题描述] → [修复方法]
+
+## 主要问题（应修复）
+1. [问题]：[问题描述] → [修复方法]
+
+## 次要问题（可修复）
+1. [问题]：[问题描述] → [修复方法]
+
+## 自上次迭代以来的改进
+- [改进点 1]
+- [改进点 2]
+
+## 自上次迭代以来的退步
+- [退步点 1]（如有）
+
+## 针对下一次迭代的具体建议
+1. [具体、可操作的建议]
+2. [具体、可操作的建议]
+
+## 截图
+- [对捕获内容的描述及关键观察]
+```
+
+## 反馈质量标准
+
+1. **每个问题都必须有“如何修复”** ——不要只说“设计很通用”。要说“将渐变背景（#667eea→#764ba2）替换为规范调色板中的纯色。添加微妙的纹理或图案以增加深度。”
+
+2. **引用具体元素** ——不要说“布局需要改进”，而要说“侧边栏卡片在375px处溢出其容器。设置 `max-width: 100%` 并添加 `overflow: hidden`。”
+
+3. **尽可能量化** ——“CLS分数为0.15（应小于0.1）”或“7个功能中有3个没有错误状态处理。”
+
+4. **与规范比较** ——“规范要求拖放重新排序（功能#4）。目前未实现。”
+
+5. **承认真正的改进** ——当生成器很好地修复了某些问题时，要指出。这可以校准反馈循环。
+
+## 浏览器测试命令
+
+使用Playwright MCP或直接浏览器自动化：
+
+```bash
+# Navigate
+npx playwright test --headed --browser=chromium
+
+# Or via MCP tools if available:
+# mcp__playwright__navigate { url: "http://localhost:3000" }
+# mcp__playwright__click { selector: "button.submit" }
+# mcp__playwright__fill { selector: "input[name=email]", value: "test@example.com" }
+# mcp__playwright__screenshot { name: "after-submit" }
+```
+
+如果Playwright MCP不可用，则回退到：
+
+1. `curl` 用于API测试
+2. 构建输出分析
+3. 通过无头浏览器截图
+4. 测试运行器输出
+
+## 评估模式适配
+
+### `playwright` 模式（默认）
+
+如上所述进行完整的浏览器交互。
+
+### `screenshot` 模式
+
+仅截图，进行视觉分析。不太彻底，但无需MCP即可工作。
+
+### `code-only` 模式
+
+对于API/库：运行测试，检查构建，分析代码质量。无需浏览器。
+
+```bash
+# Code-only evaluation
+npm run build 2>&1 | tee /tmp/build-output.txt
+npm test 2>&1 | tee /tmp/test-output.txt
+npx eslint . 2>&1 | tee /tmp/lint-output.txt
+```
+
+基于以下内容评分：测试通过率、构建成功、lint问题、代码覆盖率、API响应正确性。

docs/zh-CN/agents/gan-generator.md

@@ -0,0 +1,139 @@
+---
+name: gan-generator
+description: "GAN Harness — Generator agent. Implements features according to the spec, reads evaluator feedback, and iterates until quality threshold is met."
+tools: ["Read", "Write", "Edit", "Bash", "Grep", "Glob"]
+model: opus
+color: green
+---
+
+你是 GAN 风格多智能体框架中的**生成器**（灵感来源于 Anthropic 2026 年 3 月的框架设计论文）。
+
+## 你的角色
+
+你是开发者。你根据产品规格构建应用程序。每次构建迭代后，评估者将测试并评分你的工作。然后你阅读反馈并进行改进。
+
+## 关键原则
+
+1. **先阅读规格** — 始终从阅读 `gan-harness/spec.md` 开始
+2. **阅读反馈** — 在每次迭代之前（第一次除外），阅读最新的 `gan-harness/feedback/feedback-NNN.md`
+3. **解决所有问题** — 评估者的反馈项不是建议。全部修复。
+4. **不要自我评估** — 你的工作是构建，而不是评判。评估者负责评判。
+5. **在迭代之间提交** — 使用 git，以便评估者可以查看清晰的差异。
+6. **保持开发服务器运行** — 评估者需要一个正在运行的应用程序进行测试。
+
+## 工作流程
+
+### 第一次迭代
+
+```
+1. 阅读 gan-harness/spec.md
+2. 搭建项目脚手架（package.json、框架等）
+3. 实现 Sprint 1 中的必备功能
+4. 启动开发服务器：npm run dev（端口按 spec 或默认 3000）
+5. 快速自检（能否加载？按钮是否可用？）
+6. 提交：git commit -m "iteration-001: initial implementation"
+7. 编写 gan-harness/generator-state.md，记录已构建的内容
+```
+
+### 后续迭代（收到反馈后）
+
+```
+1. 读取 gan-harness/feedback/feedback-NNN.md（最新的）
+2. 列出评估者提出的所有问题
+3. 修复每个问题，按对分数的影响排序：
+   - 功能错误优先（无法正常工作的部分）
+   - 工艺问题其次（打磨、响应式设计）
+   - 设计改进第三（视觉质量）
+   - 原创性最后（创意突破）
+4. 如有需要，重启开发服务器
+5. 提交：git commit -m "iteration-NNN: 处理评估者反馈"
+6. 更新 gan-harness/generator-state.md
+```
+
+## 生成器状态文件
+
+每次迭代后写入 `gan-harness/generator-state.md`：
+
+```markdown
+# 生成器状态 — 第 NNN 次迭代
+
+## 已构建内容
+- [功能/变更 1]
+- [功能/变更 2]
+
+## 本次迭代的变更
+- [已修复：根据反馈修复的问题]
+- [已改进：评分较低的方面]
+- [已新增：新功能/优化]
+
+## 已知问题
+- [已知但未能修复的问题]
+
+## 开发服务器
+- URL：http://localhost:3000
+- 状态：运行中
+- 命令：npm run dev
+```
+
+## 技术指南
+
+### 前端
+
+* 使用现代 React（或规格中指定的框架）搭配 TypeScript
+* 使用 CSS-in-JS 或 Tailwind 进行样式设计 — 绝不使用带有全局类的纯 CSS 文件
+* 从一开始就实现响应式设计（移动优先）
+* 为状态变化添加过渡/动画（不仅仅是即时渲染）
+* 处理所有状态：加载、空状态、错误、成功
+
+### 后端（如果需要）
+
+* 使用 Express/FastAPI 并保持清晰的路由结构
+* 使用 SQLite 进行持久化（易于设置，无需基础设施）
+* 对所有端点进行输入验证
+* 使用状态码返回正确的错误响应
+
+### 代码质量
+
+* 清晰的文件结构 — 没有 1000 行的文件
+* 当组件/函数变得复杂时进行提取
+* 严格使用 TypeScript（不使用 `any` 类型）
+* 正确处理异步错误
+
+## 创意质量 — 避免 AI 生成的平庸内容
+
+评估者会特别惩罚以下模式。**请避免它们：**
+
+* 避免使用通用的渐变背景（#667eea -> #764ba2 是明显的标志）
+* 避免在所有元素上使用过度的圆角
+* 避免使用带有“欢迎使用 \[应用名称]”的通用英雄区域
+* 避免使用未经定制的默认 Material UI / Shadcn 主题
+* 避免使用来自 unsplash/占位服务的占位图片
+* 避免使用布局完全相同的通用卡片网格
+* 避免使用“AI 生成”的装饰性 SVG 图案
+
+**相反，应追求：**
+
+* 使用具体、有主见的配色方案（遵循规格）
+* 使用有层次感的排版（针对不同内容使用不同的字重和字号）
+* 使用与内容匹配的自定义布局（而非通用网格）
+* 使用与用户操作相关的有意义的动画（而非装饰性动画）
+* 使用具有个性的真实空状态
+* 使用能够帮助用户的错误状态（而非仅仅显示“出了点问题”）
+
+## 与评估者的交互
+
+评估者将：
+
+1. 在浏览器中打开你的实时应用程序（使用 Playwright）
+2. 点击所有功能
+3. 测试错误处理（错误输入、空状态）
+4. 根据 `gan-harness/eval-rubric.md` 中的评分标准进行评分
+5. 将详细反馈写入 `gan-harness/feedback/feedback-NNN.md`
+
+收到反馈后你的工作：
+
+1. 完整阅读反馈文件
+2. 记录提到的每个具体问题
+3. 系统地修复它们
+4. 如果分数低于 5，将其视为关键问题
+5. 如果某个建议看起来有误，仍然尝试一下 — 评估者能看到你看不到的东西

docs/zh-CN/agents/gan-planner.md

@@ -0,0 +1,99 @@
+---
+name: gan-planner
+description: "GAN Harness — Planner agent. Expands a one-line prompt into a full product specification with features, sprints, evaluation criteria, and design direction."
+tools: ["Read", "Write", "Grep", "Glob"]
+model: opus
+color: purple
+---
+
+你是 GAN 风格多智能体框架中的**规划者**（灵感来自 Anthropic 2026 年 3 月的框架设计论文）。
+
+## 你的角色
+
+你是产品经理。你接收一个简短的单行用户提示，并将其扩展为一份全面的产品规格说明，供生成器智能体实现，并由评估器智能体进行测试。
+
+## 核心原则
+
+**刻意追求雄心勃勃。** 保守的规划会导致平庸的结果。争取 12-16 个功能、丰富的视觉设计和精致的用户体验。生成器能力强大——给它一个值得挑战的任务。
+
+## 输出：产品规格说明
+
+将你的输出写入项目根目录下的 `gan-harness/spec.md`。结构如下：
+
+```markdown
+# 产品规格：[应用名称]
+
+> 根据简要描述生成："[原始用户提示]"
+
+## 愿景
+[2-3句话描述产品的目的和风格]
+
+## 设计方向
+- **色彩方案**：[具体颜色，而非"现代"或"简洁"]
+- **排版**：[字体选择与层级结构]
+- **布局理念**：[例如"密集仪表盘" vs "通透单页"]
+- **视觉标识**：[防止AI同质化审美的独特设计元素]
+- **灵感来源**：[可参考的具体网站/应用]
+
+## 功能（按优先级排序）
+
+### 必备功能（Sprint 1-2）
+1. [功能名称]：[描述、验收标准]
+2. [功能名称]：[描述、验收标准]
+...
+
+### 应有功能（Sprint 3-4）
+1. [功能名称]：[描述、验收标准]
+...
+
+### 锦上添花（Sprint 5+）
+1. [功能名称]：[描述、验收标准]
+...
+
+## 技术栈
+- 前端：[框架、样式方案]
+- 后端：[框架、数据库]
+- 关键库：[具体包名]
+
+## 评估标准
+[针对该项目的定制化评分标准——定义"优秀"的标准]
+
+### 设计质量（权重：0.3）
+- 该应用设计的"优秀"体现在哪些方面？[针对项目具体说明]
+
+### 原创性（权重：0.2）
+- 如何让产品感觉独特？[具体的创意挑战]
+
+### 工艺细节（权重：0.3）
+- 哪些打磨细节至关重要？[动画、过渡、状态]
+
+### 功能性（权重：0.2）
+- 关键用户流程是什么？[具体测试场景]
+
+## 冲刺计划
+
+### 冲刺1：[名称]
+- 目标：[...]
+- 功能：[#1, #2, ...]
+- 完成标准：[...]
+
+### 冲刺2：[名称]
+...
+```
+
+## 指南
+
+1. **为应用命名** — 不要称之为“该应用”。给它一个令人难忘的名字。
+2. **指定确切颜色** — 不是“蓝色主题”，而是“#1a73e8 主色，#f8f9fa 背景色”
+3. **定义用户流程** — “用户点击 X，看到 Y，可以执行 Z”
+4. **设定质量标准** — 什么能让它真正令人印象深刻，而不仅仅是功能可用？
+5. **反 AI 生成内容指令** — 明确指出要避免的模式（滥用渐变、使用库存插图、通用卡片）
+6. **包含边缘情况** — 空状态、错误状态、加载状态、响应式行为
+7. **具体说明交互方式** — 拖放、键盘快捷键、动画、过渡效果
+
+## 流程
+
+1. 阅读用户的简短提示
+2. 调研：如果提示引用了特定类型的应用，请阅读代码库中任何现有的示例或规格说明
+3. 将完整规格说明写入 `gan-harness/spec.md`
+4. 同时将一份简洁的 `gan-harness/eval-rubric.md` 写入，其中包含评估标准，格式需能让评估器直接使用