Stats
Actions
Available In
Tags
Plugin
backend-engineering
Backend-engineering team — 4 agents (backend-architect, service-implementation-engineer, backend-data-access-engineer, backend-reliability-engineer) for the application/service layer behind an API: domain modeling and service boundaries (monolith vs services, where to split), business-logic implementation and error handling, the data-access layer (repository pattern, ORM use, transaction boundaries, killing N+1), caching strategy (cache-aside, invalidation, stampede), background jobs and async messaging (idempotent workers, outbox, DLQs), and backend reliability (timeouts, retries with backoff + jitter, circuit breakers, graceful degradation). Language-agnostic (examples in Node/Python/Go). 6 skills, a decision-tree knowledge bank (service-boundary + cache trees + a dated map), 12 best-practices, 4 templates, 4 commands, 1 advisory hook. Seams: the contract -> api-engineering, the schema/index -> database-engineering, deploy -> devops-cicd. Requires ravenclaude-core@>=0.7.0.
What's Inside
Slash Commands4
Steps
/design-service-boundaries
Decide monolith vs services and draw domain-driven boundaries; choose sync vs async per seam.
Steps
/add-resilience
Add backend resilience: timeouts, idempotent-only backoff+jitter retries, circuit breakers, degraded mode, and idempotent workers with DLQs.
Steps
/implement-service
Implement business logic cleanly: framework at the edges, explicit error modeling, boundary validation, idempotency, outbox.
Steps
/optimize-data-access
Fix data-access issues: kill N+1, set transaction boundaries, add cache-aside with invalidation + stampede protection, outbox.
Agents4
backend-architect
/backend-architect
Use for backend architecture: domain modeling, the monolith-vs-microservices decision (defaulting to a modular monolith), domain-driven service boundaries that own their data, sync-vs-async choice, and per-boundary failure modeling. Contract → api-engineering; schema → database-engineering.
backend-data-access-engineer
/backend-data-access-engineer
Use for the data-access layer: repository/data-mapper pattern, explicit short transaction boundaries (never across HTTP), killing ORM N+1, cache-aside with a defined invalidation trigger and stampede protection, and the transactional outbox for write-then-publish.
backend-reliability-engineer
/backend-reliability-engineer
Use for backend resilience and async processing: timeouts on every outbound call, retries with exponential backoff + jitter for idempotent operations only, circuit breakers and bulkheads, defined graceful-degradation modes, and background-job/worker design.
service-implementation-engineer
/service-implementation-engineer
Use for business-logic implementation: clean service/use-case layering with the framework kept at the edges, explicit error modeling (expected vs bug) mapped to statuses, boundary validation into domain types, idempotency keys for retried operations, and the outbox pattern for write-then-publish.
Skills6
api-contract-testing
/api-contract-testing
Playbook for implementing consumer-driven contract tests (Pact) between backend services so API contract breaks surface in CI before they reach integration environments.
backend-implementation
/backend-implementation
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.
backend-resilience
/backend-resilience
Make the backend survive its dependencies: timeout every outbound call, retry idempotent-only with exponential backoff + jitter, add circuit breakers and bulkheads, define a graceful-degradation mode, and design idempotent background workers with DLQs and backpressure.
caching-and-data-access
/caching-and-data-access
Own the data-access layer: queries behind a repository, short explicit transaction boundaries (never across HTTP), kill ORM N+1 by eager-loading/batching, and cache-aside with a defined invalidation trigger plus stampede (single-flight) protection.
error-handling-and-result-modeling
/error-handling-and-result-modeling
Playbook for modeling and propagating errors in backend services — typed result/error envelopes, failure classification, HTTP status mapping, error translation at layer boundaries, and client-safe vs internal error separation. Prevents exception-driven spaghetti and accidental information leakage.
Stats
Version0.3.4
LanguageHTML
Stars4
Forks1
MaintenanceExcellent
LicenseMIT
Last Commit
Added
Available In
Safety Signals
Caution
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
