AGENT SKILL

ecc

Routing entry point for the ECC (Everything Claude Code) bundle from affaan-m/ECC: 293 skills, 68 subagents, 94 slash commands, and 122 rule files covering software-delivery practice — TDD, code review, security review, architecture, Python/TypeScript/Go conventions, git workflows, and agent tooling. Use when a task is about engineering process rather than product design: refactor plans, review passes, debugging discipline, release prep, or writing tests. For pure UI/design work prefer impeccable, taste-skill, or ui-ux-pro-max instead.

License 许可
MIT
最近更新
2026-10-31
Stars
★ 0
Forks
0

01 前言 Front Matter

name
ecc
description
Routing entry point for the ECC (Everything Claude Code) bundle from affaan-m/ECC: 293 skills, 68 subagents, 94 slash commands, and 122 rule files covering software-delivery practice — TDD, code review, security review, architecture, Python/TypeScript/Go conventions, git workflows, and agent tooling. Use when a task is about engineering process rather than product design: refactor plans, review passes, debugging discipline, release prep, or writing tests. For pure UI/design work prefer impeccable, taste-skill, or ui-ux-pro-max instead.

02 资源文件 290

03 SKILL.md 正文

ECC

Vendored from affaan-m/ECC v2.2.3 (MIT).

This is a multi-harness bundle, so it is kept nested instead of flattened into .agent/skills/. Read the directory the task calls for rather than loading all of it.

skills/     293 skills, one directory each, with its own SKILL.md
agents/     68 subagent definitions (code reviewer, security auditor, …)
commands/   94 slash commands
rules/      122 always-on rule files

Picking one

  • Review a change → skills/code-review, agent agents/code-reviewer.md.
  • Harden something before release → skills/security-review.
  • Plan a refactor → skills/ entries matching the language or domain you are in.
  • Anything about how the UI looks → not here. Use impeccable, taste-skill, ui-ux-pro-max, design-motion-principles, or awesome-design-md.

The per-directory SKILL.md frontmatter is the index; grep it rather than browsing:

grep -l "description:.*review" .agent/skills/ecc/skills/*/SKILL.md

Two deviations from upstream

  1. skills/design-system/ is renamed to skills/ecc-design-system/ (frontmatter name: updated to match) because this repo already ships an unrelated design-system skill in .agent/skills/.
  2. CLAUDE.md and .claude-plugin/ are kept for reference. The hooks ECC defines need a harness plugin install; nothing here loads them.

Assets, docs (including 6 translated copies), tests, Docker, and the other harness ports (.cursor, .kiro, .codex, .opencode, pi/, ecc2/) are not vendored.

04 同仓库更多 Skills

paooll
paooll/mobileappproj

ui-styling

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

★ 0
paooll
paooll/mobileappproj

ponytail

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

★ 0
paooll
paooll/mobileappproj

verification-loop

Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS/FAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.

★ 0
paooll
paooll/mobileappproj

returns-reverse-logistics

Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.

★ 0
paooll
paooll/mobileappproj

recursive-decision-ledger

Run repeated rollouts ("Prime Gauss" style recursive prompting) while keeping an append-only decision ledger of trials, marks, coherence checks, and promotion gates, so recursive confidence never auto-approves live trading, deploy, or destructive actions. Use when the user asks for repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail.

★ 0
paooll
paooll/mobileappproj

quality-nonconformance

Quality control and non-conformance management for regulated manufacturing (FDA 21 CFR 820, IATF 16949, AS9100): NCR lifecycle and disposition, 5-Why/Ishikawa/fault-tree/8D root cause analysis, CAPA systems, SPC interpretation, AQL sampling, and supplier quality audits. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.

★ 0