[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DSWCCGAA8CX8XYDXNE55CT":3,"skill-same:01M6DSWCCGAA8CX8XYDXNE55CT":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6DSWCCGAA8CX8XYDXNE55CT","configure-ecc",null,"Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.","AntifragileTech\u002Fantifragile-claude-code","AntifragileTech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F174357194?v=4","01M6DQCYMK4CDSQQAN0ZC72NTV","01M6DQCYS9YPW1WKMQ5TJMPQ43",9,"MIT","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fconfigure-ecc\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26],"configure","configure ecc","code","Rules","interactive","user","installer","files","project","2026-11-10 10:12:30",false,"---\nname: configure-ecc\ndescription: Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.\norigin: ECC\n---\n\n# Configure Everything Claude Code (ECC)\n\nAn interactive, step-by-step installation wizard for the Everything Claude Code project. Uses `AskUserQuestion` to guide users through selective installation of skills and rules, then verifies correctness and offers optimization.\n\n## When to Activate\n\n- User says \"configure ecc\", \"install ecc\", \"setup everything claude code\", or similar\n- User wants to selectively install skills or rules from this project\n- User wants to verify or fix an existing ECC installation\n- User wants to optimize installed skills or rules for their project\n\n## Prerequisites\n\nThis skill must be accessible to Claude Code before activation. Two ways to bootstrap:\n1. **Via Plugin**: `\u002Fplugin install everything-claude-code` — the plugin loads this skill automatically\n2. **Manual**: Copy only this skill to `~\u002F.claude\u002Fskills\u002Fconfigure-ecc\u002FSKILL.md`, then activate by saying \"configure ecc\"\n\n---\n\n## Step 0: Clone ECC Repository\n\nBefore any installation, clone the latest ECC source to `\u002Ftmp`:\n\n```bash\nrm -rf \u002Ftmp\u002Feverything-claude-code\ngit clone https:\u002F\u002Fgithub.com\u002Faffaan-m\u002Feverything-claude-code.git \u002Ftmp\u002Feverything-claude-code\n```\n\nSet `ECC_ROOT=\u002Ftmp\u002Feverything-claude-code` as the source for all subsequent copy operations.\n\nIf the clone fails (network issues, etc.), use `AskUserQuestion` to ask the user to provide a local path to an existing ECC clone.\n\n---\n\n## Step 1: Choose Installation Level\n\nUse `AskUserQuestion` to ask the user where to install:\n\n```\nQuestion: \"Where should ECC components be installed?\"\nOptions:\n  - \"User-level (~\u002F.claude\u002F)\" — \"Applies to all your Claude Code projects\"\n  - \"Project-level (.claude\u002F)\" — \"Applies only to the current project\"\n  - \"Both\" — \"Common\u002Fshared items user-level, project-specific items project-level\"\n```\n\nStore the choice as `INSTALL_LEVEL`. Set the target directory:\n- User-level: `TARGET=~\u002F.claude`\n- Project-level: `TARGET=.claude` (relative to current project root)\n- Both: `TARGET_USER=~\u002F.claude`, `TARGET_PROJECT=.claude`\n\nCreate the target directories if they don't exist:\n```bash\nmkdir -p $TARGET\u002Fskills $TARGET\u002Frules\n```\n\n---\n\n## Step 2: Select & Install Skills\n\n### 2a: Choose Scope (Core vs Niche)\n\nDefault to **Core (recommended for new users)** — copy `.agents\u002Fskills\u002F*` plus `skills\u002Fsearch-first\u002F` for research-first workflows. This bundle covers engineering, evals, verification, security, strategic compaction, frontend design, and Anthropic cross-functional skills (article-writing, content-engine, market-research, frontend-slides).\n\nUse `AskUserQuestion` (single select):\n```\nQuestion: \"Install core skills only, or include niche\u002Fframework packs?\"\nOptions:\n  - \"Core only (recommended)\" — \"tdd, e2e, evals, verification, research-first, security, frontend patterns, compacting, cross-functional Anthropic skills\"\n  - \"Core + selected niche\" — \"Add framework\u002Fdomain-specific skills after core\"\n  - \"Niche only\" — \"Skip core, install specific framework\u002Fdomain skills\"\nDefault: Core only\n```\n\nIf the user chooses niche or core + niche, continue to category selection below and only include those niche skills they pick.\n\n### 2b: Choose Skill Categories\n\nThere are 27 skills organized into 4 categories. Use `AskUserQuestion` with `multiSelect: true`:\n\n```\nQuestion: \"Which skill categories do you want to install?\"\nOptions:\n  - \"Framework & Language\" — \"Django, Spring Boot, Go, Python, Java, Frontend, Backend patterns\"\n  - \"Database\" — \"PostgreSQL, ClickHouse, JPA\u002FHibernate patterns\"\n  - \"Workflow & Quality\" — \"TDD, verification, learning, security review, compaction\"\n  - \"All skills\" — \"Install every available skill\"\n```\n\n### 2c: Confirm Individual Skills\n\nFor each selected category, print the full list of skills below and ask the user to confirm or deselect specific ones. If the list exceeds 4 items, print the list as text and use `AskUserQuestion` with an \"Install all listed\" option plus \"Other\" for the user to paste specific names.\n\n**Category: Framework & Language (17 skills)**\n\n| Skill | Description |\n|-------|-------------|\n| `backend-patterns` | Backend architecture, API design, server-side best practices for Node.js\u002FExpress\u002FNext.js |\n| `coding-standards` | Universal coding standards for TypeScript, JavaScript, React, Node.js |\n| `django-patterns` | Django architecture, REST API with DRF, ORM, caching, signals, middleware |\n| `django-security` | Django security: auth, CSRF, SQL injection, XSS prevention |\n| `django-tdd` | Django testing with pytest-django, factory_boy, mocking, coverage |\n| `django-verification` | Django verification loop: migrations, linting, tests, security scans |\n| `frontend-patterns` | React, Next.js, state management, performance, UI patterns |\n| `frontend-slides` | Zero-dependency HTML presentations, style previews, and PPTX-to-web conversion |\n| `golang-patterns` | Idiomatic Go patterns, conventions for robust Go applications |\n| `golang-testing` | Go testing: table-driven tests, subtests, benchmarks, fuzzing |\n| `java-coding-standards` | Java coding standards for Spring Boot: naming, immutability, Optional, streams |\n| `python-patterns` | Pythonic idioms, PEP 8, type hints, best practices |\n| `python-testing` | Python testing with pytest, TDD, fixtures, mocking, parametrization |\n| `springboot-patterns` | Spring Boot architecture, REST API, layered services, caching, async |\n| `springboot-security` | Spring Security: authn\u002Fauthz, validation, CSRF, secrets, rate limiting |\n| `springboot-tdd` | Spring Boot TDD with JUnit 5, Mockito, MockMvc, Testcontainers |\n| `springboot-verification` | Spring Boot verification: build, static analysis, tests, security scans |\n\n**Category: Database (3 skills)**\n\n| Skill | Description |\n|-------|-------------|\n| `clickhouse-io` | ClickHouse patterns, query optimization, analytics, data engineering |\n| `jpa-patterns` | JPA\u002FHibernate entity design, relationships, query optimization, transactions |\n| `postgres-patterns` | PostgreSQL query optimization, schema design, indexing, security |\n\n**Category: Workflow & Quality (8 skills)**\n\n| Skill | Description |\n|-------|-------------|\n| `continuous-learning` | Auto-extract reusable patterns from sessions as learned skills |\n| `continuous-learning-v2` | Instinct-based learning with confidence scoring, evolves into skills\u002Fcommands\u002Fagents |\n| `eval-harness` | Formal evaluation framework for eval-driven development (EDD) |\n| `iterative-retrieval` | Progressive context refinement for subagent context problem |\n| `security-review` | Security checklist: auth, input, secrets, API, payment features |\n| `strategic-compact` | Suggests manual context compaction at logical intervals |\n| `tdd-workflow` | Enforces TDD with 80%+ coverage: unit, integration, E2E |\n| `verification-loop` | Verification and quality loop patterns |\n\n**Category: Business & Content (5 skills)**\n\n| Skill | Description |\n|-------|-------------|\n| `article-writing` | Long-form writing in a supplied voice using notes, examples, or source docs |\n| `content-engine` | Multi-platform social content, scripts, and repurposing workflows |\n| `market-research` | Source-attributed market, competitor, fund, and technology research |\n| `investor-materials` | Pitch decks, one-pagers, investor memos, and financial models |\n| `investor-outreach` | Personalized investor cold emails, warm intros, and follow-ups |\n\n**Standalone**\n\n| Skill | Description |\n|-------|-------------|\n| `project-guidelines-example` | Template for creating project-specific skills |\n\n### 2d: Execute Installation\n\nFor each selected skill, copy the entire skill directory:\n```bash\ncp -r $ECC_ROOT\u002Fskills\u002F\u003Cskill-name> $TARGET\u002Fskills\u002F\n```\n\nNote: `continuous-learning` and `continuous-learning-v2` have extra files (config.json, hooks, scripts) — ensure the entire directory is copied, not just SKILL.md.\n\n---\n\n## Step 3: Select & Install Rules\n\nUse `AskUserQuestion` with `multiSelect: true`:\n\n```\nQuestion: \"Which rule sets do you want to install?\"\nOptions:\n  - \"Common rules (Recommended)\" — \"Language-agnostic principles: coding style, git workflow, testing, security, etc. (8 files)\"\n  - \"TypeScript\u002FJavaScript\" — \"TS\u002FJS patterns, hooks, testing with Playwright (5 files)\"\n  - \"Python\" — \"Python patterns, pytest, black\u002Fruff formatting (5 files)\"\n  - \"Go\" — \"Go patterns, table-driven tests, gofmt\u002Fstaticcheck (5 files)\"\n```\n\nExecute installation:\n```bash\n# Common rules (flat copy into rules\u002F)\ncp -r $ECC_ROOT\u002Frules\u002Fcommon\u002F* $TARGET\u002Frules\u002F\n\n# Language-specific rules (flat copy into rules\u002F)\ncp -r $ECC_ROOT\u002Frules\u002Ftypescript\u002F* $TARGET\u002Frules\u002F   # if selected\ncp -r $ECC_ROOT\u002Frules\u002Fpython\u002F* $TARGET\u002Frules\u002F        # if selected\ncp -r $ECC_ROOT\u002Frules\u002Fgolang\u002F* $TARGET\u002Frules\u002F        # if selected\n```\n\n**Important**: If the user selects any language-specific rules but NOT common rules, warn them:\n> \"Language-specific rules extend the common rules. Installing without common rules may result in incomplete coverage. Install common rules too?\"\n\n---\n\n## Step 4: Post-Installation Verification\n\nAfter installation, perform these automated checks:\n\n### 4a: Verify File Existence\n\nList all installed files and confirm they exist at the target location:\n```bash\nls -la $TARGET\u002Fskills\u002F\nls -la $TARGET\u002Frules\u002F\n```\n\n### 4b: Check Path References\n\nScan all installed `.md` files for path references:\n```bash\ngrep -rn \"~\u002F.claude\u002F\" $TARGET\u002Fskills\u002F $TARGET\u002Frules\u002F\ngrep -rn \"..\u002Fcommon\u002F\" $TARGET\u002Frules\u002F\ngrep -rn \"skills\u002F\" $TARGET\u002Fskills\u002F\n```\n\n**For project-level installs**, flag any references to `~\u002F.claude\u002F` paths:\n- If a skill references `~\u002F.claude\u002Fsettings.json` — this is usually fine (settings are always user-level)\n- If a skill references `~\u002F.claude\u002Fskills\u002F` or `~\u002F.claude\u002Frules\u002F` — this may be broken if installed only at project level\n- If a skill references another skill by name — check that the referenced skill was also installed\n\n### 4c: Check Cross-References Between Skills\n\nSome skills reference others. Verify these dependencies:\n- `django-tdd` may reference `django-patterns`\n- `springboot-tdd` may reference `springboot-patterns`\n- `continuous-learning-v2` references `~\u002F.claude\u002Fhomunculus\u002F` directory\n- `python-testing` may reference `python-patterns`\n- `golang-testing` may reference `golang-patterns`\n- Language-specific rules reference `common\u002F` counterparts\n\n### 4d: Report Issues\n\nFor each issue found, report:\n1. **File**: The file containing the problematic reference\n2. **Line**: The line number\n3. **Issue**: What's wrong (e.g., \"references ~\u002F.claude\u002Fskills\u002Fpython-patterns but python-patterns was not installed\")\n4. **Suggested fix**: What to do (e.g., \"install python-patterns skill\" or \"update path to .claude\u002Fskills\u002F\")\n\n---\n\n## Step 5: Optimize Installed Files (Optional)\n\nUse `AskUserQuestion`:\n\n```\nQuestion: \"Would you like to optimize the installed files for your project?\"\nOptions:\n  - \"Optimize skills\" — \"Remove irrelevant sections, adjust paths, tailor to your tech stack\"\n  - \"Optimize rules\" — \"Adjust coverage targets, add project-specific patterns, customize tool configs\"\n  - \"Optimize both\" — \"Full optimization of all installed files\"\n  - \"Skip\" — \"Keep everything as-is\"\n```\n\n### If optimizing skills:\n1. Read each installed SKILL.md\n2. Ask the user what their project's tech stack is (if not already known)\n3. For each skill, suggest removals of irrelevant sections\n4. Edit the SKILL.md files in-place at the installation target (NOT the source repo)\n5. Fix any path issues found in Step 4\n\n### If optimizing rules:\n1. Read each installed rule .md file\n2. Ask the user about their preferences:\n   - Test coverage target (default 80%)\n   - Preferred formatting tools\n   - Git workflow conventions\n   - Security requirements\n3. Edit the rule files in-place at the installation target\n\n**Critical**: Only modify files in the installation target (`$TARGET\u002F`), NEVER modify files in the source ECC repository (`$ECC_ROOT\u002F`).\n\n---\n\n## Step 6: Installation Summary\n\nClean up the cloned repository from `\u002Ftmp`:\n\n```bash\nrm -rf \u002Ftmp\u002Feverything-claude-code\n```\n\nThen print a summary report:\n\n```\n## ECC Installation Complete\n\n### Installation Target\n- Level: [user-level \u002F project-level \u002F both]\n- Path: [target path]\n\n### Skills Installed ([count])\n- skill-1, skill-2, skill-3, ...\n\n### Rules Installed ([count])\n- common (8 files)\n- typescript (5 files)\n- ...\n\n### Verification Results\n- [count] issues found, [count] fixed\n- [list any remaining issues]\n\n### Optimizations Applied\n- [list changes made, or \"None\"]\n```\n\n---\n\n## Troubleshooting\n\n### \"Skills not being picked up by Claude Code\"\n- Verify the skill directory contains a `SKILL.md` file (not just loose .md files)\n- For user-level: check `~\u002F.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md` exists\n- For project-level: check `.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md` exists\n\n### \"Rules not working\"\n- Rules are flat files, not in subdirectories: `$TARGET\u002Frules\u002Fcoding-style.md` (correct) vs `$TARGET\u002Frules\u002Fcommon\u002Fcoding-style.md` (incorrect for flat install)\n- Restart Claude Code after installing rules\n\n### \"Path reference errors after project-level install\"\n- Some skills assume `~\u002F.claude\u002F` paths. Run Step 4 verification to find and fix these.\n- For `continuous-learning-v2`, the `~\u002F.claude\u002Fhomunculus\u002F` directory is always user-level — this is expected and not an error.\n","# Configure Everything Claude Code (ECC)\n\nAn interactive, step-by-step installation wizard for the Everything Claude Code project. Uses `AskUserQuestion` to guide users through selective installation of skills and rules, then verifies correctness and offers optimization.\n\n## When to Activate\n\n- User says \"configure ecc\", \"install ecc\", \"setup everything claude code\", or similar\n- User wants to selectively install skills or rules from this project\n- User wants to verify or fix an existing ECC installation\n- User wants to optimize installed skills or rules for their project\n\n## Prerequisites\n\nThis skill must be accessible to Claude Code before activation. Two ways to bootstrap:\n1. **Via Plugin**: `\u002Fplugin install everything-claude-code` — the plugin loads this skill automatically\n2. **Manual**: Copy only this skill to `~\u002F.claude\u002Fskills\u002Fconfigure-ecc\u002FSKILL.md`, then activate by saying \"configure ecc\"\n\n---\n\n## Step 0: Clone ECC Repository\n\nBefore any installation, clone the latest ECC source to `\u002Ftmp`:\n\n```bash\nrm -rf \u002Ftmp\u002Feverything-claude-code\ngit clone https:\u002F\u002Fgithub.com\u002Faffaan-m\u002Feverything-claude-code.git \u002Ftmp\u002Feverything-claude-code\n```\n\nSet `ECC_ROOT=\u002Ftmp\u002Feverything-claude-code` as the source for all subsequent copy operations.\n\nIf the clone fails (network issues, etc.), use `AskUserQuestion` to ask the user to provide a local path to an existing ECC clone.\n\n---\n\n## Step 1: Choose Installation Level\n\nUse `AskUserQuestion` to ask the user where to install:\n\n```\nQuestion: \"Where should ECC components be installed?\"\nOptions:\n  - \"User-level (~\u002F.claude\u002F)\" — \"Applies to all your Claude Code projects\"\n  - \"Project-level (.claude\u002F)\" — \"Applies only to the current project\"\n  - \"Both\" — \"Common\u002Fshared items user-level, project-specific items project-level\"\n```\n\nStore the choice as `INSTALL_LEVEL`. Set the target directory:\n- User-level: `TARGET=~\u002F.claude`\n- Project-level: `TARGET=.claude` (relative to current project root)\n- Both: `TARGET_USER=~\u002F.claude`, `TARGET_PROJECT=.claude`\n\nCreate the target directories if they don't exist:\n```bash\nmkdir -p $TARGET\u002Fskills $TARGET\u002Frules\n```\n\n---\n\n## Step 2: Select & Install Skills\n\n### 2a: Choose Scope (Core vs Niche)\n\nDefault to **Core (recommended for new users)** — copy `.agents\u002Fskills\u002F*` plus `skills\u002Fsearch-first\u002F` for research-first workflows. This bundle covers engineering, evals, verification, security, strategic compaction, frontend design, and Anthropic cross-functional skills (article-writing, content-engine, market-research, frontend-slides).\n\nUse `AskUserQuestion` (single select):\n```\nQuestion: \"Install core skills only, or include niche\u002Fframework packs?\"\nOptions:\n  - \"Core only (recommended)\" — \"tdd, e2e, evals, verification, research-first, security, frontend patterns, compacting, cross-functional Anthropic skills\"\n  - \"Core + selected niche\" — \"Add framework\u002Fdomain-specific skills after core\"\n  - \"Niche only\" — \"Skip core, install specific framework\u002Fdomain skills\"\nDefault: Core only\n```\n\nIf the user chooses niche or core + niche, continue to category selection below and only include those niche skills they pick.\n\n### 2b: Choose Skill Categories\n\nThere are 27 skills organized into 4 categories. Use `AskUserQuestion` with `multiSelect: true`:\n\n```\nQuestion: \"Which skill categories do you want to install?\"\nOptions:\n  - \"Framework & Language\" — \"Django, Spring Boot, Go, Python, Java, Frontend, Backend patterns\"\n  - \"Database\" — \"PostgreSQL, ClickHouse, JPA\u002FHibernate patterns\"\n  - \"Workflow & Quality\" — \"TDD, verification, learning, security review, compaction\"\n  - \"All skills\" — \"Install every available skill\"\n```\n\n### 2c: Confirm Individual Skills\n\nFor each selected category, print the full list of skills below and ask the user to confirm or deselect specific ones. If the list exceeds 4 items, print the list as text and use `AskUserQuestion` with an \"Install all listed\" option plus \"Other\" for the user to paste specific names.\n\n**Category: Framework & Language (17 skills)**\n\n| Skill | Description |\n|-------|-------------|\n| `backend-patterns` | Backend architecture, API design, server-side best practices for Node.js\u002FExpress\u002FNext.js |\n| `coding-standards` | Universal coding standards for TypeScript, JavaScript, React, Node.js |\n| `django-patterns` | Django architecture, REST API with DRF, ORM, caching, signals, middleware |\n| `django-security` | Django security: auth, CSRF, SQL injection, XSS prevention |\n| `django-tdd` | Django testing with pytest-django, factory_boy, mocking, coverage |\n| `django-verification` | Django verification loop: migrations, linting, tests, security scans |\n| `frontend-patterns` | React, Next.js, state management, performance, UI patterns |\n| `frontend-slides` | Zero-dependency HTML presentations, style previews, and PPTX-to-web conversion |\n| `golang-patterns` | Idiomatic Go patterns, conventions for robust Go applications |\n| `golang-testing` | Go testing: table-driven tests, subtests, benchmarks, fuzzing |\n| `java-coding-standards` | Java coding standards for Spring Boot: naming, immutability, Optional, streams |\n| `python-patterns` | Pythonic idioms, PEP 8, type hints, best practices |\n| `python-testing` | Python testing with pytest, TDD, fixtures, mocking, parametrization |\n| `springboot-patterns` | Spring Boot architecture, REST API, layered services, caching, async |\n| `springboot-security` | Spring Security: authn\u002Fauthz, validation, CSRF, secrets, rate limiting |\n| `springboot-tdd` | Spring Boot TDD with JUnit 5, Mockito, MockMvc, Testcontainers |\n| `springboot-verification` | Spring Boot verification: build, static analysis, tests, security scans |\n\n**Category: Database (3 skills)**\n\n| Skill | Description |\n|-------|-------------|\n| `clickhouse-io` | ClickHouse patterns, query optimization, analytics, data engineering |\n| `jpa-patterns` | JPA\u002FHibernate entity design, relationships, query optimization, transactions |\n| `postgres-patterns` | PostgreSQL query optimization, schema design, indexing, security |\n\n**Category: Workflow & Quality (8 skills)**\n\n| Skill | Description |\n|-------|-------------|\n| `continuous-learning` | Auto-extract reusable patterns from sessions as learned skills |\n| `continuous-learning-v2` | Instinct-based learning with confidence scoring, evolves into skills\u002Fcommands\u002Fagents |\n| `eval-harness` | Formal evaluation framework for eval-driven development (EDD) |\n| `iterative-retrieval` | Progressive context refinement for subagent context problem |\n| `security-review` | Security checklist: auth, input, secrets, API, payment features |\n| `strategic-compact` | Suggests manual context compaction at logical intervals |\n| `tdd-workflow` | Enforces TDD with 80%+ coverage: unit, integration, E2E |\n| `verification-loop` | Verification and quality loop patterns |\n\n**Category: Business & Content (5 skills)**\n\n| Skill | Description |\n|-------|-------------|\n| `article-writing` | Long-form writing in a supplied voice using notes, examples, or source docs |\n| `content-engine` | Multi-platform social content, scripts, and repurposing workflows |\n| `market-research` | Source-attributed market, competitor, fund, and technology research |\n| `investor-materials` | Pitch decks, one-pagers, investor memos, and financial models |\n| `investor-outreach` | Personalized investor cold emails, warm intros, and follow-ups |\n\n**Standalone**\n\n| Skill | Description |\n|-------|-------------|\n| `project-guidelines-example` | Template for creating project-specific skills |\n\n### 2d: Execute Installation\n\nFor each selected skill, copy the entire skill directory:\n```bash\ncp -r $ECC_ROOT\u002Fskills\u002F\u003Cskill-name> $TARGET\u002Fskills\u002F\n```\n\nNote: `continuous-learning` and `continuous-learning-v2` have extra files (config.json, hooks, scripts) — ensure the entire directory is copied, not just SKILL.md.\n\n---\n\n## Step 3: Select & Install Rules\n\nUse `AskUserQuestion` with `multiSelect: true`:\n\n```\nQuestion: \"Which rule sets do you want to install?\"\nOptions:\n  - \"Common rules (Recommended)\" — \"Language-agnostic principles: coding style, git workflow, testing, security, etc. (8 files)\"\n  - \"TypeScript\u002FJavaScript\" — \"TS\u002FJS patterns, hooks, testing with Playwright (5 files)\"\n  - \"Python\" — \"Python patterns, pytest, black\u002Fruff formatting (5 files)\"\n  - \"Go\" — \"Go patterns, table-driven tests, gofmt\u002Fstaticcheck (5 files)\"\n```\n\nExecute installation:\n```bash\n# Common rules (flat copy into rules\u002F)\ncp -r $ECC_ROOT\u002Frules\u002Fcommon\u002F* $TARGET\u002Frules\u002F\n\n# Language-specific rules (flat copy into rules\u002F)\ncp -r $ECC_ROOT\u002Frules\u002Ftypescript\u002F* $TARGET\u002Frules\u002F   # if selected\ncp -r $ECC_ROOT\u002Frules\u002Fpython\u002F* $TARGET\u002Frules\u002F        # if selected\ncp -r $ECC_ROOT\u002Frules\u002Fgolang\u002F* $TARGET\u002Frules\u002F        # if selected\n```\n\n**Important**: If the user selects any language-specific rules but NOT common rules, warn them:\n> \"Language-specific rules extend the common rules. Installing without common rules may result in incomplete coverage. Install common rules too?\"\n\n---\n\n## Step 4: Post-Installation Verification\n\nAfter installation, perform these automated checks:\n\n### 4a: Verify File Existence\n\nList all installed files and confirm they exist at the target location:\n```bash\nls -la $TARGET\u002Fskills\u002F\nls -la $TARGET\u002Frules\u002F\n```\n\n### 4b: Check Path References\n\nScan all installed `.md` files for path references:\n```bash\ngrep -rn \"~\u002F.claude\u002F\" $TARGET\u002Fskills\u002F $TARGET\u002Frules\u002F\ngrep -rn \"..\u002Fcommon\u002F\" $TARGET\u002Frules\u002F\ngrep -rn \"skills\u002F\" $TARGET\u002Fskills\u002F\n```\n\n**For project-level installs**, flag any references to `~\u002F.claude\u002F` paths:\n- If a skill references `~\u002F.claude\u002Fsettings.json` — this is usually fine (settings are always user-level)\n- If a skill references `~\u002F.claude\u002Fskills\u002F` or `~\u002F.claude\u002Frules\u002F` — this may be broken if installed only at project level\n- If a skill references another skill by name — check that the referenced skill was also installed\n\n### 4c: Check Cross-References Between Skills\n\nSome skills reference others. Verify these dependencies:\n- `django-tdd` may reference `django-patterns`\n- `springboot-tdd` may reference `springboot-patterns`\n- `continuous-learning-v2` references `~\u002F.claude\u002Fhomunculus\u002F` directory\n- `python-testing` may reference `python-patterns`\n- `golang-testing` may reference `golang-patterns`\n- Language-specific rules reference `common\u002F` counterparts\n\n### 4d: Report Issues\n\nFor each issue found, report:\n1. **File**: The file containing the problematic reference\n2. **Line**: The line number\n3. **Issue**: What's wrong (e.g., \"references ~\u002F.claude\u002Fskills\u002Fpython-patterns but python-patterns was not installed\")\n4. **Suggested fix**: What to do (e.g., \"install python-patterns skill\" or \"update path to .claude\u002Fskills\u002F\")\n\n---\n\n## Step 5: Optimize Installed Files (Optional)\n\nUse `AskUserQuestion`:\n\n```\nQuestion: \"Would you like to optimize the installed files for your project?\"\nOptions:\n  - \"Optimize skills\" — \"Remove irrelevant sections, adjust paths, tailor to your tech stack\"\n  - \"Optimize rules\" — \"Adjust coverage targets, add project-specific patterns, customize tool configs\"\n  - \"Optimize both\" — \"Full optimization of all installed files\"\n  - \"Skip\" — \"Keep everything as-is\"\n```\n\n### If optimizing skills:\n1. Read each installed SKILL.md\n2. Ask the user what their project's tech stack is (if not already known)\n3. For each skill, suggest removals of irrelevant sections\n4. Edit the SKILL.md files in-place at the installation target (NOT the source repo)\n5. Fix any path issues found in Step 4\n\n### If optimizing rules:\n1. Read each installed rule .md file\n2. Ask the user about their preferences:\n   - Test coverage target (default 80%)\n   - Preferred formatting tools\n   - Git workflow conventions\n   - Security requirements\n3. Edit the rule files in-place at the installation target\n\n**Critical**: Only modify files in the installation target (`$TARGET\u002F`), NEVER modify files in the source ECC repository (`$ECC_ROOT\u002F`).\n\n---\n\n## Step 6: Installation Summary\n\nClean up the cloned repository from `\u002Ftmp`:\n\n```bash\nrm -rf \u002Ftmp\u002Feverything-claude-code\n```\n\nThen print a summary report:\n\n```\n## ECC Installation Complete\n\n### Installation Target\n- Level: [user-level \u002F project-level \u002F both]\n- Path: [target path]\n\n### Skills Installed ([count])\n- skill-1, skill-2, skill-3, ...\n\n### Rules Installed ([count])\n- common (8 files)\n- typescript (5 files)\n- ...\n\n### Verification Results\n- [count] issues found, [count] fixed\n- [list any remaining issues]\n\n### Optimizations Applied\n- [list changes made, or \"None\"]\n```\n\n---\n\n## Troubleshooting\n\n### \"Skills not being picked up by Claude Code\"\n- Verify the skill directory contains a `SKILL.md` file (not just loose .md files)\n- For user-level: check `~\u002F.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md` exists\n- For project-level: check `.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md` exists\n\n### \"Rules not working\"\n- Rules are flat files, not in subdirectories: `$TARGET\u002Frules\u002Fcoding-style.md` (correct) vs `$TARGET\u002Frules\u002Fcommon\u002Fcoding-style.md` (incorrect for flat install)\n- Restart Claude Code after installing rules\n\n### \"Path reference errors after project-level install\"\n- Some skills assume `~\u002F.claude\u002F` paths. Run Step 4 verification to find and fix these.\n- For `continuous-learning-v2`, the `~\u002F.claude\u002Fhomunculus\u002F` directory is always user-level — this is expected and not an error.\n",{"name":5,"origin":32,"description":7},"ECC","master","c73386b305dec167db7654e0e6feacb462d4f9dc","assets\u002Fskills\u002Fthinking\u002Fconfigure-ecc",1,"https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code","https:\u002F\u002Fgithub.com\u002FAntifragileTech","2026-10-02 14:22:14",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add AntifragileTech\u002Fantifragile-claude-code --skill configure-ecc",{"tool":46,"command":47},"bunx","bunx skills add AntifragileTech\u002Fantifragile-claude-code --skill configure-ecc",{"tool":49,"command":50},"pnpm","pnpm dlx skills add AntifragileTech\u002Fantifragile-claude-code --skill configure-ecc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fconfigure-ecc\u002FSKILL.md",true,[],[55,81,95,109,122,135],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":74,"publishedAt":27},"01M6DT9Q6VYA615SCXR757TZZ7","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwriting-skills\u002FSKILL.md",[61,66,69],{"categoryNo":62,"categoryName":63,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":67,"categoryName":68,"taxonomyType":64,"taxonomyTypeDesc":65},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[75,76,77,78,79,80],"writing skills","writing","use","editing","work","deployment",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":89,"publishedAt":27},"01M6DT9GFHDNY90P41WGAE1TV0","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwriting-plans\u002FSKILL.md",[87,88],{"categoryNo":67,"categoryName":68,"taxonomyType":64,"taxonomyTypeDesc":65},{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[90,91,76,92,93,77,20,94],"plans","writing plans","requirements","task","spec",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":103,"publishedAt":27},"01M6DT9C6PFGD86WS3HY7YE3XG","docs:write-concisely","Apply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwrite-concisely\u002FSKILL.md",[101,102],{"categoryNo":67,"categoryName":68,"taxonomyType":64,"taxonomyTypeDesc":65},{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[104,105,106,107,21,108,76],"docs:write concisely","write","docs","read","documentation",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":27},"01M6DT98AWQ27P0N1CG97WAG66","kaizen:why","Iterative Five Whys root cause analysis drilling from symptoms to fundamentals","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fwhy\u002FSKILL.md",[],[111,116,117,118,119,120,121],"why","kaizen","issue","five whys","analysis","root cause analysis",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":27},"01M6DT93EH25NAX19R3WGE1P53","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fverification-loop\u002FSKILL.md",[],[129,130,131,132,20,133,134],"verification loop","verification","loop","sessions","claude code sessions","system",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":27},"01M6DT90GW7Z7VCN98P9DVYSNC","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FAntifragileTech\u002Fantifragile-claude-code\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fthinking\u002Fverification-before-completion\u002FSKILL.md",[],[142,130,143,79,77,144,145,146],"verification before completion","commands","evidence","claim","complete"]