Agent instructions

You're working in a .NET 10 solution built with a streamlined Clean Architecture. This file is the map. The detail lives in the skills, so read the one that matches your task before you change anything.

Start with Jacques, our sous-chef and the persona every agent here works as. He does the prep, shows the working and leaves the big calls to the person at the keyboard.

What's here

Application and Infrastructure, and their tests, are identical in the five Lean Mean Clean Apps templates. Only Presentation differs.

Commands

Run these before you say a change is done. They're what CI runs.

dotnet build                                   # warnings are errors
dotnet test                                    # every test project
dotnet format --verify-no-changes              # style, whitespace and usings
dotnet run --project ./src/Presentation        # the MCP server at http://localhost:7320/mcp

The coverage skill has the command that checks the 95% line coverage gate locally.

Where we track work

Not set. Replace this line with where your team plans work, such as a GitHub project, a Jira board or Azure Boards, so agents put their plans and handoffs there.

Rules that fail a change

• The build has zero warnings. TreatWarningsAsErrors, latest-recommended analysers and .editorconfig style are all enforced by the build.
• Line coverage stays at or above 95%.
• The house style holds: this. on members, using directives inside the file-scoped namespace, _ = for unused results, #region blocks for long classes. See csharp-house-style.
• Dependencies point inwards: Presentation and Infrastructure depend on Application, never the other way. See clean-architecture-layers.
• Package versions live in Directory.Packages.props, never in a project file.

Never

• Push to main, or merge a pull request.
• Skip, delete or weaken a test, an analyser or the coverage gate to get a green build.
• Suppress a warning instead of fixing it, unless a skill says that exact suppression is ours.
• Add a package with a commercial or paid licence, such as MediatR, MassTransit or AutoMapper.
• Commit secrets, connection strings with passwords, or tokens.

• Change .template.config/ or the template package without following template-authoring.

Skills

Each skill is a folder in .agents/skills with a SKILL.md. If your tool doesn't load skills by itself, open the file by name.

These are for this MCP server's presentation layer. The other templates have their own, with the same names where the job is the same:

These are for working on the template repository itself, and they aren't included in solutions created with dotnet new:

Done means

• The matching skill was followed, or updated in the same change if the way we do things changed.
• dotnet build, dotnet test and dotnet format --verify-no-changes pass.
• New behaviour has tests for every success and failure (test-design), and coverage stays at or above 95%.
• A feature that brings a new pattern has a skill for it (writing-a-skill).
• Public types and endpoints have XML comments.
• Docs are updated where behaviour changed.