From backend-engineering
Implement business logic cleanly: keep the framework at the edges with logic in testable use-cases, model errors explicitly (expected vs bug), validate inputs into domain types at the boundary, add idempotency keys for retried operations, and use the outbox for write-then-publish.
How this skill is triggered — by the user, by Claude, or both
Slash command
/backend-engineering:backend-implementationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Logic in plain testable use-cases; HTTP/ORM/framework in thin adapters. A controller full of rules is untestable.
Logic in plain testable use-cases; HTTP/ORM/framework in thin adapters. A controller full of rules is untestable.
Distinguish expected failures (validation/not-found/conflict) from bugs; typed results mapped to status at the edge. No bare catch-all.
Parse-and-validate inputs into domain types; the core works with valid data.
Dedup key for retried work (webhooks/payments/async). Outbox: write the event in the same transaction as the state change so you never publish for a rolled-back write.
npx claudepluginhub mcorbett51090/ravenclaude --plugin backend-engineeringGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.