Practical Notes
- Per README quick start: 28 agents, 125 skills, and 60 commands.
- Keeps both plugin install and
npx ecc <language>steps to distribute rules/commands correctly. - Includes hooks + rules + MCP configs so the harness becomes consistent across tools.
Main
A good way to adopt it without chaos:
- Start with one language profile (e.g.,
npx ecc typescript) and one repo. Don’t roll it out org-wide on day one. - Pick 3–5 commands that match your team’s bottlenecks (planning, TDD, code review, build fix, release notes).
- Enable hooks gradually. Hooks are powerful; start with non-destructive ones (format/lint reminders) before approval gates.
- Treat rules as policy. Keep a short “why” doc explaining what the rules do and when to override.
If you see “Duplicate hooks file”, the README notes it’s usually from a duplicated hooks declaration in a plugin manifest—remove the duplicate entry.
FAQ
Q: Why do I need npx ecc <language> after installing the plugin?
A: Per README: the Claude Code plugin does not automatically distribute rules, so you still need the language install step.
Q: Can I install only parts? A: Yes—README mentions selective install profiles/modules. Start small to avoid workflow churn.
Q: What’s the minimum environment? A: Node.js (README points to package.json requirements, >=18) plus your coding harness of choice.