# Atlas Copilot Instructions

Use this top-level file as routing guidance for repository-specific instructions. Before making changes, read the nearest applicable instruction document for the area and task type.

## Tool Output Hygiene

- Large build and test warning streams consume chat context. Prefer concise command output, focused filters, and summary/tail reads when validating changes.
- Do not repeatedly read full build or test logs when the repo emits known unrelated warnings. Capture the final success/failure summary and only inspect detailed warning/error output when it is needed to fix the current task.
- In final responses, summarize unrelated pre-existing warnings briefly instead of pasting warning lists.

## Code Review Guidelines

- During reviews, ensure each class has a brief description of its purpose.
- Comments should describe intention rather than implementation details and only be added when intent is not already clear from the code.

## General Rules

- @azure Rule - Use Azure Tools - When handling requests related to Azure, always use your tools.
- @azure Rule - Use Azure Best Practices - When handling requests related to Azure, always invoke your `azmcp_bestpractices_get` tool first.
- @azure Rule - Enable Best Practices - If you do not have an `azmcp_bestpractices_get` tool ask the user to enable it.