db-architect

Design normalized database schemas with migrations and indexing for PostgreSQL, MySQL, and SQLite.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mickaelyoshua/dev --skill db-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-architect
Source: https://github.com/mickaelyoshua/dev/tree/main/.claude-skills/db-architect
Command: npx skills add https://github.com/mickaelyoshua/dev --skill db-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designs, creates, and configures robust database schemas that are normalized, scalable, and engine-specific, reducing maintenance and migration risk.

Core Features & Use Cases

  • Schema design and normalization guidance from 3NF principles.
  • Migration planning and engine-specific configuration (PostgreSQL, MySQL, SQLite) plus index strategy.
  • Enforced constraints, foreign keys, and naming conventions to avoid orphaned references and drift.

Quick Start

Describe your entities, relationships, and constraints, and I will generate a normalized schema with migrations.

Frequently Asked Questions about db-architect

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

FAQPage Schema
How do I design a relational database schema that enforces 3NF normalization?

To design a 3NF normalized relational database schema, describe your entities, relationships, and constraints. The system then generates a normalized schema with mandatory foreign keys, explicit ON DELETE behavior, and timestamped created_at/updated_at columns.

Can I use this to generate database schemas for both PostgreSQL and SQLite?

Yes, you can generate database schemas for PostgreSQL, MySQL, and SQLite. The schema design applies engine-specific settings and configurations tailored to each relational database platform to ensure robust execution.

What is the best way to configure foreign keys with explicit ON DELETE behavior?

Configuring foreign keys with explicit ON DELETE behavior requires defining mandatory constraints during schema creation. The design process enforces these explicit deletion rules alongside appropriate indexing to avoid orphaned references and data drift.

Why does database schema drift occur and how can I prevent it?

Database schema drift occurs when naming conventions and foreign key constraints are not explicitly enforced. Prevent drift by generating normalized schemas with mandatory foreign keys, explicit ON DELETE behavior, and clear naming conventions.

Do I need to provide entity relationships to get a normalized database schema?

Yes, you need to provide your entities, relationships, and constraints as input. The system uses these requirements to generate a fully normalized database schema with appropriate indexing and engine-specific configurations.