What problem does it solve? Designing a database schema from scratch is error-prone: unclear entity boundaries, missing constraints, and poorly planned relationships lead to data inconsistency and costly rework. This Skill turns a System Requirement Masterplan into a complete, migration-ready database design for PostgreSQL and Laravel. ## Core Features & Use Cases - Entity & Relationship Design: Identifies core entities, defines One-to-One, One-to-Many, Many-to-Many, and Polymorphic relationships, and specifies pivot tables and foreign keys. - Business Rules & Constraints: Embeds business logic at the database layer (uniqueness, delete protection, audit logs) so data stays consistent even if the application layer fails. - Laravel Migration Guidance: Provides table creation order, FK/index/pivot naming conventions, and Seeder/Factory suggestions, delivered as a database-design.md document. - Use Case: After finishing architecture planning with /architect, run /database to produce a full schema for an e-commerce system — tables, relationships, constraints, and migration suggestions — ready for developers to implement immediately. ## Quick Start Invoke the /database command with the system you want to design, for example "/database ระบบจองห้องประชุม", and attach your requirement masterplan if available.