db-logical-design

Define relational schemas with keys, constraints, and referential integrity.

7|Updated Feb 14, 2026

Search Tags:#design #database #schema #integrity #constraints #data-modeling #relational

Ready to run

npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill db-logical-design

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: db-logical-design
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/db-logical-design
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill db-logical-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Logical database design workflow for table structure, key strategy, constraints, and relational consistency. Use when durable schema semantics must be defined before physical tuning; do not use for query-only optimization tasks.

Core Features & Use Cases

Define keys, unique constraints, and relationship cardinality to preserve data identity across the schema.
Enforce referential integrity and cascade behavior to maintain consistent data lifecycle.
Plan migrations and lifecycle columns (created/updated/deactivated) to support evolution and auditing.

Quick Start

Start by mapping your domain concepts to relational tables, then specify keys, constraints, and lifecycle columns to establish a durable schema.

Frequently Asked Questions about db-logical-design

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

FAQPage Schema

How do I design a relational database schema with proper data integrity constraints?▼

Design relational database schemas by mapping conceptual entities to tables, defining primary and alternate keys, and enforcing constraints to preserve data identity and integrity.

What is the best way to enforce referential integrity and cascade behavior in a database?▼

Enforce referential integrity by defining relationship cardinality and cascade rules across tables, maintaining consistent data lifecycle and consistent relational structures.

When do I need logical database design versus physical tuning?▼

Use logical database design when durable schema semantics must be defined before physical tuning; do not use it for query-only optimization tasks.

How do I map domain concepts to relational tables for data modeling?▼

Map domain concepts to relational structures to establish a durable schema, specifying keys, constraints, and lifecycle columns to support data evolution and auditing.

How do I plan database migrations with lifecycle audit columns?▼

Plan migrations and lifecycle columns including created, updated, and deactivated timestamps to support database schema evolution and lifecycle auditing.