What problem does it solve?
This Skill turns plain-language domain requirements into a precise relational data model, reducing schema ambiguity and helping teams define the persistence layer before implementation begins.
Core Features & Use Cases
- Entity Modeling: Identifies tables, columns, keys, and relationships from business descriptions or plan artifacts.
- Constraint and Index Design: Adds practical constraints, defaults, and indexes based on the target database and expected access patterns.
- Design Rationale: Documents trade-offs, normalization choices, and migration ordering so downstream implementation stays consistent.
- Use Case: A team describing users, projects, tasks, and tags can use this Skill to produce a reviewable schema spec that Feature and Implement skills can follow without guessing.
Quick Start
Provide the domain description, target database, and any project memory or plan context, and ask this Skill to draft the relational data model.