Stats
Actions
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)
From backend-engineering
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/backend-engineering:caching-and-data-accessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Persistence behind a repository; no raw ORM in controllers. Transaction boundaries live here — **short**, never spanning an external HTTP call.
Persistence behind a repository; no raw ORM in controllers. Transaction boundaries live here — short, never spanning an external HTTP call.
The #1 ORM perf bug. Eager-load/join/batch what you iterate; detect in tests. SQL-level tuning -> database-engineering.
Read-through; write invalidates/updates; TTL as a safety net. No invalidation story = stale-data generator.
On a hot-key miss, single-flight/lock so a thousand misses don't all hit the DB.
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.