Menü
Guide users through ECC's current agents, skills, commands, hooks, rules, install profiles, and project onboarding by reading the live repository surface before answering.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.
Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent. Use when adding a capability that does not exist yet.
Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.
Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.
Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.
Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.
| name | ecc-guide |
| description | Guide users through ECC's current agents, skills, commands, hooks, rules, install profiles, and project onboarding by reading the live repository surface before answering. |
| origin | community |
Use this skill when a user needs help understanding, navigating, installing, or choosing parts of Everything Claude Code.
Use this skill when the user:
Answer from current files, not memory. ECC changes quickly, so hard-coded catalog counts, feature lists, and install instructions go stale.
When the ECC repository is available, inspect the relevant files before giving a concrete answer:
node scripts/ci/catalog.js --json
find skills -maxdepth 2 -name SKILL.md | sort
find commands -maxdepth 1 -name '*.md' | sort
find agents -maxdepth 1 -name '*.md' | sort
node scripts/install-plan.js --list-profiles
node scripts/install-plan.js --list-components --json
Use the smallest set of reads needed for the user's question.
README.md: install paths, uninstall/reset guidance, public positioning, FAQsAGENTS.md: contributor guidance and project structureagent.yaml: exported gitagent surface and command listcommands/: maintained slash-command compatibility shimsskills/*/SKILL.md: reusable workflows and domain playbooksagents/*.md: delegated subagent role promptsrules/: language and harness ruleshooks/README.md, hooks/hooks.json, scripts/hooks/: hook behavior and safety gatesmanifests/install-*.json: selective install modules, components, profiles, and target supportdocs/: harness guides, architecture notes, translated docs, release docsLead with the answer, then give the next action. Most users do not need a full catalog dump.
Good first response shape:
Avoid:
Give a short menu:
Point to README.md for install/reset and /project-init for project-specific onboarding.
For "what should I use for X?":
skills/, commands/, and agents/.Useful searches:
rg -n "<query>" skills commands agents docs
find skills -maxdepth 2 -name SKILL.md | sort
Use managed install paths:
node scripts/install-plan.js --list-profiles
node scripts/install-plan.js --profile minimal --target claude --json
node scripts/install-apply.js --profile minimal --target claude --dry-run
For specific skill installs:
node scripts/install-plan.js --skills <skill-id> --target claude --json
node scripts/install-apply.js --skills <skill-id> --target claude --dry-run
Warn users not to stack plugin installs and full manual/profile installs unless they intentionally want duplicate surfaces.
Use /project-init when the user wants ECC configured for a target repo. The expected sequence is:
CLAUDE.md and settings filesAsk for the target harness and install path first, then inspect:
.claude/, .cursor/, .codex/, .gemini/, .opencode/, .codebuddy/, .joycode/, or .qwen/hooks/hooks.jsonFor repo health, suggest:
npm run harness:audit -- --format text
npm run observability:ready
npm test
Use <skill-or-command>. It fits because <reason>.
Canonical file: <path>
Verify with: <command>
Next: <one concrete action>
Best matches:
- <path>: <why it matters>
- <path>: <why it matters>
Recommendation: <which one to use first and why>
Detected: <stack evidence>
Target: <harness>
Plan: <profile/modules/skills>
Dry run: <command>
Would change: <paths>
Needs approval before apply: <yes/no>
/project-init: stack-aware onboarding plan for a target repo/harness-audit: deterministic readiness scorecard/skill-health: skill quality review/skill-create: generate a new skill from local git history/security-scan: inspect Claude/OpenCode configuration security