/configure-ecc

name: configure-ecc
description: Interactive installer for awesome claude notes — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.
origin: ECC

Configure awesome claude notes (ECC)

An interactive, step-by-step installation wizard for the awesome claude notes 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 awesome-claude-notes` — 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`:

rm -rf /tmp/awesome-claude-notes
git clone https://github.com/loulanyue/awesome-claude-notes.git /tmp/awesome-claude-notes

Set `ECC_ROOT=/tmp/awesome-claude-notes` 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:

mkdir -p $TARGET/skills $TARGET/rules

---

Step 2: Select & Install Skills

2a: Choose Scope (Core vs Niche)

Default to **Core (recommended for new users)** — copy `.agents/skills/*` plus `skills/search-first/` 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).

Use `AskUserQuestion` (single select):

Question: "Install core skills only, or include niche/framework packs?"
Options:
  - "Core only (recommended)" — "tdd, e2e, evals, verification, research-first, security, frontend patterns, compacting, cross-functional Anthropic skills"
  - "Core + selected niche" — "Add framework/domain-specific skills after core"
  - "Niche only" — "Skip core, install specific framework/domain skills"
Default: Core only

If the user chooses niche or core + niche, continue to category selection below and only include those niche skills they pick.

2b: Choose Skill Categories

There are 7 selectable category groups below. The detailed confirmation lists that follow cover 45 skills across 8 categories, plus 1 standalone template. Use `AskUserQuestion` with `multiSelect: true`:

Question: "Which skill categories do you want to install?"
Options:
  - "Framework & Language" — "Django, Laravel, Spring Boot, Go, Python, Java, Frontend, Backend patterns"
  - "Database" — "PostgreSQL, ClickHouse, JPA/Hibernate patterns"
  - "Workflow & Quality" — "TDD, verification, learning, security review, compaction"
  - "Research & APIs" — "Deep research, Exa search, Claude API patterns"
  - "Social & Content Distribution" — "X/Twitter API, crossposting alongside content-engine"
  - "Media Generation" — "fal.ai image/video/audio alongside VideoDB"
  - "Orchestration" — "dmux multi-agent workflows"
  - "All skills" — "Install every available skill"

2c: 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 (21 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 | | `laravel-patterns` | Laravel architecture patterns: routing, controllers, Eloquent, queues, caching | | `laravel-security` | Laravel security: auth, policies, CSRF, mass assignment, rate limiting | | `laravel-tdd` | Laravel testing with PHPUnit and Pest, factories, fakes, coverage | | `laravel-verification` | Laravel verification: linting, static analysis, tests, security scans | | `frontend-patterns` | React, Next.js, state management, performance, UI patterns | | `frontend-slides` | Zero-dependency HTML presentations, style previews, and PPTX-to-web conversion | | `golang-patterns` | Idiomatic Go patterns, conventions for robust Go applications | | `golang-testing` | Go testing: table-driven tests, subtests, benchmark