MySQL Database Design Assistant

Problem

MySQL table designs often suffer from inconsistent naming, arbitrary data types, and weak indexing. This skill targets the design step between business documentation and executable DDL, helping engineers turn entities, fields, status codes, and constraints into a reviewable CREATE TABLE script.

How it works

The workflow is practical rather than generic:

• Use Read or Glob to inspect .md business-rule files and extract entities, fields, enums, status codes, and relationships.
• Analyze existing .sql files to understand legacy schemas and compatibility risks.
• Apply naming and type rules, such as lowercase identifiers, VARCHAR, DECIMAL(M,2), DATETIME, and TINYINT(1).
• Design primary keys, unique business keys, and indexes for high-frequency queries, following the leftmost prefix rule.
• Generate MySQL DDL with column comments, utf8mb4, InnoDB, and no foreign keys, leaving consistency to the application layer.

Boundaries

It is most useful for new table design, schema review, and DDL cleanup on MySQL 5.7/8.0. It does not replace data migration, load testing, or full sharding strategy. If the business-rule document is incomplete, the generated design may miss fields or constraints.