Meta Chatmode.instructions

---
applyTo: ".github/chatmodes/**"
---

# Chatmode Instructions

## Purpose

Define the standard for creating, structuring, and using chatmode files in the project. A chatmode configures the behavior of an AI agent (e.g., Copilot) for a specific context or workflow (e.g., architect, reviewer, tester).

## General Rules

-   A chatmode file must only be created if the user explicitly requests a specific dialogue/configuration mode for the AI (e.g., "Create an architect chatmode", "Add a reviewer chatmode").
-   Chatmodes are passive: they modify the AI's behavior in the background for all relevant requests.
-   Each chatmode must be documented in English and clearly describe:
    -   The expected role of the AI (e.g., "Act as an experienced software architect")
    -   The priorities, tone, constraints, and objectives of the mode
    -   The specific instructions to apply (e.g., "Always propose an architecture before generating code")
-   The file name must follow the format: `{role}.chatmode.md` (e.g., `architect.chatmode.md`, `reviewer.chatmode.md`).
-   The front matter must include:
    -   `tools` (optional): List of tools required by the chatmode.
    -   `description` (optional): summary of the chatmode

## Chatmode File Structure

1. **Front matter YAML** (mandatory)
2. **Main title** (`#`)
3. **Chatmode purpose**
4. **Expected behavior**
5. **Constraints and priorities**
6. **Example usage**
7. **References** (other related instructions or prompts)

## Examples