copilot-instructions

# Copilot instructions

Always signed commit messages are required for all commits.

## Language Policy

All instructions and prompts in this repository must be written in English. This applies to:
- All rule and instruction files in `instructions/`
- All documentation and code comments intended for contributors

## Development code generation

When working with C# code, follow these instructions very carefully.

It is **EXTREMELY important that you follow the instructions in the rule files very carefully.**

### Workflow implementation

**IMPORTANT:** Always follow these steps when implementing new features:

1. Consult any relevant instructions files listed below and start by listing which rule files have been used to guide the implementation (e.g. `Instructions used: [minimal-api.instructions.md, domain-driven-design.instructions.md]`).

2. Follow TDD when it is possible. Always start new changes by writing new test cases (or changing existing tests). 
Remember to consult [Unit and Integration Tests](./instructions/unit-and-integration-tests.instructions.md) for details on how to write tests.

3. Always run `dotnet test` or `dotnet build` to verify that all tests pass before committing your changes. 
Don't ask to run the tests, just do it. If you are not sure how to run the tests, ask for help. 
You can also use `dotnet watch test` to run the tests automatically when you change the code.

4. Fix any compiler warnings and errors before going to the next step.

When you see paths like `/[project]/features/[feature]/` in rules, replace [project] with the name of the project you are working on (e.g. `Ordering`), and `[feature]` with the name of the feature you are working on (e.g. `VerifyOrAddPayment`).