What problem does it solve? Designing or reviewing a Thinkwise Software Factory data model without consistent conventions leads to inconsistent naming, misclassified entities, wrong column types, and validation errors that only surface at generation time. This Skill provides the reference guidelines for domains, tables, columns, and references so every sf_mcp change is checked against the conventions before being proposed or executed. ## Core Features & Use Cases - Naming and classification rules: Enforces singular lowercase underscore-separated names, classifies tables as strong entities, weak entities, link tables, or inheritance tables, and defines primary/foreign key naming. - Column and domain design: Covers data types, identity columns, defaults, calculated columns, column order, grid/form visibility, grouping, and data sensitivity classification. - Modeling workflow guidance: Includes menu placement decisions, bulk-import task detection, and verified API write quirks for scripting changes through a metadata-driven modeling API. - Use Case: When asked to add a sales_order_line table to an existing model, the Skill guides naming it as a weak entity of sales_order, placing the parent foreign key first in the primary key, choosing domains, and setting grid visibility before committing via sf_mcp. ## Quick Start Review my Thinkwise data model and check the table and column names against the Thinkwise modeling guidelines before I create a new sales order entity.
