| name | coreex-api-e2e |
| description | Create a complete new entity with CRUD API endpoints end-to-end in a single guided workflow: DTO contract, database migration, EF Core repository, validator (+ unit tests), optional policy guard (+ unit tests), application service, API endpoint, and integration tests. USE FOR: adding a brand-new entity to an existing CoreEx solution where the full stack — from database table to HTTP endpoint — is needed. DO NOT USE FOR: modifying an existing entity or endpoint (use the targeted L1 skill directly), read-only façade entities backed by an external adapter with no local table (use individual L1 skills), or any partial-stack additions. |
| argument-hint | Optional: entity name, CRUD operations needed (Get/Query/Create/Update/Patch/Delete), key fields |
| tags | ["coreex","api","entity","end-to-end","crud","vertical-slice"] |
CoreEx: Add API (End-to-End)
Guides you through adding a complete new entity and its CRUD API in one sitting: gathers all context upfront, then invokes the appropriate L1 skills in sequence so you are never asked the same question twice.
When to Use
- Adding a brand-new entity to an existing CoreEx solution — full stack from database table to HTTP endpoint
- The entity will be owned and persisted locally (not sourced purely from an external adapter)
- You want the entire vertical slice — contract, migration, repository, validator, app-service, API, and tests — in one workflow
When Not to Use
- Modifying an existing entity, endpoint, or validator — invoke the targeted L1 skill directly (e.g.
coreex-validator, coreex-api)
- Read-only façade entity backed by an external adapter with no local table — use individual L1 skills and skip migration/repository
- Adding only a subset of layers (e.g. validator only, API only) — call the relevant L1 skill directly
Workflow Overview
- Read Feature Configuration — resolve
rop-enabled, outbox-enabled, and data-provider from the solution-root AGENTS.md, and check whether a *.Domain project exists, before asking anything.
- Interview — gather entity name, fields, operations (Get/Query/Create/Update/Patch/Delete), identifier type, whether a policy guard is needed, and (if any field is ref-data) whether that reference-data type already exists; batch all questions into one turn.
- Execute L1 sequence — invoke each L1 skill in order, passing context resolved in steps 1–2; no repeated questions.
- Validate —
dotnet build across all projects; confirm unit and integration test classes are present.
For full step-by-step guidance see references/workflow.md.
L1 Sequence
Key References
