How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
gjovanovicstReads credentialsCopilot instructionsgjovanovicst/golang-auth-api/.github/copilot-instructions.md
changing handlers. Run `swag init` (often implied or manual) to regenerate docs in `docs/`. - **Security**: - Use `internal/middleware` for JWT validation & RBAC. - Don't expose raw GORM errors to API clients
hiromailyCopilot instructionshiromaily/go-crypto-wallet/.github/copilot-instructions.md
cryptocurrency wallet implementation supporting BTC, BCH, ETH, XRP, and ERC-20 tokens. **Security is paramount** - this project handles private keys and cryptocurrency transactions. ## Quick Reference - **Architecture**: Clean Architecture with clear
harnessCopilot instructionsharness/harness-skills/.github/copilot-instructions.md
/enforce-sbom` | Add SBOM Policy Enforcement (verify attestation + OPA policy sets) | | `/manage-artifacts` | Artifact registry setup, security scanning, and cross-region replication | | `/manage-cde` | Cloud development environments, workspace templates, and auto-hibernation | | `/manage-delegates
cmgraybCopilot instructionscmgrayb/hass-dyson/.github/copilot-instructions.md
leverages asynchronous programming to ensure non-blocking operations within Home Assistant. The design prioritizes security, maintainability, and adherence to Home Assistant's integration guidelines. The integration should handle ONLY
InfomaniakCopilot instructionsInfomaniak/desktop-kDrive/.github/copilot-instructions.md
MCP/tool is available. - Treat new SonarCloud issues as review-relevant context, especially correctness, reliability, security, and maintainability issues. - Never guess, infer, fabricate, or reconstruct SonarCloud findings from code alone. Only
wangdage12Copilot instructionswangdage12/Snap.Hutao/.github/copilot-instructions.md
gracefully. - XAML: Reuse existing styles/resources; keep bindings simple and observable; avoid UI thread blocking. - Security & privacy: Don’t log secrets or game tokens; follow existing storage conventions. --- ## Localization and strings
Prism-ShadowReads credentialsCopilot instructionsPrism-Shadow/agenthub/.github/copilot-instructions.md
authenticate with the respective AI model providers. Make sure to handle these credentials securely and never log or expose them in test output
MicrosoftCopilot instructionsmicrosoft/AntiSSRF/.github/copilot-instructions.md
coding assistant AI that **follows the company’s Security Development Lifecycle (SDL) guidelines** for secure coding. **Always apply the following practices when generating source code:** - **Use approved frameworks & libraries:** Leverage
javiarmestoCopilot instructionsjaviarmesto/ALDC-AL-Development-Collection/.github/copilot-instructions.md
Event subscribers, publishers, handled pattern | al-developer, al-architect | | `skill-permissions` | Permission sets, XLIFF, security | al-developer | | `skill-pages` | Page types, FastTabs, actions, dynamic UI | al-developer | | `skill-migrate
javiarmestoCopilot instructionsjaviarmesto/ALDC-AL-Development-Collection/instructions/copilot-instructions.md
Event subscribers, publishers, handled pattern | al-developer, al-architect | | `skill-permissions` | Permission sets, XLIFF, security | al-developer | | `skill-pages` | Page types, FastTabs, actions, dynamic UI | al-developer | | `skill-migrate
putervisionCopilot instructionsputervision/state-memory-mcp/.github/copilot-instructions.md
read/write access to the workspace's local `.vision-memory-mcp/` cache directory. # Cryptographic Vault & Security (webcrypt-mcp) This project provides native `webcrypt-mcp` tooling for zero-dependency
MicrosoftReads credentialsCopilot instructionsmicrosoft/Agent365-Samples/.github/copilot-instructions.md
Rule 2 (Copyright headers) - Apply all three rules together when reviewing sample code - Prioritize security checks (no secrets) above all other validations
Perfect-AbstractionsCopilot instructionsPerfect-Abstractions/Compose/.github/copilot-instructions.md
changes, 2 for breaking/critical. - LABELS: Apply appropriate labels (bug, enhancement, docs, security, breaking-change, chore). - COMPATIBILITY: Preserve externally observable standard behavior (events, errors, return values). - STORAGE: Reuse structs by copying
MicrosoftCopilot instructionsmicrosoft/haste/.github/copilot-instructions.md
Satellite imagery, GDAL/rasterio, provider adapters, damage assessment | Yes | | `ui` | React/FluentUI/Azure Maps/MSAL, frontend only | Yes | | `security` | Dependabot alerts, CVE analysis, dependency audits. Never auto-merges. | No (reports only) | ### Validation Agents | Agent
MicrosoftCopilot instructionsmicrosoft/PromptKit/.github/copilot-instructions.md
tasks (anti-hallucination, self-verification, operational-constraints) - **`analysis/`** — Domain/language-specific checks (memory-safety-c, security-vulnerability). Language-specific protocols are separate files, not conditional blocks. - **`reasoning/`** — Systematic reasoning approaches (root-cause
Microsoft AzureCopilot instructionsAzure/agent-app-orchestrator/.github/copilot-instructions.md
under `src/strategies/`. ## Working rules - Confirm the goal, acceptance criteria, constraints, current behavior, and affected security or compatibility boundaries. - Reuse repository patterns and tools. Make small, complete changes without unrelated refactoring
haruCopilot instructionsharu/redmine_ai_helper/.github/copilot-instructions.md
prompt templates (EN/JP) - `config/ai_helper/config.json` — MCP server configuration - `config/ai_helper/config.yml` — Langfuse configuration ## Critical Implementation Details **Frontend Security:** - Build HTML structures in ERB templates (`*.html.erb`), not in JavaScript - This prevents
MicrosoftCopilot instructionsmicrosoft/edge-ai/.github/copilot-instructions.md
Comprehensive coding guidelines and instructions for edge ai - Brought to you by microsoft/edge-ai
Microsoft AzureCopilot instructionsAzure/Azure-Landing-Zones/.github/copilot-instructions.md
Component | Bicep Registry Module | Type | |-----------|----------------------|------| | Management group hierarchy (int-root, platform, connectivity, identity, management, security, landing zones, corp, online, sandbox, decommissioned) | `br/public:avm/ptn/alz/empty` | Pattern | **Logging:** | Component | Bicep Registry Module | Type
layer5ioDeletes or force-pushesCopilot instructionslayer5io/docs/.github/copilot-instructions.md
alert type="success" title="Note" >}} Your Note {{< /alert >}} ``` Alert types: - `type="danger"`: Critical alerts (security-related or breaking changes) - `type="info"`: General informational content - `type="warning"`: Important warnings that need
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.
