Security Considerations**
- Scripts should be reviewed for security implications
- External dependencies should be clearly documented
- No malicious patterns (unexpected network calls, unauthorized file access)
### Common Issues to Flag
- **Missing
Test fixture OpenAPI spec files
openapi-diff/ # C#/.NET solution (core diff engine)
docs/ # Documentation
```
## CI
CI runs on both Ubuntu and Windows via GitHub Actions (`.github/workflows/ci.yml`). It runs
edt.1c.ru/dev/ru/docs/plugins/project/
We are developing a plugin for EDT, this is the MCP server.
Documentation is here: https://edt.1c.ru/dev/edt/2026.1/apidocs/
DO NOT BUILD YOURSELF, ASK THE EXPERT!
ALL CODE
interface in `src/alfanous/api.py`
4. Write tests in `src/tests/test_*.py`
5. Update documentation if needed
### Modifying Index Structure
1. Update indexing logic in `src/alfanous/indexing.py`
2. Update importer in `src/alfanous_import/`
3. Rebuild
warnings
- Treat new byte-compilation warnings as regressions when touching Emacs Lisp code.
- For documentation hygiene on touched files, also run `M-x checkdoc` (or batch
`checkdoc-file`) before wrapping
SqlScriptDom/Parser/TSql/Ast.xml` (AST node definitions)
### Step 4: Check SQL Server Version Support
Always verify Microsoft documentation:
- Search for "Applies to: SQL Server 20XX (XX.x)" in Microsoft docs
- Note that different features
implementation.
- Use local `super-dev` commands when you need to generate or refresh documents, spec artifacts, quality reports, or delivery manifests.
## First-Response Contract
- On the first reply after `/super-dev
LeafyGreen UI - Copilot Instructions
This document provides comprehensive guidance for coding agents working on the LeafyGreen UI design system repository. Following these instructions will minimize build failures, validation errors
gallery correctly
- Getting Started page loads with video and action cards
- Contribute page shows documentation
- All navigation links work
## Repository Structure
Key directories and files:
- `website/` - Main Docusaurus application
central hub repository for **Azure App Configuration**. It contains cross-language examples, documentation, configuration schemas, and release notes for the App Configuration ecosystem.
## Repository Structure
- `examples/` — Working sample applications across
development runner
├── .env.example # Example environment variables
├── requirements.txt # Production dependencies
├── Dockerfile # Container definition
└── README.md # Usage documentation
```
### CLI Design
- Use `typer` for CLI parsing
- Support both flags and environment variables
- Provide --help
spawning within its budget. Subagents are trusted to work
within their turn ceiling.
---
## DOCUMENTATION POLICY
**Default: NO new docs.** Use Empirica breadcrumbs instead.
- Findings, unknowns, dead-ends -> logged
review comments, or check results
- `gdextension-hygiene` for a finish pass that checks validation, documentation, sample/test sync, and build wiring
- When the task touches `.gd` files anywhere in the repo
profile
isolation, does not weaken local path boundaries, and avoids remote debugging
unless explicitly documented.
- For CI changes, check forked-PR secret behavior and avoid recommending
`pull_request_target
Copilot Instructions for BitRouter
**This file is deliberately a pointer, not a document.** Read these instead:
- [`AGENTS.md`](../AGENTS.md) — the repository rules for anything editing this
codebase: the hard prohibitions (`#[allow
repo uses).
- If a lockfile is present, keep it updated consistently with `uv` workflows.
## Documentation & consistency (IMPORTANT)
- **After any code changes**, always check and update relevant documentation (`docs/`, `README.md`), output