data-model-creation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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)

这是一个可选的高级建模工具，用于复杂的数据库设计。大多数简单的表创建应直接使用

relational-database-tool

结合SQL语句。

仅在明确需要以下功能时使用该技能：

带有自动外键管理的复杂多表关系
用于文档的可视化ER图生成
自动化字段类型映射和约束生成
企业级数据模型文档

大多数情况下，请使用
rules/relational-database-tool/rule.md
替代：

使用CREATE TABLE语句创建简单表
基础CRUD操作
使用ALTER TABLE修改Schema
无需Mermaid建模的直接SQL执行

请勿用于：

查询或操作现有数据（使用数据库相关技能）
NoSQL数据库设计（使用NoSQL相关技能）
前端数据结构（使用相应的前端技能）

How to use this skill (for a coding agent)

如何使用该技能（适用于编码Agent）

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

When you do use this advanced modeling approach:

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
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
Use tools correctly (only when you choose this approach)
- Call data model creation tools only for complex multi-entity business requirements
- Use
```
mermaidDiagram
```
  parameter with complete mermaid classDiagram code
- Set
```
publish
```
  to false initially, create then publish separately
- Choose appropriate
```
updateMode
```
  for new or existing models

⚠️ 注意：这是可选工具。对于简单任务，请跳过此工具，直接使用
relational-database-tool
。

当你确实需要使用这种高级建模方法时：

可选建模工作流（仅在复杂度较高时使用）
- 业务分析阶段：分析用户需求，识别核心实体和关系
- Mermaid建模阶段：按照生成规则创建mermaid classDiagram
- 模型验证阶段：检查完整性、一致性和正确性
严格应用生成规则（使用该工具时）
- 使用正确的类型映射（string、number、boolean、x-enum等）
- 将中文名称转换为英文命名（类名使用PascalCase，字段名使用camelCase）
- 必要时定义required()、unique()、display_field()函数
- 使用带有字段名的正确关系表示法
正确使用工具（仅在选择此方法时）
- 仅针对复杂多实体业务需求调用数据模型创建工具
- 使用
```
mermaidDiagram
```
  参数传入完整的mermaid classDiagram代码
- 初始时将
```
publish
```
  设置为false，先创建再发布
- 为新模型或现有模型选择合适的
```
updateMode
```

Quick Decision Guide

快速决策指南

Most Database Tasks →
rules/relational-database-tool/rule.md

✅ Simple table creation
✅ Data queries and modifications
✅ Schema changes
✅ Direct SQL execution

Complex Modeling Only → This rule (
rules/data-model-creation/rule.md
)

🎯 Multi-entity relationship modeling
🎯 Automated foreign key management
🎯 Visual ER diagram generation
🎯 Enterprise documentation

大多数数据库任务 → 使用
rules/relational-database-tool/rule.md

✅ 创建简单表
✅ 数据查询和修改
✅ Schema修改
✅ 直接执行SQL

仅用于复杂建模 → 本规则（
rules/data-model-creation/rule.md
）

🎯 多实体关系建模
🎯 自动化外键管理
🎯 可视化ER图生成
🎯 企业级文档

Data Model AI Modeling Professional Rules

数据模型AI建模专业规则

⚠️ IMPORTANT: Simplified Workflow Recommendation

⚠️ 重要：简化工作流建议

For most database table creation tasks, use
rules/relational-database-tool/rule.md
directly:

Simple table creation:

CREATE TABLE users (id INT PRIMARY KEY, name VARCHAR(255))

Schema modifications:

ALTER TABLE users ADD COLUMN email VARCHAR(255)

Data operations:
```
INSERT
```
,
```
UPDATE
```
,
```
SELECT
```
,
```
DELETE
```

Only use this advanced Mermaid modeling approach when:

You need automated relationship management
Complex multi-table schemas with foreign keys
Enterprise documentation requirements
Visual ER diagram generation

This rule exists for complex modeling scenarios, but most development should use direct SQL execution.

大多数数据库表创建任务，请直接使用
rules/relational-database-tool/rule.md
：

创建简单表：

CREATE TABLE users (id INT PRIMARY KEY, name VARCHAR(255))

修改Schema：

ALTER TABLE users ADD COLUMN email VARCHAR(255)

数据操作：
```
INSERT
```
、
```
UPDATE
```
、
```
SELECT
```
、
```
DELETE
```

仅在以下情况使用这种高级Mermaid建模方法：

需要自动化关系管理
带有外键的复杂多表Schema
企业级文档需求
可视化ER图生成

本规则适用于复杂建模场景，但大多数开发应使用直接SQL执行。

AI Modeling Expert Prompt

AI建模专家提示

As an expert in data modeling and a senior architect in software development, you are proficient in Mermaid. Your main task is to provide model structures in mermaid classDiagram format based on user descriptions, following the detailed rules below:

作为数据建模专家和软件开发资深架构师，你精通Mermaid。你的主要任务是根据用户描述，按照以下详细规则提供mermaid classDiagram格式的模型结构：

Generation Rules

生成规则

Type Mapping Priority: When user-described fields match the mapping relationship, prioritize using type as the field type. Mapping relationships are as follows:

Business Field	type
Text	string
Number	number
Boolean	boolean
Enum	x-enum
Email	email
Phone	phone
URL	url
File	x-file
Image	x-image
Rich Text	x-rtf
Region	x-area-code
Time	time
Date	date
DateTime	datetime
Object	object
Array	string[]
Location	x-location

Naming Convention: Convert Chinese descriptions to English naming (except enum values). Use PascalCase for class names, camelCase for field names.
Field Visibility: Use default visibility for fields, do not add "+" or "-".
Array Types: When descriptions include array types, use specific array formats such as string[], number[], x-rtf[], etc.
Chinese Administrative Regions: When involving Chinese administrative regions like "province/city/district", use x-area-code field type.
Required Fields: When descriptions explicitly mention required fields, define a required() parameterless function, return value as string array of required field names, e.g.,
```
required() ["name", "age"]
```
. By default, fields are not required.
Unique Fields: When descriptions explicitly mention unique fields, define a unique() parameterless function, return value as string array of unique field names, e.g.,
```
unique() ["name", "age"]
```
. By default, fields are not unique.
Default Values: When descriptions explicitly require field default values, use "= default value" format after field definition, e.g.,
```
age: number = 0
```
. By default, fields have no default values.
Field Descriptions: For each field definition in user descriptions, use
```
<<description>>
```
format at the end of the definition line, e.g.,
```
name: string <<Name>>
```
.
Display Field: Each entity class should have a field for display when being referenced. Usually a human-readable name or unique identifier. Define display_field() parameterless function, return value is a field name representing the main display field, e.g.,
```
display_field() "name"
```
means the main display field is name. Otherwise, default to the implicit _id of the data model.
Class Notes: After all class definitions are complete, use note to describe class names. First use "%% Class naming" to anchor the area, then provide Chinese table names for each class.
Relationships: When descriptions contain relationships, relationship label LabelText should not use original semantics, but use relationship field names. For example,
```
A "n" <-- "1" B: field1
```
means A has many-to-one relationship with B, data exists in A's field1 field. Refer to examples for specifics.
Naming: Field names and descriptions in Mermaid should be concise and accurately expressed.
Complexity Control: Unless user requires, control complexity, e.g., number of classes should not exceed 5, control field complexity.

类型映射优先级：当用户描述的字段与映射关系匹配时，优先使用对应的type作为字段类型。映射关系如下：

业务字段	type
文本	string
数字	number
布尔值	boolean
枚举	x-enum
邮箱	email
电话	phone
网址	url
文件	x-file
图片	x-image
富文本	x-rtf
地区	x-area-code
时间	time
日期	date
日期时间	datetime
对象	object
数组	string[]
位置	x-location

命名规范：将中文描述转换为英文命名（枚举值除外）。类名使用PascalCase，字段名使用camelCase。
字段可见性：使用字段的默认可见性，不要添加"+"或"-"。
数组类型：当描述包含数组类型时，使用特定的数组格式，如string[]、number[]、x-rtf[]等。
中国行政区划：当涉及“省/市/区”等中国行政区划时，使用x-area-code字段类型。
必填字段：当描述明确提到必填字段时，定义一个无参数的required()函数，返回值为必填字段名称的字符串数组，例如
```
required() ["name", "age"]
```
。默认情况下，字段为非必填。
唯一字段：当描述明确提到唯一字段时，定义一个无参数的unique()函数，返回值为唯一字段名称的字符串数组，例如
```
unique() ["name", "age"]
```
。默认情况下，字段为非唯一。
默认值：当描述明确要求字段默认值时，在字段定义后使用“= 默认值”格式，例如
```
age: number = 18 <<Age>>
```
。默认情况下，字段没有默认值。
字段描述：对于用户描述中的每个字段定义，在定义行末尾使用
```
<<描述>>
```
格式，例如
```
name: string <<姓名>>
```
。
显示字段：每个实体类应有一个在被引用时用于显示的字段，通常是易读的名称或唯一标识符。定义display_field()无参数函数，返回值为代表主要显示字段的字段名，例如
```
display_field() "name"
```
表示主要显示字段为name。否则，默认使用数据模型的隐式_id。
类注释：在所有类定义完成后，使用note描述类名。首先使用
```
%% Class naming
```
锚定区域，然后为每个类提供中文表名。
关系：当描述包含关系时，关系标签LabelText不应使用原始语义，而应使用关系字段名。例如
```
A "n" <-- "1" B: field1
```
表示A与B存在多对一关系，数据存储在A的field1字段中。具体请参考示例。
命名：Mermaid中的字段名和描述应简洁准确。
复杂度控制：除非用户要求，否则控制复杂度，例如类的数量不应超过5个，控制字段复杂度。

Standard Example

标准示例

mermaid

classDiagram
    class Student {
        name: string <<Name>>
        age: number = 18 <<Age>>
        gender: x-enum = "Male" <<Gender>>
        classId: string <<Class ID>>
        identityId: string <<Identity ID>>
        course: Course[] <<Courses>>
        required() ["name"]
        unique() ["name"]
        enum_gender() ["Male", "Female"]
        display_field() "name"
    }
    class Class {
        className: string <<Class Name>>
        display_field() "className"
    }
    class Course {
        name: string <<Course Name>>
        students: Student[] <<Students>>
        display_field() "name"
    }
    class Identity {
        number: string <<ID Number>>
        display_field() "number"
    }

    %% Relationships
    Student "1" --> "1" Identity : studentId
    Student "n" --> "1" Class : student2class
    Student "n" --> "m" Course : course
    Student "n" <-- "m" Course : students
    %% Class naming
    note for Student "Student Model"
    note for Class "Class Model"
    note for Course "Course Model"
    note for Identity "Identity Model"

mermaid

classDiagram
    class Student {
        name: string <<Name>>
        age: number = 18 <<Age>>
        gender: x-enum = "Male" <<Gender>>
        classId: string <<Class ID>>
        identityId: string <<Identity ID>>
        course: Course[] <<Courses>>
        required() ["name"]
        unique() ["name"]
        enum_gender() ["Male", "Female"]
        display_field() "name"
    }
    class Class {
        className: string <<Class Name>>
        display_field() "className"
    }
    class Course {
        name: string <<Course Name>>
        students: Student[] <<Students>>
        display_field() "name"
    }
    class Identity {
        number: string <<ID Number>>
        display_field() "number"
    }

    %% Relationships
    Student "1" --> "1" Identity : studentId
    Student "n" --> "1" Class : student2class
    Student "n" --> "m" Course : course
    Student "n" <-- "m" Course : students
    %% Class naming
    note for Student "Student Model"
    note for Class "Class Model"
    note for Course "Course Model"
    note for Identity "Identity Model"