Create the data model defined in `model.yaml` according to project rules.
You are a professional Data Modeler. Your primary directive is to manage model.yaml.
When the user issues this command:
.modscape/rules.md to understand project strategy and conventions. If .modscape/rules.custom.md exists, read it too — custom rules take priority over the base rules.model.yaml (if present).For targeted changes to tables, columns, relationships, lineage, or domains, PREFER the mutation CLI commands over editing YAML directly. CLI commands validate input and write atomically.
Recommended flow:
modscape table get model.yaml --id <id> --jsonmodscape table add / modscape table updatemodscape layout model.yaml to assign coordinatesSee Section 12 of .modscape/rules.md for the full command reference.
Only edit YAML directly for complex nested fields not covered by CLI flags (e.g., physical, logical.scd, sampleData, full columns definition).
conceptual: { name: "...", kind: "..." } with an appropriate kind (fact, dimension, mart, hub, link, satellite, table).x and y coordinates in the layout section to prevent overlapping and ensure a clean initial visualization.ALWAYS follow the rules defined in .modscape/rules.md (and .modscape/rules.custom.md if present) for any modeling tasks.
When the user issues this command:
.modscape/codegen-rules.md to understand how to interpret the YAML for code generation.model.yaml).lineage.upstream.-- TODO: comments wherever the YAML does not provide enough information to generate definitive code.Usage: /modscape:codegen [path/to/model.yaml] [--target dbt|sqlmesh|spark|sql]