Efficient AI Coding with Claude Code: Essential ECC Tools and Minimal Install

Pre‑install: consult for precise selection

Run the consult command to describe the development scenario and obtain a recommended profile (minimal or core) and a list of rules, skills, and agents to install.

git clone https://github.com/affaan-m/everything-claude-code.git
cd everything-claude-code
npm install
node scripts/ecc.js consult "Claude Code daily development, TypeScript + Vue, front‑end feature iteration, prioritize code standards and review, no complex hooks or multi‑agent orchestration" --target claude
# or
npx ecc consult "Claude Code daily development, TypeScript + Vue, front‑end feature iteration, prioritize code standards and review, no complex hooks or multi‑agent orchestration" --target claude

Use the repository’s node scripts/ecc.js consult because the published npm package ecc-universal may not contain the latest consult command.

Operation flow:

Run the command.

Review the output: recommended profile, items to install, preview of file changes.

Confirm and execute the provided installation command.

Consultation avoids installing unnecessary slash commands and reduces conflicts with existing plugins.

Sample output:

Six core AI‑coding functions (ordered by frequency)

1. Rules (language + generic)

Rules enforce project code style, error‑handling conventions, and prohibited patterns, reducing rework.

# Plugin path: manually copy rules
git clone https://github.com/affaan-m/everything-claude-code.git
cd everything-claude-code
mkdir -p ~/.claude/rules/ecc
cp -R rules/common ~/.claude/rules/ecc/
cp -R rules/typescript ~/.claude/rules/ecc/
# Minimal profile via script
./install.sh --profile minimal --target claude

After installation the rules are active automatically. Verify with /help or the command palette.

2. search‑first skill

Forces a global search and call‑chain read before code modification, preventing “one change breaks three places”.

# Preview plan
./install.sh --profile minimal --target claude --with skill:search-first --dry-run
# Install
./install.sh --profile minimal --target claude --with skill:search-first
# or via consult
npx ecc consult "search-first skill" --target claude

Typical workflow:

Trigger /search-first.

Describe the feature to modify.

AI returns search results and impact analysis; confirm before code generation.

An impact report is recorded automatically.

3. Reviewer / Code‑review agent

Encapsulates senior‑engineer review as a repeatable agent, suitable for small‑step PR workflows.

# Dry run
./install.sh --profile minimal --target claude --with agent:code-reviewer --dry-run
# Install
./install.sh --profile minimal --target claude --with agent:code-reviewer
# or via consult
npx ecc consult "code reviewer agent typescript vue" --target claude

Usage after lint/build:

Open Claude Code’s command palette and select the Reviewer Agent.

Provide a prompt, e.g.:

请 review 这个 PR：文件列表 [列出]，重点关注：调用链影响、类型安全、错误处理一致性。

AI returns a structured review report.

4. Quality‑gate / harness‑audit commands

One‑click validation of acceptance criteria and gate checks.

# Install with minimal profile (commands are part of core set)
./install.sh --profile minimal --target claude --dry-run
./install.sh --profile minimal --target claude

Run before a release or major change:

/quality-gate
/harness-audit --strict

The output lists failed gates and can serve as a PR checklist.

5. Documentation‑lookup / pattern skills

Provides API references and project‑specific conventions, reducing hallucinations.

# Install TypeScript language pack
./install.sh --profile minimal --target claude --with lang:typescript --dry-run
./install.sh --profile minimal --target claude --with lang:typescript
# or via consult
npx ecc consult "documentation lookup + vue patterns + typescript best practices" --target claude

Typical usage:

/docs-lookup "Vue 3.4 Composition API best practices"

6. Minimal hooks + environment‑variable control

Hooks are the most conflict‑prone component; install with the minimal profile and enable only when needed.

# Add hooks later
./install.sh --target claude --modules hooks-runtime
# Runtime control without uninstall
ECC_HOOK_PROFILE=minimal claude
ECC_DISABLED_HOOKS=session-start,pre-commit claude

Default is “install and forget”; downgrade only if problems arise.

Full installation process (recommended order)

Inventory existing Claude Code plugins and slash commands.

Run consult to obtain a recommendation list.

Choose a single installation path: either install.sh or the plugin marketplace (not both).

Install only the six core items listed above.

Validate by opening Claude Code, running /help, and testing a small code snippet to confirm rules.

Document the mapping “command → source → usage” in docs/ECC‑installed‑list.md.

Hard rules for coexistence with existing plugins

Keep only one implementation of the same capability (e.g., if a review skill already exists, do not install ECC’s Reviewer Agent).

Rules can be stacked because they are read‑only.

Hooks are the most dangerous; downgrade to minimal immediately when issues appear.

Periodically uninstall any slash command or skill not used in the past month.

Daily AI‑coding closed loop (standard process after ECC)

Requirement slicing (input/output + acceptance criteria).

Trigger search-first skill for AI requirement analysis.

Write code (rules apply automatically).

Run local lint / build / test.

Trigger Reviewer Agent for self‑inspection.

Run quality-gate when needed.

Small PR + write‑back change record.

Three immediate steps

Clone the ECC repository, run npm install, then execute node scripts/ecc.js consult "your stack and needs". Compare the output with ./install.sh ... --dry-run to preview file changes.

If the recommendation list contains items unrelated to your stack, do not execute the first “Install” command blindly.

Choose a single installation path. For plugin installation, copy rules/common and language packs to ~/.claude/rules/ecc/. For script installation, use --profile minimal and incrementally add --with skill:search-first, --with agent:code-reviewer, etc.

Conclusion

Installing the six high‑frequency capabilities—Rules, search‑first, Reviewer Agent, Quality‑gate, Documentation‑lookup, and minimal Hooks—provides a stable AI‑coding workflow: requirement → impact analysis → coding → review → quality gate → PR. Additional ECC features can be added later as needed.