ezbuy/ezorm

Overview

This skill generates ezorm YAML schema files for MySQL and mysqlr from user requirements. It prefers mysqlr by default unless the user explicitly asks for classic mysql. The output is YAML only, suitable for immediate use with the ezorm tooling.

How this skill works

I restate the domain model as simple entities and relationships, ask one clarification only if a critical piece is missing, then choose db: mysql or db: mysqlr. Fields are mapped to the appropriate mysql/mysqlr types and flags, table metadata (dbname and table/dbtable) is set, and indexes/uniques/primary constraints are added. The final deliverable is one or more YAML documents separated by '---' and containing only valid ezorm schema syntax.

When to use it

• You need ezorm-compatible schema YAML for a Go project using MySQL/mysqlr.
• You want schema-first ORM files generated from a domain description or ERD.
• You prefer mysqlr features and want it chosen automatically unless otherwise requested.
• You need concise, validated YAML for automated pipelines or CI validation.

Best practices

• Describe entities, key fields, and relationships explicitly; I will ask one critical clarification if needed.
• Specify if you require classic mysql instead of the default mysqlr.
• Provide preferred table names or allow snake_case defaults derived from entity names.
• Request explicit foreign keys only when you want fk entries; otherwise use logical relations without fk.
• Keep schemas minimal: include only fields and flags you need; avoid inventing behaviors.

Example use cases

• Generate YAML schemas from an app domain: User, Post, Comment with user->post and post->comment relationships.
• Produce a mysqlr schema for a microservice data model where mysqlr-specific types or flags are needed.
• Create multiple YAML documents separated by '---' for several entities in a single output.
• Convert a brief ERD description into validated ezorm YAML for use with scripts/validate.sh.