CoreEx Bootstrap

Initialises a blank CoreEx repository by generating root guidance files and immediately chaining to /coreex-scaffold for solution shaping.

When to Use

• The repository has just had dotnet new coreex-ai run — .github/ and .claude/ AI assets are present but there are no root guidance files (README.md, AGENTS.md, CLAUDE.md).
• This is a brand-new, empty-first greenfield repository with no src/, tests/, or tools/ directories.

When Not to Use

• The repository already has a README.md or src/ — use /coreex-scaffold directly.
• You are adding new hosts to an existing CoreEx solution — use /coreex-scaffold instead.
• You want architecture guidance — use /coreex-expert instead.
• dotnet new coreex-ai has not yet been run — run it first so the AI workflow assets are present.

Workflow

1. Confirm the project name. Read the workspace root folder name as the default. If it is already in [Company].[Product].[Domain] form (e.g. Avanade.Bookstore.Books), use it as-is. Otherwise ask the user for the correct 3-part name.

2. Generate root guidance files. Write the three files below, substituting {{project-name}} with the confirmed project name.

3. Chain to /coreex-scaffold. Immediately invoke the scaffold skill to interview the solution shape and run the right dotnet new coreex* commands.

File Templates

README.md

# {{project-name}}

This repository is a CoreEx application service.

## Next Step

Run `/coreex-scaffold` in Copilot Chat or Claude Code. The workflow will ask about:

- the bounded context and solution name;
- whether the domain owns data or is a facade;
- whether it needs an API host;
- whether it needs reliable event publishing and an outbox relay;
- whether it needs to consume events with a subscriber host;
- whether reference data, a domain layer, and ROP should be enabled.

From that interview, the workflow will derive and run the right `dotnet new coreex*` commands for the solution.

AGENTS.md

# {{project-name}} — CoreEx Bootstrap

This repository is intentionally bootstrapped with only the **CoreEx AI workflow assets**.

Run `/coreex-scaffold` to interview the business/domain shape and scaffold the smallest safe `dotnet new coreex*` command set for this solution.

Until that workflow runs, the repository is expected to stay mostly empty apart from:

- `.github/` instructions, prompts, skills, and the cached CoreEx docs.
- `.claude/commands/` prompt shims.
- this bootstrap guidance file.

If the repository still only contains this bootstrap shell, it is safe for `/coreex-scaffold` to use `dotnet new ... --force` when replacing placeholder files with the full solution scaffold.

Use `/coreex-expert` when you need CoreEx architecture guidance before choosing the final shape.

CLAUDE.md

@.github/instructions/coreex.instructions.md
@.github/instructions/coreex-conventions.instructions.md
@.github/instructions/coreex-contracts.instructions.md
@.github/instructions/coreex-application-services.instructions.md
@.github/instructions/coreex-aspire.instructions.md
@.github/instructions/coreex-validators.instructions.md
@.github/instructions/coreex-repositories.instructions.md
@.github/instructions/coreex-api-controllers.instructions.md
@.github/instructions/coreex-event-subscribers.instructions.md
@.github/instructions/coreex-host-setup.instructions.md
@.github/instructions/coreex-domain.instructions.md
@.github/instructions/coreex-tests.instructions.md
@.github/instructions/coreex-tooling.instructions.md

## Slash commands

| Command | What it does |
|---|---|
| `/coreex-bootstrap` | Generates root guidance files for a blank CoreEx repo, then chains to `/coreex-scaffold` |
| `/coreex-scaffold` | Guided interview → derives and runs the right `dotnet new coreex*` commands for this solution shape |
| `/coreex-expert` | Architecture guidance, pattern decisions, and sample-aligned implementation advice |
| `/coreex-docs-sync` | Refreshes the entire AI asset bundle and docs cache from the CoreEx.Template release matching this project's CoreEx NuGet version |