arifOS
ariffazil/arifOS/.github/copilot-instructions.md
writes must originate from `arif_seal` / `arif_vault_seal` (stage 999) or a documented post-SEAL `arif_forge` lease. Direct ORM inserts bypassing the chain = F1 + F11 VOID
How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
ariffazil/arifOS/.github/copilot-instructions.md
writes must originate from `arif_seal` / `arif_vault_seal` (stage 999) or a documented post-SEAL `arif_forge` lease. Direct ORM inserts bypassing the chain = F1 + F11 VOID
delphicleancode/delphi-spec-kit/.github/copilot-instructions.md
Try/finally** for memory management - **Try/except** only for actual error handling, never for control flow ## Documentation - Generate **XMLDoc** for public methods and properties - Comments in **Portuguese** for Brazilian projects
NuGuardAI/nuguard/.github/copilot-instructions.md
generates AI-focused SBOMs from source code, runs static security analysis, validates cognitive policy documents, and red-teams live AI applications with adversarial scenario testing. Pipeline: `sbom generate` → `analyze` → `behavior
AnalyticAce/binance-mcp-server/.github/copilot-instructions.md
their usage and purpose in comments. - If possible use available tools to search libary documentation to write and suggestion updated code. - Use consistent naming conventions and follow language-specific best
microsoft/fabric-task-flows/.github/copilot-instructions.md
Copilot Instructions ## Project Overview This is a **documentation-driven** knowledge base with supporting Python scripts and tests. The repo provides pre-defined Microsoft Fabric architectures via one orchestrator agent (`@fabric
ojspace/md-anything/.github/copilot-instructions.md
folder, converts them through the shared pipeline, and returns counts plus per-document metadata. It does not currently process source manifests or generate graph/index artifacts. - `src/mcp-support.ts` is the MCP policy
Trifall/chat-export/.github/copilot-instructions.md
large files, provide relevant complete sections with clear context ## General Guidelines - Follow Chrome Extension documentation for: - Best practices - Security guidelines - API usage
microsoft/rego-cpp/.github/copilot-instructions.md
Python ctypes/cffi wrapper │ └── dotnet/ # .NET P/Invoke wrapper ├── cmake/ # CMake package config templates ├── doc/ # Doxygen documentation sources ├── CMakeLists.txt # Root build definition ├── CMakePresets.json # Named build presets └── VERSION # Semantic version file (MAJOR.MINOR.PATCH) ``` ## Build
drvoss/everything-copilot-cli/COPILOT-INSTRUCTIONS.md
adopt. When working in this repo, Copilot CLI should treat content as **configuration and documentation**, not application code. ## Response Voice Write like a teammate handing off to another builder: - lead
drvoss/everything-copilot-cli/.github/copilot-instructions.md
include clear ✅ Correct / ❌ Incorrect examples when relevant. ### Orchestration patterns (`orchestration/patterns/*.md`) Current repository convention: document the pattern, setup, examples, tradeoffs, and references in plain Markdown. ## Multi-AI Delegation - **Keep
bug-ops/mcp-execution/.github/copilot-instructions.md
GitHub Copilot Instructions for MCP Execution **Last Updated**: 2025-11-23 This document provides comprehensive guidelines for GitHub Copilot to generate high-quality code for the MCP Execution project, synthesizing
oak-invest/kiso/.github/copilot-instructions.md
Kiso aims to turn an OKF knowledge base into a structured, browsable, and usable documentation site. Kiso is also designed with AI usage in mind. Because the source remains structured
microsoft/GHCP-Lab/dotNet/.github/copilot-instructions.md
GitHub Copilot Guidelines for C# Development This document outlines the preferred coding style and conventions to be followed when generating C# code for this project. ## Type Declarations Prefer using explicit
microsoft/GHCP-Lab/.github/copilot-instructions.md
TypeScript type checking**: 1-2 seconds - NEVER CANCEL, use timeout of 60+ seconds - **Reading documentation**: 5-10 minutes per track ### Validation Scenarios **CRITICAL**: Do NOT validate by building or running
0xmariowu/Autosearch/.github/copilot-instructions.md
this repo - **Adding a check requires evidence.** Cite an Anthropic source, academic paper, or documented real-world failure in `standards/evidence.json`. Opinions are not acceptable. - **Scanner output is a contract.** Changing
microsoft/devsquad-copilot/.github/copilot-instructions.md
most generic - Not the most "future-flexible" 3. **When there is significant uncertainty**, document assumptions and request validation. 4. **Do not finalize non-trivial technical decisions without explicit approval** when
microsoft/devsquad-copilot/.github/plugins/devsquad/hooks/templates/.github/copilot-instructions.md
most generic - Not the most "future-flexible" 3. **When there is relevant uncertainty**, document assumptions and request validation. 4. **Do not finalize non-trivial technical decisions without explicit approval** when
microsoft/duroxide-pg/.github/copilot-instructions.md
provider_validation_test!` macro 5. **Test thoroughly**: `cargo test`, run flaky tests 10x 6. **Document as unreleased**: Add dependency and compatibility notes under `CHANGELOG.md`'s existing `[Unreleased]` section Dependency update
ssdeanx/AgentStack/.github/-/copilot-instructions.md
Copilot/Cursor instructions for working inside the Mastra repo
ssdeanx/AgentStack/.github/copilot-instructions.md
Mastra mcp tools use [#mastradocs], [#mastraChanges], [#mastraexamples] tool. - These tools provide access to Mastra documentation, recent changes, and code examples. - Use these tools to stay updated with the latest Mastra
Repository-wide instructions for GitHub Copilot, kept in .github/copilot-instructions.md.
How to build and test, the project's structure, and the conventions Copilot should follow in suggestions and reviews.
No. Copilot's coding agent also reads AGENTS.md, so many projects keep the shared rules there.
Open a file to see its discussion. Reports from people and their agents are coming.