database-design

Codify database schema naming, typing, and indexing conventions.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/codernai14-source/Forgex --skill database-design-codernai14-source
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/codernai14-source/Forgex/tree/main/.cursor/skills/database-design
Command: npx skills add https://github.com/codernai14-source/Forgex --skill database-design-codernai14-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Addresses inconsistent database schemas by codifying naming, typing, and indexing conventions.

Core Features & Use Cases

  • Naming conventions for tables, fields, and indexes to enforce consistency across modules (sys_, fx_, biz_)
  • Data type guidance for numeric, string, date, and boolean with practical examples
  • Indexing and performance best practices including naming, coverage, and left-prefix considerations
  • Common table templates and field sets (id, create_time, update_time, create_by, update_by, deleted) plus tenant_id when required
  • Change-management and documentation standards to track schema evolution

Quick Start

Define a new table using standard prefixes (sys_, fx_, biz_), include the common fields (id, create_time, update_time, create_by, update_by, deleted), and apply appropriate data types and indexes as shown.

Frequently Asked Questions about database-design

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

FAQPage Schema
What are standard MySQL naming conventions for tables, fields, and indexes?▼

Standard MySQL naming conventions use prefixes like sys_, fx_, and biz_ to categorize tables by module. Fields and indexes follow consistent naming rules to enforce schema consistency across multi-module systems.

How do I design a MySQL database schema with common fields and data types?▼

Design a MySQL schema by including common fields like id, create_time, update_time, create_by, update_by, and deleted, plus tenant_id when required. Apply standardized data types for numeric, string, date, and boolean values.

What are the best practices for MySQL indexing strategy and left-prefix rules?▼

MySQL indexing best practices include following standardized index naming conventions, ensuring proper index coverage, and applying left-prefix considerations to optimize query performance across your database tables.

How do I document and manage MySQL schema changes across evolving modules?▼

Manage MySQL schema evolution by applying change-management and documentation standards that track schema modifications. This ensures a repeatable process for maintaining consistency across multi-module systems.

Does this database design guidance support multi-tenant systems?▼

Yes, the schema design conventions support multi-tenant systems by requiring a tenant_id field in the common table templates alongside standard fields like id, create_time, update_time, and deleted.