database-schema-designer

database-schema-designer is a skill for Claude Code, Codex from OneWave-AI/claude-skills. It costs 141 tokens per session (1,452 once invoked), scanned A, original, MIT.

A database design workflow for planning SQL or NoSQL data stores. It maps tables or collections, relationships, indexes, and constraints before implementation.

In plain words
What is it for?
Use it to create schemas, text-based ER diagrams, migration scripts, and database design guidance for systems such as PostgreSQL, MySQL, or MongoDB.
Why use it?
It turns unclear application requirements into a structured data model and reduces problems caused by missing relationships or unsuitable indexes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create schemas, text-based ER diagrams, migration scripts, and database design guidance for systems such as PostgreSQL, MySQL, or MongoDB.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/onewave-ai/claude-skills/database-schema-designer
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.

Any agent
npx skills add OneWave-AI/claude-skills --skill database-schema-designer
Clone the repo
git clone --depth 1 https://github.com/OneWave-AI/claude-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for database-schema-designer

README.md
[![agentmods](https://agentmods.dev/badge/skills/onewave-ai/claude-skills/database-schema-designer/github.svg)](https://agentmods.dev/skills/onewave-ai/claude-skills/database-schema-designer)
Your own site
<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/database-schema-designer"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/database-schema-designer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for database-schema-designer

Your own site · 80×15
<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/database-schema-designer"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/database-schema-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 141 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,452 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk pass 15 Feb 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00141 $0.01452
Opus 5.5 $0.00056 $0.00581
Sonnet 5.5 $0.00028 $0.00290
Haiku 4.5 $0.00014 $0.00145

Measured 1mo ago against content hash 8807c7f705b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

database-schema-designer 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 1mo ago.

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.

database-schema-designer/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Database Schema Designer

Design a schema that enforces the data's rules in the database and makes the app's real queries fast.

Workflow

  1. Collect requirements. Get from the conversation or codebase, and ask only for what blocks the design:

    • Engine and version (default: PostgreSQL 18; check docker-compose.yml, ORM config, or Supabase project if present)
    • Entities and how they relate, in plain language
    • The 5-10 most frequent or most important queries, including filters and sort order
    • Volume and growth (rows per table per year), read/write mix
    • Tenancy (single app, multi-tenant by organization), retention, audit, and compliance needs (PII, deletion requests)
    • ORM or migration tool in use (Prisma, Drizzle, Rails, Django, Alembic, Supabase migrations, plain SQL)
  2. Model entities and relationships. List entities, attributes, and cardinality (1:1, 1:N, N:M). Normalize to 3NF by default; denormalize only for a named query that needs it, and say which.

  3. Choose keys and types using references/postgres.md (or references/other-engines.md for MySQL, SQLite, MongoDB). Defaults for Postgres: bigint generated always as identity or uuid DEFAULT uuidv7() primary keys, text over varchar(n), timestamptz for every timestamp, numeric for money.

  4. Encode the rules as constraints. NOT NULL wherever a value is required, UNIQUE for natural keys, CHECK for ranges and allowed values, foreign keys with a deliberate ON DELETE choice for each. Data rules that live only in app code get broken by the next script or admin fix.

  5. Derive indexes from the queries in step 1, not from a checklist. For each query, name the index that serves it. Index every foreign key column you join or cascade on (Postgres does not do this automatically). Do not add an index a UNIQUE or primary key already provides.

  6. Write the deliverable: DDL, ERD, index rationale, and migrations with rollback, using references/schema-templates.md and the layout in references/output-format.md. Match the user's migration tool if they have one.

Read the full file on GitHub · 62 lines

Files

What ships with it

4 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. 1mo ago Changed · +21 lines · +87 tokens per session 8807c7f705b4
  2. 1mo ago First seen · 41 lines · 54 tokens per session scan A a1ca262a1283

Subscribe to this mod's changes

database-schema-designer is a skill published in the GitHub repository OneWave-AI/claude-skills (376 stars, last pushed 5d ago), licensed MIT. It adds 141 tokens to every session and 1,452 once invoked, about $0.0006 per session on Opus 5.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-09-03.