From 90ad4edb1f492e211ff3f67535d3221096dc09bb Mon Sep 17 00:00:00 2001 From: Hor1zonZzz <105845016+Hor1zonZzz@users.noreply.github.com> Date: Thu, 5 Feb 2026 21:58:02 +0800 Subject: [PATCH] feat(skills): add configure-ecc interactive installation wizard Add a new skill that guides users through selective installation of ECC skills and rules via AskUserQuestion. Clones the repo to /tmp, lets users choose components and install level (user/project), verifies path correctness, offers optimization, and cleans up on completion. Co-authored-by: Hor1zonZzz Co-authored-by: Claude Opus 4.5 --- skills/configure-ecc/SKILL.md | 298 ++++++++++++++++++++++++++++++++++ 1 file changed, 298 insertions(+) create mode 100644 skills/configure-ecc/SKILL.md diff --git a/skills/configure-ecc/SKILL.md b/skills/configure-ecc/SKILL.md new file mode 100644 index 00000000..c57118cf --- /dev/null +++ b/skills/configure-ecc/SKILL.md @@ -0,0 +1,298 @@ +--- +name: configure-ecc +description: 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. +--- + +# Configure Everything Claude Code (ECC) + +An 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. + +## When to Activate + +- User says "configure ecc", "install ecc", "setup everything claude code", or similar +- User wants to selectively install skills or rules from this project +- User wants to verify or fix an existing ECC installation +- User wants to optimize installed skills or rules for their project + +## Prerequisites + +This skill must be accessible to Claude Code before activation. Two ways to bootstrap: +1. **Via Plugin**: `/plugin install everything-claude-code` — the plugin loads this skill automatically +2. **Manual**: Copy only this skill to `~/.claude/skills/configure-ecc/SKILL.md`, then activate by saying "configure ecc" + +--- + +## Step 0: Clone ECC Repository + +Before any installation, clone the latest ECC source to `/tmp`: + +```bash +rm -rf /tmp/everything-claude-code +git clone https://github.com/affaan-m/everything-claude-code.git /tmp/everything-claude-code +``` + +Set `ECC_ROOT=/tmp/everything-claude-code` as the source for all subsequent copy operations. + +If the clone fails (network issues, etc.), use `AskUserQuestion` to ask the user to provide a local path to an existing ECC clone. + +--- + +## Step 1: Choose Installation Level + +Use `AskUserQuestion` to ask the user where to install: + +``` +Question: "Where should ECC components be installed?" +Options: + - "User-level (~/.claude/)" — "Applies to all your Claude Code projects" + - "Project-level (.claude/)" — "Applies only to the current project" + - "Both" — "Common/shared items user-level, project-specific items project-level" +``` + +Store the choice as `INSTALL_LEVEL`. Set the target directory: +- User-level: `TARGET=~/.claude` +- Project-level: `TARGET=.claude` (relative to current project root) +- Both: `TARGET_USER=~/.claude`, `TARGET_PROJECT=.claude` + +Create the target directories if they don't exist: +```bash +mkdir -p $TARGET/skills $TARGET/rules +``` + +--- + +## Step 2: Select & Install Skills + +### 2a: Choose Skill Categories + +There are 27 skills organized into 4 categories. Use `AskUserQuestion` with `multiSelect: true`: + +``` +Question: "Which skill categories do you want to install?" +Options: + - "Framework & Language" — "Django, Spring Boot, Go, Python, Java, Frontend, Backend patterns" + - "Database" — "PostgreSQL, ClickHouse, JPA/Hibernate patterns" + - "Workflow & Quality" — "TDD, verification, learning, security review, compaction" + - "All skills" — "Install every available skill" +``` + +### 2b: Confirm Individual Skills + +For 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. + +**Category: Framework & Language (16 skills)** + +| Skill | Description | +|-------|-------------| +| `backend-patterns` | Backend architecture, API design, server-side best practices for Node.js/Express/Next.js | +| `coding-standards` | Universal coding standards for TypeScript, JavaScript, React, Node.js | +| `django-patterns` | Django architecture, REST API with DRF, ORM, caching, signals, middleware | +| `django-security` | Django security: auth, CSRF, SQL injection, XSS prevention | +| `django-tdd` | Django testing with pytest-django, factory_boy, mocking, coverage | +| `django-verification` | Django verification loop: migrations, linting, tests, security scans | +| `frontend-patterns` | React, Next.js, state management, performance, UI patterns | +| `golang-patterns` | Idiomatic Go patterns, conventions for robust Go applications | +| `golang-testing` | Go testing: table-driven tests, subtests, benchmarks, fuzzing | +| `java-coding-standards` | Java coding standards for Spring Boot: naming, immutability, Optional, streams | +| `python-patterns` | Pythonic idioms, PEP 8, type hints, best practices | +| `python-testing` | Python testing with pytest, TDD, fixtures, mocking, parametrization | +| `springboot-patterns` | Spring Boot architecture, REST API, layered services, caching, async | +| `springboot-security` | Spring Security: authn/authz, validation, CSRF, secrets, rate limiting | +| `springboot-tdd` | Spring Boot TDD with JUnit 5, Mockito, MockMvc, Testcontainers | +| `springboot-verification` | Spring Boot verification: build, static analysis, tests, security scans | + +**Category: Database (3 skills)** + +| Skill | Description | +|-------|-------------| +| `clickhouse-io` | ClickHouse patterns, query optimization, analytics, data engineering | +| `jpa-patterns` | JPA/Hibernate entity design, relationships, query optimization, transactions | +| `postgres-patterns` | PostgreSQL query optimization, schema design, indexing, security | + +**Category: Workflow & Quality (8 skills)** + +| Skill | Description | +|-------|-------------| +| `continuous-learning` | Auto-extract reusable patterns from sessions as learned skills | +| `continuous-learning-v2` | Instinct-based learning with confidence scoring, evolves into skills/commands/agents | +| `eval-harness` | Formal evaluation framework for eval-driven development (EDD) | +| `iterative-retrieval` | Progressive context refinement for subagent context problem | +| `security-review` | Security checklist: auth, input, secrets, API, payment features | +| `strategic-compact` | Suggests manual context compaction at logical intervals | +| `tdd-workflow` | Enforces TDD with 80%+ coverage: unit, integration, E2E | +| `verification-loop` | Verification and quality loop patterns | + +**Standalone** + +| Skill | Description | +|-------|-------------| +| `project-guidelines-example` | Template for creating project-specific skills | + +### 2c: Execute Installation + +For each selected skill, copy the entire skill directory: +```bash +cp -r $ECC_ROOT/skills/ $TARGET/skills/ +``` + +Note: `continuous-learning` and `continuous-learning-v2` have extra files (config.json, hooks, scripts) — ensure the entire directory is copied, not just SKILL.md. + +--- + +## Step 3: Select & Install Rules + +Use `AskUserQuestion` with `multiSelect: true`: + +``` +Question: "Which rule sets do you want to install?" +Options: + - "Common rules (Recommended)" — "Language-agnostic principles: coding style, git workflow, testing, security, etc. (8 files)" + - "TypeScript/JavaScript" — "TS/JS patterns, hooks, testing with Playwright (5 files)" + - "Python" — "Python patterns, pytest, black/ruff formatting (5 files)" + - "Go" — "Go patterns, table-driven tests, gofmt/staticcheck (5 files)" +``` + +Execute installation: +```bash +# Common rules (flat copy into rules/) +cp -r $ECC_ROOT/rules/common/* $TARGET/rules/ + +# Language-specific rules (flat copy into rules/) +cp -r $ECC_ROOT/rules/typescript/* $TARGET/rules/ # if selected +cp -r $ECC_ROOT/rules/python/* $TARGET/rules/ # if selected +cp -r $ECC_ROOT/rules/golang/* $TARGET/rules/ # if selected +``` + +**Important**: If the user selects any language-specific rules but NOT common rules, warn them: +> "Language-specific rules extend the common rules. Installing without common rules may result in incomplete coverage. Install common rules too?" + +--- + +## Step 4: Post-Installation Verification + +After installation, perform these automated checks: + +### 4a: Verify File Existence + +List all installed files and confirm they exist at the target location: +```bash +ls -la $TARGET/skills/ +ls -la $TARGET/rules/ +``` + +### 4b: Check Path References + +Scan all installed `.md` files for path references: +```bash +grep -rn "~/.claude/" $TARGET/skills/ $TARGET/rules/ +grep -rn "../common/" $TARGET/rules/ +grep -rn "skills/" $TARGET/skills/ +``` + +**For project-level installs**, flag any references to `~/.claude/` paths: +- If a skill references `~/.claude/settings.json` — this is usually fine (settings are always user-level) +- If a skill references `~/.claude/skills/` or `~/.claude/rules/` — this may be broken if installed only at project level +- If a skill references another skill by name — check that the referenced skill was also installed + +### 4c: Check Cross-References Between Skills + +Some skills reference others. Verify these dependencies: +- `django-tdd` may reference `django-patterns` +- `springboot-tdd` may reference `springboot-patterns` +- `continuous-learning-v2` references `~/.claude/homunculus/` directory +- `python-testing` may reference `python-patterns` +- `golang-testing` may reference `golang-patterns` +- Language-specific rules reference `common/` counterparts + +### 4d: Report Issues + +For each issue found, report: +1. **File**: The file containing the problematic reference +2. **Line**: The line number +3. **Issue**: What's wrong (e.g., "references ~/.claude/skills/python-patterns but python-patterns was not installed") +4. **Suggested fix**: What to do (e.g., "install python-patterns skill" or "update path to .claude/skills/") + +--- + +## Step 5: Optimize Installed Files (Optional) + +Use `AskUserQuestion`: + +``` +Question: "Would you like to optimize the installed files for your project?" +Options: + - "Optimize skills" — "Remove irrelevant sections, adjust paths, tailor to your tech stack" + - "Optimize rules" — "Adjust coverage targets, add project-specific patterns, customize tool configs" + - "Optimize both" — "Full optimization of all installed files" + - "Skip" — "Keep everything as-is" +``` + +### If optimizing skills: +1. Read each installed SKILL.md +2. Ask the user what their project's tech stack is (if not already known) +3. For each skill, suggest removals of irrelevant sections +4. Edit the SKILL.md files in-place at the installation target (NOT the source repo) +5. Fix any path issues found in Step 4 + +### If optimizing rules: +1. Read each installed rule .md file +2. Ask the user about their preferences: + - Test coverage target (default 80%) + - Preferred formatting tools + - Git workflow conventions + - Security requirements +3. Edit the rule files in-place at the installation target + +**Critical**: Only modify files in the installation target (`$TARGET/`), NEVER modify files in the source ECC repository (`$ECC_ROOT/`). + +--- + +## Step 6: Installation Summary + +Clean up the cloned repository from `/tmp`: + +```bash +rm -rf /tmp/everything-claude-code +``` + +Then print a summary report: + +``` +## ECC Installation Complete + +### Installation Target +- Level: [user-level / project-level / both] +- Path: [target path] + +### Skills Installed ([count]) +- skill-1, skill-2, skill-3, ... + +### Rules Installed ([count]) +- common (8 files) +- typescript (5 files) +- ... + +### Verification Results +- [count] issues found, [count] fixed +- [list any remaining issues] + +### Optimizations Applied +- [list changes made, or "None"] +``` + +--- + +## Troubleshooting + +### "Skills not being picked up by Claude Code" +- Verify the skill directory contains a `SKILL.md` file (not just loose .md files) +- For user-level: check `~/.claude/skills//SKILL.md` exists +- For project-level: check `.claude/skills//SKILL.md` exists + +### "Rules not working" +- Rules are flat files, not in subdirectories: `$TARGET/rules/coding-style.md` (correct) vs `$TARGET/rules/common/coding-style.md` (incorrect for flat install) +- Restart Claude Code after installing rules + +### "Path reference errors after project-level install" +- Some skills assume `~/.claude/` paths. Run Step 4 verification to find and fix these. +- For `continuous-learning-v2`, the `~/.claude/homunculus/` directory is always user-level — this is expected and not an error.