data-model

Design database schemas with entities, relationships, and indexing strategies.

3|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/vndee/engineering-skills --skill data-model-vndee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-model
Source: https://github.com/vndee/engineering-skills/tree/main/.claude/skills/data-model
Command: npx skills add https://github.com/vndee/engineering-skills --skill data-model-vndee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing robust database schemas upfront prevents painful migrations, refactors, and performance pitfalls that frequently arise when data models evolve in production.

Core Features & Use Cases

  • Identify entities and relationships to shape tables and foreign keys.
  • Define attributes with sensible data types and constraints (PKs, defaults, and not-null).
  • Plan indexing strategies and access patterns to support scalable queries.

Quick Start

List the core entities and their key attributes for the domain you are modeling.

Frequently Asked Questions about data-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a database schema to prevent costly migrations later?

Design robust database schemas before migrations by explicitly defining entities, attributes, and relationships upfront. This prevents painful refactors and performance pitfalls by enforcing naming conventions, data types, and indexing decisions early.

What is the best way to model entity relationships and foreign keys for a new domain?

Model entity relationships by identifying core domain entities and mapping their connections to shape tables and foreign keys. Use explicit entity definitions and recommended data-type conventions to structure attributes and constraints effectively.

How do I plan an indexing strategy for scalable database queries?

Plan indexing strategies by evaluating access patterns to support scalable queries. Define sensible data types, constraints, and explicit indexing decisions during schema design to optimize performance before executing migrations.

When do I need to consider soft-delete conventions in database schema design?

Consider soft-delete conventions during database schema design when planning for domain expansions or redesigns. Enforce explicit entity definitions and relationship modeling to handle data retention without costly production refactors.

Does this schema design approach work for existing project redesigns or only new projects?

This schema design approach is applicable to both new projects and existing domain expansions or redesigns. It guides entities, attributes, relationships, and indexing decisions to prevent performance pitfalls when data models evolve.