ECC skills and rules: how to install only what your stack needs
To install only the ECC skills and rules you need, start from the minimal profile and add components with --with (for example --with framework:nextjs) or --skills tdd-workflow,security-review; for rules, copy only rules/common and your language's folder into .claude/rules/ecc/. That way the agent does not load hundreds of descriptions it will never use.
This is part 5 of the complete ECC guide. Below: how the 406-component catalog is organized, the difference between skills and rules, how to add a specific framework, which skills are most useful and how to scope rules to one project.
Skills and rules: what each one is
| Skills | Rules | |
|---|---|---|
| What they are | Procedures the agent loads when needed | Standards loaded always or when certain files are touched |
| Where they live | `~/.claude/skills/<name>/SKILL.md` | `~/.claude/rules/` or the project's `.claude/rules/` |
| Context cost | Only their description, until used | Their full text, whenever loaded |
| Example | `tdd-workflow`: the TDD steps | `common/testing.md`: "minimum 80% coverage" |
If skills are new to you, start with the Claude Code skills guide. The key point: skills are cheap until used; rules cost every time they load.
The catalog: 406 components in 7 families
ECC's installer works with components, not loose files. We listed them with the CLI:
node scripts/catalog.js components| Family | Count | What it groups |
|---|---|---|
| `skill:` | 328 | A single skill (`skill:tdd-workflow`) |
| `capability:` | 23 | A themed bundle: `security`, `database`, `research`, `content`, `media`, `social`… |
| `lang:` | 14 | TypeScript, Python, Go, Java, Swift, C++, C, Kotlin, ArkTS, Perl, Ruby, Rust, C#, F# |
| `framework:` | 9 | Angular, React, Vue, Next.js, Django, Spring Boot, Quarkus, Rails, Laravel |
| `locale:` | 13 | Documentation translations |
| `agent:` | 13 | Standalone agents you can add |
| `baseline:` | 6 | The foundations: rules, hooks, commands, config |
To inspect one: node scripts/catalog.js show framework:nextjs.
Add just your framework with --with
We dry-ran the minimal profile alone and with Next.js:
npx ecc-universal@2.2.3 install --profile minimal --target claude --dry-run
npx ecc-universal@2.2.3 install --profile minimal --target claude --with framework:nextjs --dry-run--with framework:nextjs adds the framework-language module (127 more files). You can chain several: --with framework:nextjs --with capability:security. For specific skills by name, the repository installer accepts --skills:
./install.sh --target claude --skills tdd-workflow,security-review,e2e-testingIf you are unsure which component fits, consult suggests candidates from plain language. As we saw in part 4, it matches keywords and sometimes picks the wrong stack: check its list before installing.
The skills most worth having
Out of 328, these are the ones you will use in almost any project:
| Skill | What for |
|---|---|
| `search-first` | Research before coding: look through code and docs before inventing |
| `tdd-workflow` | The RED → GREEN → REFACTOR loop we tested in [part 3](/en/ecc-plan-tdd-code-review-workflow) |
| `verification-loop` | Continuous verification, not just at the end |
| `security-review` | Security checklist before a merge |
| `api-design` | REST design: pagination, errors, versioning |
| `database-migrations` | Migrations with Prisma, Drizzle, Django or Go without breaking data |
| `e2e-testing` | End-to-end tests with Playwright and the Page Object Model |
| `deployment-patterns` and `docker-patterns` | CI/CD, health checks, rollbacks and containers |
| `strategic-compact` | When to compact context (covered in part 7) |
Two more keep your collection tidy: skill-stocktake audits the quality of your skills and commands, and /skill-create generates new skills from your git history.
Rules: global or per project
ECC ships rules in 22 folders: common, typescript, python, golang, rust, java, kotlin, swift, php, ruby, cpp, csharp, fsharp, dart, perl, react, react-native, vue, nuxt, angular, arkts and web.
The common ones (coding-style, git-workflow, testing, security, performance, patterns, hooks, agents…) are always loaded, about 2,900 words. Language rules carry paths: in their frontmatter and only load when you touch matching files, as we saw in part 2.
To apply them to one repository only:
cd your-project
mkdir -p .claude/rules/ecc
cp -R /path/to/ECC/rules/common .claude/rules/ecc/
cp -R /path/to/ECC/rules/typescript .claude/rules/ecc/Copy the whole folder, not individual files: rules link to each other and file names repeat across languages (coding-style.md exists in almost all of them).
Read the rules before accepting them
Rules are opinions. common/testing.md demands 80% coverage plus unit, integration and E2E tests for everything. On a prototype that can slow the agent more than it helps. Edit the copies in your project: they are yours, and ECC only updates what it recorded in its install state.
Common mistakes
- Copying
rules/common/*.mdinstead of the folder. Cross-references break. Usecp -R rules/common. - Nesting skills under
~/.claude/skills/ecc/. Claude Code only discovers skills that are direct children of~/.claude/skills/. - Installing
capability:contentorcapability:social"just in case". That is dozens of marketing, investor and social skills. If you code, you do not need them. - Mixing ECC rules with your
CLAUDE.mdwithout reading them. If yourCLAUDE.mdsays one thing about commits and thegit-workflowrule says another, the agent hesitates. Remove what contradicts.
FAQ
Do the skills work in Codex or Cursor? Yes: the catalog is published for several targets (--target codex, --target cursor…), with fewer features than in Claude Code.
Can I delete a skill I do not use? Yes. If ECC installed it, doctor will flag it as missing; ignore that, or uninstall and reinstall without that component.
How many skills should I keep active? There is no official number. For reference, in part 7 we measured that the minimal profile already adds about 12,500 estimated tokens in descriptions alone.
Conclusion
You do not install ECC; you choose from it. Start with minimal, add your framework with --with, copy only your language's rules into the project and read them before accepting them. Part 6 covers the other piece that changes your day most: hooks, memory across sessions and continuous learning.
// source code
Help us grow
codigoagente is free, with no paywalls. If this article helped you, any of these keeps the blog going.
- Share it with someone who'll find it usefulWhatsAppLinkedInXFacebook
- Meet our sponsorSafe Build Labs
More on AI agents

- Skills for your agents
- Claude Code

guide · Marketing psychology guide for AI agents · #3
- Skills for your agents
- Claude Code

guide · Marketing psychology guide for AI agents · #2
- Skills for your agents
- Claude Code