data-modeling-designer

Designs database schemas by analyzing access patterns and applying normalization rules.

Updated May 24, 2026

Search Tags:#schema design #database #data modeling #normalization #storage

Ready to run

npx skills add https://github.com/haJ1t/senior-dev-squad-skills --skill data-modeling-designer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: data-modeling-designer
Source: https://github.com/haJ1t/senior-dev-squad-skills/tree/main/plugins/senior-dev-squad/skills/data-modeling-designer
Command: npx skills add https://github.com/haJ1t/senior-dev-squad-skills --skill data-modeling-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in designing schemas for persistent storage by considering access patterns and invariants, ensuring data models are correct by construction.

Core Features & Use Cases

Schema Design: Design schemas based on access patterns and invariants.
Normalization: Apply normalization rules and justify deviations.
Storage Paradigm: Choose between relational, document, key-value, or hybrid storage.
Constraints and Evolution: Enforce invariants in the schema and plan for schema evolution.
Use Case: When starting a new service, choosing between storage options, or designing or reviewing schemas.

Quick Start

Run the 'data-modeling-designer' skill to create a schema for a new service.

Frequently Asked Questions about data-modeling-designer

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

FAQPage Schema

How do I design a database schema based on access patterns and invariants?▼

Schema design involves analyzing access patterns and invariants, applying normalization rules, and choosing between relational, document, key-value, or hybrid storage paradigms to ensure data integrity and scalability.

What is the best way to apply normalization rules when designing data models?▼

Applying normalization rules involves structuring data to reduce redundancy while justifying deviations when necessary. This ensures your data models remain correct by construction and maintain data integrity across access patterns.

How do I choose between relational, document, and key-value storage paradigms?▼

Choosing between relational, document, key-value, or hybrid storage paradigms requires analyzing your specific access patterns and invariants to determine which model best ensures data integrity and scalability for your service.

How do I enforce invariants and plan for schema evolution in a new service?▼

To enforce invariants and plan for schema evolution, define constraints directly within your schema design. This approach ensures data models remain correct by construction as your service and storage requirements scale.

When do I need to review schema design for persistent storage?▼

You need to review schema design for persistent storage when starting a new service, choosing between storage options, or evaluating existing schemas. This ensures your data models align with current access patterns and invariants.