What problem does it solve? Adding a reference data (Code/Text lookup) type in a CoreEx solution touches two separate projects — the *.Database project for schema and seed rows, and the *.CodeGen project for entity definitions — and confusing the two YAML files or editing generated .g.cs files causes runtime failures. This Skill guides the complete end-to-end workflow so each step lands in the right place. ## Core Features & Use Cases - New reference data types: Scaffold the migration script, add seed rows, register the table in dbex.yaml, and generate contracts, controllers, services, repositories, and mappers via CodeGen. - Modify existing types: Add extra stored properties, amend seed rows, change pluralization or identifier types, and alter tables with immutable delta scripts. - Contract wiring: Attach an existing ref-data type to a contract using [ReferenceData<T>] partial properties with Roslyn-generated navigation accessors. - Use Case: You need a new Brand lookup table in a PostgreSQL-backed CoreEx service. The Skill walks you through creating the snake_case table script, seeding rows in ref-data.seed.yaml, defining the entity in ref-data.yaml, and running both dotnet run -- All and CodeGen in the correct order. ## Quick Start Ask the AI to add a new reference data type named Brand to your CoreEx domain with a few seed rows, and it will execute the database and CodeGen workflow end to end.
