database-schema-designer

Design SQL and NoSQL database schemas with ERD generation and migration scripts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/engmiguelamaral-png/Arquitetos --skill database-schema-designer-engmiguelamaral-png
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-schema-designer
Source: https://github.com/engmiguelamaral-png/Arquitetos/tree/main/database-schema-designer
Command: npx skills add https://github.com/engmiguelamaral-png/Arquitetos --skill database-schema-designer-engmiguelamaral-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designs optimized database schemas for SQL and NoSQL systems, enabling scalable data architectures and maintainable models.

Core Features & Use Cases

  • SQL schema design: Identifies entities, attributes, primary keys, foreign keys, relationships, normalization to 3NF, and indexing strategy.
  • NoSQL schema planning: Designs document-based schemas aligned to access patterns, embedding vs referencing, and denormalization guidance.
  • ER diagrams & migrations: Generates ERDs and migration scripts to evolve schemas safely in production.
  • Use case: When building a data-heavy application, design a scalable, auditable schema that supports expected queries and growth.

Quick Start

Generate a complete, production-ready database schema for a specified domain, including tables, relationships, constraints, and a sample migration plan.

Frequently Asked Questions about database-schema-designer

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

FAQPage Schema
How do I design a scalable database schema for a data-heavy application?

Design a scalable database schema by identifying entities, attributes, primary and foreign keys, and applying normalization to 3NF. This process includes defining relationships, enforcing indexing strategies, and generating an ER diagram to visualize the data architecture.

What is the best way to model NoSQL data for specific access patterns?

Model NoSQL data by designing document-based schemas aligned to your expected access patterns. This involves choosing between data embedding and referencing, and applying denormalization guidance to optimize query performance for scalable systems.

How do I generate migration scripts to evolve my SQL schema safely?

Generate migration scripts to evolve SQL schemas safely by planning robust migration strategies alongside schema design. This ensures production environments can apply structural changes without downtime or data loss.

Does database schema design work for both SQL and NoSQL systems?

Yes, database schema design works for both SQL and NoSQL systems. It covers SQL normalization and indexing alongside NoSQL document-based schema planning, embedding versus referencing, and denormalization guidance.

When do I need to use normalization and ER diagrams for database modeling?

Use normalization and ER diagrams when building data-heavy applications that require maintainable and auditable data models. Normalization to 3NF reduces data redundancy, while ER diagrams map out entities and relationships.

Why should I use embedding versus referencing in NoSQL schema design?

Use embedding versus referencing in NoSQL schema design to align document structures with specific access patterns. Embedding optimizes read performance by grouping related data, while referencing prevents data duplication during updates.