Data Model AI Modeling Professional Rules

When to use this skill

This is an OPTIONAL advanced modeling tool for complex database design. Most simple table creation should use relational-database-tool directly with SQL statements.

ONLY use this skill when you specifically need:

• Complex multi-table relationships with automatic foreign key management
• Visual ER diagram generation for documentation
• Automated field type mapping and constraint generation
• Enterprise-level data model documentation

For most cases, use rules/relational-database-tool/rule.md instead:

• Simple table creation with CREATE TABLE statements
• Basic CRUD operations
• Schema modifications with ALTER TABLE
• Direct SQL execution without Mermaid modeling

Do NOT use for:

• Querying or manipulating existing data (use database skills)
• NoSQL database design (use NoSQL skills)
• Frontend data structures (use appropriate frontend skills)

How to use this skill (for a coding agent)

⚠️ NOTE: This is OPTIONAL. For simple tasks, skip this and use relational-database-tool directly.

When you do use this advanced modeling approach:

1. Optional modeling workflow (only when complexity justifies it)

   • Business analysis phase: Analyze user requirements, identify core entities and relationships
   • Mermaid modeling phase: Create mermaid classDiagram following generation rules
   • Model validation phase: Check completeness, consistency, and correctness

2. Apply generation rules strictly (when using this tool)

   • Use correct type mappings (string, number, boolean, x-enum, etc.)
   • Convert Chinese to English naming (PascalCase for classes, camelCase for fields)
   • Define required(), unique(), display_field() functions when needed
   • Use proper relationship notation with field names