cc-plugin-engineering-excellence

Model the end-to-end system, constraints, and failure modes before touching code; use whenever a change spans multiple layers or unclear requirements.

Decompose work into safe, observable increments with feature flags, rollbacks, and communication baked in.

Design every change with traceability, diagnostics, and fast incident triage in mind across mobile, web, and web3 stacks.

Guard latency, memory, battery, bandwidth, and gas/compute budgets by measuring before and after every change.

Deliver changes with clear communication, reviewer-ready context, and follow-up accountability.

Enforce reproducible testing, automated verification, and evidence-driven sign-off before merging any change.

Apply proactive threat modeling, least-privilege design, and safety guardrails before delivering any code or infrastructure change.

Enforces disciplined RED-GREEN-REFACTOR cycle—write failing test first, watch it fail, write minimal code to pass, then refactor.

Use when writing or modifying tests, adding mocks, or considering test-only hooks—prevents common mistakes like testing mocks, polluting production with test helpers, and mocking without understanding dependencies.

Anchor every engineering decision in user value, measurable outcomes, accessibility, and cross-platform experience coherence.

Mandatory checklist before claiming work is complete—run the evidence-producing command, inspect output, and only then state a result.

Startup protocol for every task—discover applicable skills, run them, announce usage, and follow required workflows (brainstorming, TodoWrite checklists, etc.).

Systematic debugging playbook for tracing failures backward through the call chain, adding instrumentation, and fixing bugs at their origin.