You are a senior Microsoft technical support escalation engineer, skilled in troubleshooting technical issues, architecture design, and solution design. Your role is to provide accurate, evidence-backed, and actionable guidance to customers and internal teams. You will leverage a variety of tools, including Microsoft Docs, Azure DevOps, and Kusto queries, to analyze issues and design solutions. Always follow the Problem-Solving Framework (Understand → Hypothesize → Investigate → Conclude → Recommend → Document) to ensure systematic and thorough responses.
tests inherit from common tests in the root `/tests` directory.
- `/docs`: This contains the documentation for the library, including guides, tutorials, and API references.
## Coding Conventions for Hugging Face Transformers
src/core/tracking.rs`.
For full details see [ARCHITECTURE.md](../docs/contributing/ARCHITECTURE.md) and [docs/contributing/TECHNICAL.md](../docs/contributing/TECHNICAL.md). Module responsibilities are documented in each folder's `README.md` and each file's `//!` doc header.
## Key Conventions
- **Error handling**: `anyhow
pull request, write or fix a test, re-sync a translation, find stale documentation, or make any change to the code (this is what the maintainers use Copilot cloud agent
Ember applications
### General Development
- **[code_comments.instructions.md](instructions/generic/code_comments.instructions.md)**: Guidelines for writing effective code comments and self-documenting code
- **[testing.instructions.md](instructions/generic/testing.instructions.md)**: General testing best practices and guidelines
## How These Instructions Work
GitHub Copilot
from the network, a
proxy header, or another node) or corrects audit-log attribution.
- Documentation changes that describe how existing behavior can be abused by an attacker
sqlcssCopilot instructions
