coreex-api-e2e

Creates a complete CoreEx entity with CRUD API endpoints across all application layers.

28|8|Updated Feb 21, 2022
One-click install
npx skills add https://github.com/Avanade/CoreEx --skill coreex-api-e2e-avanade
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coreex-api-e2e
Source: https://github.com/Avanade/CoreEx/tree/main/.github/skills/coreex-api-e2e
Command: npx skills add https://github.com/Avanade/CoreEx --skill coreex-api-e2e-avanade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Adding a new entity to a CoreEx solution requires touching many layers — DTO contract, database migration, EF Core repository, validator, policy, application service, API endpoint, and tests — and doing them in the right order with consistent context is error-prone and repetitive. ## Core Features & Use Cases - Single Interview, Full Stack: Gathers entity name, fields, operations, identifier type, and guard requirements once, then invokes each L1 skill in sequence without re-asking questions. - Feature-Aware Sequencing: Reads AGENTS.md feature configuration (rop-enabled, outbox-enabled, data-provider, *.Domain project) to conditionally include or skip steps like aggregate, migration, and repository. - Built-in Validation: Finishes with dotnet build and confirms unit test and integration test classes exist for the validator, policy, and API. - Use Case: You need to add a new Product entity with Get/Query/Create/Update/Delete endpoints to an existing CoreEx service — this skill walks the entire vertical slice from database table to HTTP endpoint in one guided workflow. ## Quick Start Ask the AI to add a new entity named Product with Get, Query, Create, Update, and Delete operations end-to-end using the coreex-api-e2e workflow.

Frequently Asked Questions about coreex-api-e2e

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new entity with CRUD endpoints to a CoreEx solution?▼

Use the coreex-api-e2e workflow, which interviews you once for the entity name, fields, operations, and identifier type, then invokes the L1 skills in order: contract, migration, repository, validator, app-service, API, and tests. It finishes with a dotnet build validation.

What layers does a CoreEx end-to-end entity workflow generate?▼

It generates the DTO contract, database migration, EF Core repository, validator with unit tests, optional policy guard with unit tests, application service, API endpoint, and integration test classes. Aggregate and ref-data steps run conditionally based on solution configuration.

When should I not use the CoreEx end-to-end API workflow?▼

Skip it when modifying an existing entity or endpoint, building a read-only façade backed by an external adapter with no local table, or adding only a subset of layers. In those cases invoke the targeted L1 skill such as coreex-validator or coreex-api directly.

Does the CoreEx workflow skip database steps when there is no data provider?▼

Yes. When `data-provider = None` in the solution-root AGENTS.md feature configuration, both the migration and repository steps are skipped together, since a repository without a table would be an incomplete state.

How does the CoreEx workflow avoid asking the same question twice?▼

It batches all questions — entity name, CRUD operations, properties, identifier type, guard needs, ref-data status — into a single upfront interview, then passes the resolved context to each L1 skill so none of them re-ask.