菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/mcorbett51090/RavenClaude --skill caching-and-data-access命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | caching-and-data-access |
| description | 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. |
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.