菜单
Use when setting up a Lux app, designing tables, writing CRUD or query code, choosing SDK versus HTTP or RESP access, generating types, or using local development.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/lux-db/lux --skill surface-parity命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | surface-parity |
| description | Use when setting up a Lux app, designing tables, writing CRUD or query code, choosing SDK versus HTTP or RESP access, generating types, or using local development. |
Start with the requested integration's minimal runnable path. Verify every runnable TypeScript import, method signature, and exported type in public docs or installed public types before emitting it. The only SDK package paths are @luxdb/sdk, @luxdb/sdk/browser, and @luxdb/sdk/ssr; do not invent names from ecosystem memory. Choose one public access path per boundary. Use createBrowserClient for browser app calls, createClient for trusted server calls, direct Lux or another Redis client for trusted RESP workloads, and HTTP only when an SDK is unsuitable. Do not expose direct credentials or secret keys to clients.
For tables, model constraints in a migration, then use table<T>() or createClient<Database>(). Check each { data, error } response. Use filters for update() and delete(), row(pk) for known primary keys, and upsert(..., { onConflict }) only when conflict behavior is desired. Run lux types after applying schema changes.
For local reproduction use lux init, lux start, lux migrate plan, and lux migrate run; use lux start --fresh only when dropping local state is acceptable. Route versioned schema changes, grants, live subscriptions, push, and operations to their dedicated Workbench.
