e2ec-it
16 verified skills
sp-writing-plans
SUPERPOWERS-style implementation planning: turn an approved design into 2–5 minute tasks with exact file paths, commands, verifications, and frequent commits.
content-media
crush/skills/ecc-tdd
# ECC TDD Workflow Default cycle: 1) Write/extend tests (failing) 2) Implement minimal code to pass 3) Refactor (only after green) 4) Re-run tests and lint Checklist: - Tests cover: happy path, edge cases, error cases - Deterministic: no time/network flakes unless mocked - Clear assertions; avoid over-mocking If tests are expensive: - Add a fast unit layer first - Add integration/E2E only where needed
development
crush/skills/ecc-api-design
# 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
development
crush/skills/ecc-code-review
# ECC Code Review Review checklist: - Correctness: logic matches requirements; handles errors; no silent failure - Readability: naming, small functions, clear invariants - Tests: coverage for new behavior; no brittle tests - Performance: no obvious N+1, unbounded loops, large allocations - DX: helpful logs; clear errors; docs updated if needed Provide: - Must-fix items - Nice-to-have improvements - Suggested patch/diff if practical
development
crush/skills/ecc-cost-aware-llm
# ECC Cost-Aware LLM Workflow Rules: - Choose smallest capable model for the job - Cache and reuse results where feasible - Avoid sending large logs/blobs; summarize first - Track token usage and set budgets Practical: - Add logging for prompt+response sizes (sanitized) - Add "budget exceeded" fallback behavior - Provide a test mode that uses a cheaper model
testing
crush/skills/ecc-deployment
# ECC Deployment Patterns Checklist: - Health checks (readiness/liveness) + timeouts - Rollback plan (previous image/tag, config rollback) - Migrations: forward-only or safe rollback strategy - Observability: logs, metrics, alerting basics - Release: staged rollout if possible (canary/blue-green) Artifacts to produce: - A deploy script template with rollback - A short runbook (how to deploy, verify, rollback)
testing
crush/skills/ecc-docker
# ECC Docker Patterns Compose checklist: - Named volumes for persistent data - Explicit networks; avoid "host" unless necessary - Healthchecks for key services - Resource limits where possible - Avoid baking secrets into images; use env / secret mounts If debugging: - Check container logs - Verify ports and DNS on the compose network - Validate volume permissions
development
crush/skills/ecc-planner
# ECC Planner Use this when: - The user asks for a feature or refactor and you need a safe plan. Output format: 1) Goal (1-2 lines) 2) Assumptions (bullets) 3) Plan (numbered steps, each verifiable) 4) Acceptance criteria (bullets) 5) Risk list + mitigations 6) Test plan (commands or steps) Rules: - Prefer smallest viable change. - Identify files likely to change before editing. - Call out migrations, env vars, and rollback steps explicitly.
development
crush/skills/ecc-security-review
# ECC Security Review Checklist: - Input validation and output encoding - AuthN/AuthZ boundaries (who can call what) - Secrets: no hardcoded tokens/keys; env vars only - Dependency risk: check lockfile changes; prefer pinned versions - SSRF / RCE vectors (URLs, file paths, shells) - SQL/NoSQL injection checks Deliver: - Top risks + severity - Concrete mitigations - Tests for the highest-risk paths
development
sp-brainstorming
SUPERPOWERS-style brainstorming: MUST run before implementing features/behavior changes. Clarify intent, propose options, present design, get approval.
data-ai
sp-executing-plans
Execute a written plan in batches with checkpoints; stop on blockers; finish via sp-finish-branch.
testing
sp-finish-branch
Finish development branch: verify tests, present 4 options (merge/PR/keep/discard), then cleanup worktree safely.
development
sp-git-worktrees
Create isolated worktree for feature work; verify ignore rules; run baseline tests before work.
testing
sp-request-code-review
Request review between tasks and before merge. Use git SHAs to scope changes and produce actionable findings.
development
sp-subagent-dev
Execute plan per task with role separation and review loops (spec then quality). In Crush, simulate subagents via role prompts / new sessions.
development
sp-tdd
SUPERPOWERS TDD enforcement: NO production code without a failing test first. Delete code written before tests.
development