database-schema-design
Document or design a database schema with entity relationships, table definitions, constraints, indexes, and access patterns. Use when asked to design a database, document an existing schema, model entities and relationships, define table structures, plan an index strategy, or produce a data model for review. Produces a structured schema document covering an ER diagram, table DDL definitions, index strategy, access pattern analysis, normalization decisions, and migration notes.
npx skills add mohitagw15856/pm-claude-skills --skill database-schema-design --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Database Schema Design Skill Produce a complete database schema design document for a given domain. A schema document is not just a list of tables — it is a record of decisions: what was modelled, how entities relate, which queries the schema is optimised for, and what trade-offs were made. A good schema design document lets an engineer understand the data model, query it correctly, extend it safely, and write migrations without breaking things. ## Required Inputs Ask for these if not already provided: - **Domain description** — what the system does; what business objects are being modelled - **Entities and relationships** — the main things in the domain and how they relate (e.g. "a User has many Orders; an Order has many OrderItems; an OrderItem references a Product") - **Expected query patterns** — the most important read and write queries (e.g. "fetch all orders for a user, sorted by date"; "look up a product by SKU") - **Database engine** — PostgreSQL, MySQL, SQLite, CockroachDB, etc. — this affects DDL syntax and available types - **Expected data volume** — approximate row counts, growth rate, and any partitioning needs - **Constraints** — any existing conventions, naming st
- Required Inputs
- Output Format
- 1. Overview
- 2. Entity Relationship Diagram
- 3. Table Definitions
- organisations
- users
- [tablea]
- [jointable] (Many-to-many)
- 4. Index Strategy
- 5. Access Pattern Analysis
- AP-1: Fetch all active users for an organisation (paginated)
- AP-2: Look up a user by email (case-insensitive)
- AP-3: Fetch [tablea] items for a user by status
What does the database-schema-design skill do?
Document or design a database schema with entity relationships, table definitions, constraints, indexes, and access patterns. Use when asked to design a database, document an existing schema, model entities and relationships, define table structures, plan an index strategy, or produce a data model for review. Produces a structured schema document covering an ER diagram, table DDL definitions, index strategy, access pattern analysis, normalization decisions, and migration notes.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill database-schema-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.