[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D83MTFAS689WFBRH0B3HKB":3,"skill-same:01M6D83MTFAS689WFBRH0B3HKB":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M6D83MTFAS689WFBRH0B3HKB","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.","oabdelmaksoud\u002FSuperClaw","oabdelmaksoud","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F50699149?v=4","01M6D5CVVN778ZCDP1WHS816SP","Omar Abdelmaksoud","01M6D5CW1RHNSKCJR85GJACBFT",2,"MIT","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fconfigure-ecc\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"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":33,"description":7},"ECC","main","7b610356e36623652299fa2acb477ff821b1d920","upstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fconfigure-ecc",0,"https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fo-abdelmaksoud\u002F","Full-Stack Engineer | AI Systems Architect | Building autonomous multi-agent systems","2026-03-08 21:12:53",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add oabdelmaksoud\u002FSuperClaw --skill configure-ecc",{"tool":49,"command":50},"bunx","bunx skills add oabdelmaksoud\u002FSuperClaw --skill configure-ecc",{"tool":52,"command":53},"pnpm","pnpm dlx skills add oabdelmaksoud\u002FSuperClaw --skill configure-ecc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fconfigure-ecc\u002FSKILL.md",true,[57,63,67,71,75,79],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"agents\u002Fopenai.yaml","REFERENCE","参考文档",243,"https:\u002F\u002Fgithub.com\u002FSigurdHall\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fthinking-planning\u002Fnarrative-design\u002Fagents\u002Fopenai.yaml",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fdata-storytelling.md",2218,"https:\u002F\u002Fgithub.com\u002FSigurdHall\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fthinking-planning\u002Fnarrative-design\u002Freferences\u002Fdata-storytelling.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fmeeting-prep.md",1819,"https:\u002F\u002Fgithub.com\u002FSigurdHall\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fthinking-planning\u002Fnarrative-design\u002Freferences\u002Fmeeting-prep.md",{"path":72,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fpitch-and-proposal.md",1841,"https:\u002F\u002Fgithub.com\u002FSigurdHall\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fthinking-planning\u002Fnarrative-design\u002Freferences\u002Fpitch-and-proposal.md",{"path":76,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fpresentation-and-visuals.md",2184,"https:\u002F\u002Fgithub.com\u002FSigurdHall\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fthinking-planning\u002Fnarrative-design\u002Freferences\u002Fpresentation-and-visuals.md",{"path":80,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fsource-influences.md",1162,"https:\u002F\u002Fgithub.com\u002FSigurdHall\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fthinking-planning\u002Fnarrative-design\u002Freferences\u002Fsource-influences.md",[84,105,118,149,175,194],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":95,"publishedAt":28},"01M6D88QCPTBZVCRED0NZ1Y8K8","visa-doc-translate","Translate visa application documents (images) to English and create a bilingual PDF with original and translation","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fvisa-doc-translate\u002FSKILL.md",[90],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[96,97,98,99,100,101,102,103,104],"translate","doc","visa doc translate","translation","application","create","images","PDF","documents",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":28},"01M6D88NBM95T3TFM50CYYAP65","verification-loop","A comprehensive verification system for Claude Code sessions.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[112,113,114,115,21,116,117],"verification","loop","verification loop","sessions","claude code sessions","system",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":135,"publishedAt":28},"01M6D88JFZ2P996GVRHJNSZSTM","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[124,127,130],{"categoryNo":125,"categoryName":126,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":128,"categoryName":129,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[136,137,138,139,140,141,21,142,143,144,145,146,147,148],"tdd","workflow","tdd workflow","e2e tests","e2e","integration","development","use","test","refactoring","coverage","tests","writing",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":28},"01M6D88FTHRRSVJMXF2G7MQAK3","swiftui-patterns","SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS\u002FmacOS UI best practices.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswiftui-patterns\u002FSKILL.md",[],[156,157,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174],"patterns","swiftui","swiftui patterns","architecture","macos","performance","state management","best practices","state","ui","Optimization","ios","architecture patterns","Composition","performance optimization","view","management","swiftui architecture","navigation",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":182,"publishedAt":28},"01M6D88D527QTQT9DKHTRFN6EA","swift-protocol-di-testing","Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-protocol-di-testing\u002FSKILL.md",[181],{"categoryNo":125,"categoryName":126,"taxonomyType":93,"taxonomyTypeDesc":94},[183,184,185,186,21,187,188,189,190,117,191,192,193],"swift protocol di testing","protocol","swift","testing","protocols","file","network","injection","dependency","swift testing","dependency injection",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":28},"01M6D88AJW8H2QNWSW5ZY82R43","swift-concurrency-6-2","Swift 6.2 Approachable Concurrency — single-threaded by default, @concurrent for explicit background offloading, isolated conformances for main actor types.","https:\u002F\u002Fgithub.com\u002Foabdelmaksoud\u002FSuperClaw\u002Fblob\u002Fmain\u002Fupstream-sync\u002Fwork\u002Fecc\u002Fskills\u002Fswift-concurrency-6-2\u002FSKILL.md",[],[201,202,185,203,204,34],"concurrency","swift concurrency","swift concurrency 6 2","default"]