database-design

A guide to designing databases, including tables and relationships, indexes, database choices, ORM choices, and schema changes. An ORM is a tool that lets application code work with database data through programming objects or methods.

In plain words
What is it for?
Use it when choosing a database or ORM, designing tables and relationships, planning indexes, improving slow queries, or preparing safe migrations.
Why use it?
It helps match the database and data structure to the application instead of relying on one default setup.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/misonl/ling/database-design
Any agent
npx skills add MisonL/Ling --skill database-design
Clone the repo
git clone --depth 1 https://github.com/MisonL/Ling

Made for: Claude Code, Codex.

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 468 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00030 $0.00468
Opus 5 $0.00015 $0.00234
Sonnet 5 $0.00006 $0.00094
Haiku 4.5 $0.00003 $0.00047

Measured 2d ago against content hash a13f162269b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

database-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/schema_validator.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/database-design/SKILL.md · 55 lines

What it actually says

数据库设计

学习如何思考(THINK),而非机械复制 SQL 模式。

选择性阅读规则

仅阅读与请求相关的文档! 查阅内容地图,找到所需信息。

文件 描述 阅读时机
database-selection.md PostgreSQL vs Neon vs Turso vs SQLite 选择数据库时
orm-selection.md Drizzle vs Prisma vs Kysely 选择 ORM 时
schema-design.md 范式化、主键、关系设计 设计模式时
indexing.md 索引类型、复合索引 性能调优时
optimization.md N+1 问题、EXPLAIN ANALYZE 查询优化时
migrations.md 安全迁移、Serverless 数据库 模式变更时

[WARN] 核心原则

  • 需求不明确时,主动询问数据库偏好。
  • 根据实际上下文选择数据库与 ORM。
  • 不要任何场景都默认使用 PostgreSQL。

决策检查清单

在设计模式(Schema)之前:

  • 是否已询问数据库偏好?
  • 是否为当前上下文选择了合适的数据库?
  • 是否考虑了部署环境?
  • 是否规划了索引策略?
  • 是否定义了关系类型?

反模式

[FAIL] 为简单应用默认使用 PostgreSQL(SQLite 可能已足够)
[FAIL] 忽略索引设计
[FAIL] 在生产环境中使用 SELECT *
[FAIL] 在结构化数据更优时强行存储 JSON
[FAIL] 忽略 N+1 查询问题


Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 55 lines · 30 tokens per session scan A a13f162269b9

Subscribe to this mod's changes

database-design is a skill published in the GitHub repository MisonL/Ling (9 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 468 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens