AI Support in the Template

Both ApiStandard and MiniApi provide an AGENTS.md file at the project root and reusable AI skills under .agents/skills. They share the iteration-documentation and delivery loop, but their backend constraints differ: ApiStandard targets Controllers and business modules, while MiniApi targets Minimal APIs, Native AOT, and trimming.

File layout

The template's AI guidance is primarily organized as follows:

AGENTS.md
.agents/
└── skills/
    ├── perigon/
    │   └── references/
    │       ├── angular.md
    │       ├── backend.md
    │       └── perigon-cli.md
    ├── aspire/
    │   └── references/
    ├── aspire-orchestration/
    │   └── references/
    ├── ux/
    │   └── references/
    │       ├── common.md
    │       ├── web.md
    │       ├── desktop.md
    │       └── phone.md
    ├── test/
    ├── native-aot/            # MiniApi
    ├── delivery-loop/
    ├── dotnet-inspect/
    ├── docs/
    │   └── references/
    │       ├── requirements.md
    │       ├── design.md
    │       └── plan-tasks.md
    ├── code-review/
    └── commit-message/

SKILL.md is the entry point for each skill. A skill loads its focused references only when the task needs them, so an agent does not have to paste the complete project policy into every conversation.

Iteration documentation model

Demand.md and Design.md are project-wide requirement/design summaries and indexes; they do not contain every feature's details. Product design and development plans are organized by iteration and feature module:

docs/
├── UserStory/
│   ├── Demand.md
│   ├── Design.md
│   └── Iter0-Initial/PD0001-Initial.md
└── Development/
    ├── ProjectTracking.md
    └── Iter0-Initial/PT0001-Initial.md

• Iteration directories use Iter<number>-<Name>.
• PD####-Name.md is a Product Design for one feature module in an iteration, including requirements, scenarios, and design.
• PT####-Name.md is a Plan Task linked to its source PD, including tasks, dependencies, progress, implementation results, and verification evidence.
• PD/PT numbers are four-digit, monotonically increasing, and not reused within an iteration. Each document focuses on one feature module.

Both templates include Iter0-Initial/PD0001-Initial.md and Iter0-Initial/PT0001-Initial.md as their initial product-design and plan-task templates. A MiniApi PT also records the AOT impact decision, publish/runtime evidence, or the reason that validation was not run.

Project rules from AGENTS.md

The project-level guidance establishes these important rules:

• Prefer deterministic, accurate work: inspect facts and existing code before using a command, path, or project structure; do not guess.
• Validate code changes with a build, test, or another check appropriate to the change.
• The baseline is C# 14, Aspire 13+, ASP.NET Core 10, and EF Core 10; Angular is the default frontend technology.
• ApiStandard places business code under src/Modules and exposes it through Controllers. MiniApi uses ApiService/Endpoints/Managers/Models/Services and does not assume an AdminService, Controllers, a Modules layer, or a built-in migration resource.
• A MiniApi endpoint group derives from RestEndpointBase and is registered through a static MapEndpoints method and the generated MapEndpointGroups() call. Typed handlers, parameter binding, and JSON contracts must remain statically analyzable for AOT.
• Prefer Perigon for scaffolding, adding modules/services, code generation, OpenAPI clients, and MCP configuration. Prefer the Aspire CLI for AppHost startup, resource state, logs, traces, and distributed-app configuration.
• Before planning, implementing, or reviewing Perigon business code, read perigon; read aspire only when the task crosses AppHost or distributed-runtime boundaries. UI work also requires ux and the reference for the target platform.
• A checked task is only a progress index. Do not claim completion without implementation evidence and the required checks passing.
• After every AI coding run, update the active PT's checkboxes, progress, implementation record, and verification evidence, then synchronize ProjectTracking.md. Also update the source PD when observable behavior or design changed.

These rules provide AI workflow context; they do not replace the compiler, tests, or code review for the project.

Available skills

perigon and aspire are the primary entry skills. aspire routes distributed-app work, while aspire-orchestration handles concrete local lifecycle operations; ordinary builds and tests should not be delegated to the Aspire workflow.

Recommended workflow

1. Read AGENTS.md, then load perigon, aspire, or another focused skill for the task.
2. Prefer Perigon CLI/MCP when creating solutions, modules, services, or generated code; inspect perigon <command> -h before running a command.
3. For Aspire runtime work, use commands such as aspire start, aspire wait, and aspire describe instead of substituting dotnet run for the AppHost workflow.
4. When generating DTOs or changing a module, check the directory, file granularity, type names, and all references together.
5. Run the appropriate build or tests after a change, and use the code-review skill for high-risk changes.
6. For every AI coding change, use delivery-loop for implement → verify → update PT/ProjectTracking/PD → converge. Even a small fix uses a concise PT implementation record.
7. In MiniApi, also use native-aot when changing endpoints, DTO/JSON behavior, reflection, dependencies, EF models, or publish settings. A normal build is not a substitute for Native AOT publish evidence.

See MCP for Perigon Agent MCP setup and code-generation capabilities.