生产级数据访问解决方案，专门针对 N+1 查询问题。当代码在循环中查询数据库、ORM 逐行延迟加载关联、或者列表端点在 5 行时快但在 50 行时慢时使用。已处理案例见 references/bad-vs-good.md。不适用于 HTTP 契约设计或 Go/JavaScript 语言风格。
该技能定义了生产环境下的数据访问基调，核心规则为：禁止 N+1 查询、禁止在热点路径上使用 SELECT *、查询必须基于索引、大列表必须分页。当 ORM 或循环隐藏了数据库往返次数，导致规则被违反时，本技能提供诊断和解决步骤。它面向使用 Cursor、Claude Code 等 AI 编码工具的开发者，特别适用于后端数据密集型应用。使用时，需先阅读 references/bad-vs-good.md 中的正反案例，了解在集合加载关联、标记映射为急切加载、或将一对多关系联入分页列表时如何避免陷阱。完成标准包括：N 个父记录的列表不会发起 N 次相同的关联查询、查询日志或追踪中语句数量固定（1 或 2 条，或 1 + N/批处理）、分页时每页返回正确的父记录数而非被 join 撑大的行数。
npx skills add https://github.com/backupcompany/skill-cursor/tree/HEAD/skills/data-access规则 03 是底线：禁止 N+1，禁止在热点路径上使用 SELECT *，查询必须由索引支持，大列表必须分页。本技能展示当 ORM 或循环隐藏了数据库往返次数时，该规则如何被违反。
在从集合中加载关联、将映射标记为急切加载、或将一对多关系联入分页列表之前，请先阅读 references/bad-vs-good.md。
This repo contains 3 individual skills — each has its own dedicated page.
Design or review REST/RPC API contracts that are consistent, evolvable, and hard to misuse. Use when defining new endpoints, reviewing an API surface, or resolving naming/versioning/error-shape questions.
Rigorous, severity-ranked review of a diff, PR, or file. Use when you want a thorough check of correctness, security, performance, design, readability, and test coverage with actionable feedback.
Production Go playbook. Use when writing or reviewing Go: errors, goroutines, byte payloads, parsers, and switches on external input. Worked cases are in references/bad-vs-good.md. Do not use for JavaScript, TypeScript, or API-contract design.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".