mysql-ddl-conventions

Enforce MySQL DDL conventions for schema design and peer reviews.

5|1|Updated May 9, 2026
One-click install
npx skills add https://github.com/ql-link/LinkRag --skill mysql-ddl-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mysql-ddl-conventions
Source: https://github.com/ql-link/LinkRag/tree/main/.ai/skills/mysql-ddl-conventions
Command: npx skills add https://github.com/ql-link/LinkRag --skill mysql-ddl-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a comprehensive, consistent set of MySQL table naming, indexing, and data-type conventions to streamline database design, review, and maintenance across projects.

Core Features & Use Cases

  • Naming conventions: enforce snake_case for tables and columns, singular table names, and avoidance of mixed-language or pinyin naming.
  • Indexing and constraints guidance: standardized primary keys, index naming with prefixes (idx_, uk_), and guidelines to minimize index count while preserving query performance.
  • Field design and auditing: guidance on primary keys, status enums, numeric counters, and timestamp columns (created_at, updated_at) with proper defaults; longtext usage for large content.
  • DDL templates and comments: provide a ready-to-use create table template with engine/charset and robust COMMENT annotations.
  • Real-world workflows: used when designing new schemas, auditing existing schemas, or documenting database design standards for peer reviews.

Quick Start

Consult the MySQL DDL conventions to draft your next table using snake_case naming, proper primary key, indexed fields, and a compliant DDL template.

Frequently Asked Questions about mysql-ddl-conventions

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

FAQPage Schema
What are the standard MySQL naming conventions for schema design?

Standard MySQL naming conventions enforce snake_case for tables and columns, use singular table names, and require specific index prefixes like idx_ and uk_ to maintain consistent schema design across teams.

How do I write a compliant MySQL DDL template for new tables?

You can use a standardized MySQL DDL template that includes InnoDB engine settings, utf8mb4 charset, proper primary keys, timestamp columns with defaults, and robust COMMENT annotations for table metadata.

What is the best way to name indexes and constraints in MySQL?

The best way to name MySQL indexes is by using standardized prefixes such as idx_ for standard indexes and uk_ for unique constraints, minimizing total index count while preserving query performance.

How do I audit an existing MySQL schema for compliance?

You audit an existing MySQL schema by reviewing field types, primary keys, status enums, numeric counters, and timestamp columns against standardized DDL conventions during peer reviews.

Does this MySQL schema design standard support longtext fields?

Yes, these MySQL DDL conventions support longtext usage for large content storage, alongside standardized primary keys, timestamp defaults, and utf8mb4 charset settings for comprehensive schema compliance.

When do I need to apply standardized DDL conventions to my database?

You need to apply DDL conventions when creating new tables, adding constraints, naming indexes, or documenting database design standards for peer reviews to ensure consistent schema maintenance.