Contract

• Input: domain requirements and access patterns.
• Output: schema and migration artifact.
• Side effects: none (design only; no DB writes during skill run unless user explicitly runs migration scripts separately).
• Dependencies: none.
• Stop condition: schema and migration plan complete.
• Risk: low.
• Boundary: schema design and migration plan; no direct DB changes unless user executes scripts separately.

Relational DB Design

Design a relational database schema — entities, relations, keys, indexes, constraints — with normalisation, query patterns, and migration planning.

When to use