crush/skills/ecc-api-design/SKILL.md
# ECC API Design Guidelines: - Pagination: cursor-based when possible - Errors: stable error codes + human messages - Idempotency for POST where applicable - Validation: reject unknown fields for strict APIs (when safe) - Versioning: prefer additive changes; document breaking changes Deliver: - Endpoint table (method/path/auth) - Example requests/responses - Error schema
npx skillsauth add e2ec-it/pub-xifan-crush-best-practices crush/skills/ecc-api-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guidelines:
Deliver:
content-media
SUPERPOWERS-style implementation planning: turn an approved design into 2–5 minute tasks with exact file paths, commands, verifications, and frequent commits.
development
SUPERPOWERS TDD enforcement: NO production code without a failing test first. Delete code written before tests.
development
Execute plan per task with role separation and review loops (spec then quality). In Crush, simulate subagents via role prompts / new sessions.
development
Request review between tasks and before merge. Use git SHAs to scope changes and produce actionable findings.