coreex-solution-scaffolder

Generates CoreEx .NET solution scaffolds from interview answers using dotnet new templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Choosing the right CoreEx template combination (API, relay, subscriber, Aspire AppHost) and the correct dotnet new flags is error-prone, especially around naming rules and retrofit scenarios. This Skill turns a short plain-English interview into validated, safe scaffolding commands. ## Core Features & Use Cases - Guided interview: Asks one question at a time (via confirmation cards when available) covering hosts, database provider, messaging, reference data, Domain layer, ROP, and Aspire AppHost, then derives the exact template inputs. - Safe generation: Enforces the [Company].[Product].[Domain] naming convention, runs dry-runs before real template commands, pins CoreEx.Template versions, and refuses unsafe --force operations on existing solutions. - Retrofit support: Adds missing Api, Relay, Subscribe, or Aspire hosts to existing CoreEx solutions without overwriting hand-written code, including AppHost and CodeGen follow-up handling. - Validation: Wires projects into the .slnx, runs dotnet build and unit tests, and can provision local dependency assets (docker-compose, Service Bus emulator config) for a runnable local state. - Use Case: A developer with a bootstrap-only repo answers a few questions and gets a complete event-driven CoreEx solution with SQL Server, Service Bus relay, subscriber, and Aspire orchestration, built and tested. ## Quick Start Ask the assistant to scaffold a new CoreEx solution for your requirements, for example: run the coreex-solution-scaffolder skill to create a new CoreEx service with an API and SQL Server storage.

Frequently Asked Questions about coreex-solution-scaffolder

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

FAQPage Schema
How do I scaffold a new CoreEx solution with dotnet new?▼

Run the coreex solution template with your chosen data and messaging providers, then add host templates like coreex-api, coreex-relay, or coreex-subscribe using four-part names. This Skill automates that flow through a short interview and validates the result with dotnet build.

How do I add a missing API or subscriber host to an existing CoreEx solution?▼

Run only the missing host template with the four-part name, for example dotnet new coreex-api -n Company.Product.Books.Api, then add the project to the .slnx. Do not re-run the root coreex template, which would overwrite existing code.

What naming format do CoreEx templates require?▼

The coreex solution template takes a three-part base name like Company.Product.Books, while every addon template requires a four-part name with its suffix, such as Company.Product.Books.Api. Passing the base name to an addon causes folder collisions with sibling projects.

Can I add a .NET Aspire AppHost to a CoreEx solution?▼

Yes, run dotnet new coreex-aspire after all host templates exist, passing --has-api, --has-relay, and --has-subscribe to match the chosen hosts. If an AppHost already exists, edit AppHost.cs manually instead of re-running with --force.

When should I not use the CoreEx scaffolding skill?▼

Do not use it for runtime debugging, container or package restore issues, or creating the initial bootstrap repository. Run dotnet new coreex-ai and the coreex-bootstrap skill first, and use the CoreEx Expert agent for architectural guidance on existing implementations.