Kubernetes.
## Directives Générales
### Principes de Base
- Utilisez l'anglais pour tout le code, la documentation et les commentaires.
- Priorisez un code modulaire, réutilisable et évolutif.
- Suivez les conventions de nommage
sans état.
- Utilisez HTTPS et forcez SSL.
- Implémentez des politiques CORS appropriées.
## Documentation API
- Utilisez le package OpenAPI intégré pour la documentation d'API.
- Fournissez des commentaires XML pour
INFO, DEBUG).
- Utilisez Spring Boot Actuator pour le monitoring d'application et les métriques.
## Documentation API
- Utilisez Springdoc OpenAPI (anciennement Swagger) pour la documentation API.
## Accès aux Données
fonctions, par exemple, "const toggle = () =>". Aussi, définissez un type si possible.
---
**Avertissement**: Ce document a été localisé par [GitHub Copilot](https://docs.github.com/copilot/about-github-copilot/what-is-github-copilot). Par conséquent, il peut contenir des erreurs
dépendances clairement pour optimiser la lisibilité et la maintenabilité.
Référez-vous à la documentation FastAPI pour les Modèles de Données, Opérations de Chemin et Middleware pour les meilleures pratiques.
---
**Avertissement
OpenAPI, cela fait toujours référence à la version spec 3.0.1.
Lorsque vous créez un document OpenAPI, vous devez toujours considérer la réutilisabilité du schéma de données. NE dupliquez
this repo, changes must follow the **official best
practices from that technology's own documentation** — not conventions
inferred from blog posts, Stack Overflow, or general training knowledge.
Concretely:
- **Terraform / HashiCorp
GitHub Copilot Instructions for MCS-Labs
This document contains essential context for GitHub Copilot when working on the Microsoft Copilot Studio Labs repository.
## 🎯 Project Overview
**What This Is**: A Jekyll
direct general SDK usage questions to issues if they belong in support channels or documentation.
- Keep issue reports actionable. Include SDK version, runtime or framework details, platform details, stack traces
assets` that summarizes modes, tools, resources, and quick-start.
- The prompt now explicitly documents authentication behavior:
- `FMP_ACCESS_TOKEN` is optional for server initialization.
- It is required to successfully call
/skills/use-discatsharp/SKILL.md`.
- Preserve user changes and verify current DisCatSharp APIs through live source or the documentation MCP.
- Credit Copilot-assisted commits with `Co-Authored-By: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com
stubs *before* importing the module under test. See `src/services/__tests__/graph.test.ts` for the pattern.
## Microsoft Graph Documentation (microsoftdocs/mcp)
The workspace has a `microsoftdocs/mcp` server configured (`.vscode/mcp.json`) that provides access to official Microsoft
Iris Copilot Instructions
Read [AGENTS.md](../AGENTS.md) first. The canonical document map is [docs/index.md](../docs/index.md). If an older report, audit, ADR, plan, or comment conflicts with those files, treat the older
required scopes.
**Important:** OAuth scopes must always be kept in sync between implementation and documentation:
- Implementation: `src/index.ts` defines all scopes in the `allRequiredScopes` array
- Documentation: `README.md` section "Scopes for Authentication
Java and Python)
- `/eng/` - Engineering system files including common scripts and pipeline templates
- `/doc/` - Documentation including development guidelines
- `.github/` - GitHub configuration, workflows, and custom agents
## Tool Development
### Creating
Complex team workflows** - Not applicable
5. **Minor style issues** - Code is auto-formatted
6. **Documentation for external users** - Internal project
### Common Patterns to Check
- Shell scripts should export `USER
affects a user-facing workflow (e.g., creating a container, running a query, editing a document). E2E tests live in `test/` organized by API type.
Tooling and conventions:
- Use **Jest
read the text in it → `image-text file`
- opening a PDF or Office document → inspect its format first, then read a narrow slice: PDF `pdf-meta`/`pdf-outline` then
examples/` | Terraform HCL examples for each resource and data source |
| `docs/` | Auto-generated provider documentation (do NOT edit manually) |
| `templates/` | Go templates for documentation generation (`tfplugindocs`) |
## Resource Categories
1. **Fabric