How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
ashp15205Copilot instructionsashp15205/vibe-coding-essentials/templates/copilot-instructions.md
inline comments for non-obvious logic. - For multi-step operations, break into named steps. ## Security - Never complete patterns that include hardcoded secrets, passwords, or API keys. - Flag SQL string interpolation
event4u-appCopilot instructionsevent4u-app/agent-config/.github/copilot-instructions.md
invocation: true` on commands** — required marker, do not remove. **What TO flag:** code defects, security issues, broken tests, type errors, and any new `.agent-src.uncondensed/` substring introduced into `dist/agent-src/rules/` body content
GitHubCopilot instructionsgithub/hooks/.github/copilot-instructions.md
changes. - Make special note of any changes to dependencies. - Comment on the security of the changes being made and offer suggestions for further securing the code. ## Repository Organization - `.github/` - GitHub
MicrosoftCopilot instructionsmicrosoft/ACESEvals/.github/copilot-instructions.md
Naming:** The external name for this project is **ACES** (Agent Capability Evaluation Suite). **SABER** (Security Agent Benchmarking and Evaluation Research) is the internal Microsoft codename. The Python package, CLI commands
MicrosoftCopilot instructionsmicrosoft/ai-cheatcode/.github/copilot-instructions.md
Raghav BN | Mar 31 | | 003 | Prompt-Chained Triage + Playbooks | 🔧 | Raghav BN | Apr 7 | | 004 | Secure In-Boundary Processing | 🧠 | Raghav BN | Apr 14 | | 005 | Human-in-the-Loop Approval Gates | 🧠 | Pete
paulasilvatechCopilot instructionspaulasilvatech/awesome-harness-primitives/.github/copilot-instructions.md
either contract, update that specification before dependent guidance. An explicit user requirement or stricter security policy wins for the requested change. ## Repository Purpose and Layout This repository curates reusable GitHub
rajnandan1Copilot instructionsrajnandan1/ken/.github/copilot-instructions.md
brute-force about: input validation at trust boundaries, error handling that prevents data loss, security, accessibility, or user requirements. Never rewrite what you don't yet understand: trace the unit
rajyramanCopilot instructionsrajyraman/mcp-dataverse/.github/copilot-instructions.md
include details like logical name, schema name<, display name, description, object type code etc. # Security Guidelines - Do not show any sensitive information like Secret, Client/Application Id, Password, or Tenant
wuemaikblumeCopilot instructionswuemaikblume/dsgvo-skills/codex/copilot-instructions.md
MD5/SHA1/SHA256-pur. Pepper im Secret-Manager, Salt automatisch. 2. **Setzt der Code Session-Cookies?** → `HttpOnly`, `Secure`, `SameSite=Lax` (Default) oder `Strict` (Admin). Session-IDs aus `crypto.randomBytes(32)`, nicht JWT in Cookie
fritzprixCopilot instructionsfritzprix/libr-agent/.github/copilot-instructions.md
Ecosystem**: Planning, Knowledge, Browser, Workspace, Code Execution - **MCP Integration**: Session-isolated stdio/HTTP protocol with security validation ## Technology Stack **Core Framework:** - PNPM (Package Manager) - Tauri 2.x (Latest cross-platform desktop
mantacronCopilot instructionsmantacron/manta/.github/copilot-instructions.md
writing code; the agent pipeline runs automatically via git hooks (Claude Code). --- ## Principles 1. **Security by default** — never trust external input; sanitize all user-supplied data before use; never hardcode
MicrosoftCopilot instructionsmicrosoft/slack-plus-teams/.github/copilot-instructions.md
example code and knowledge-base Markdown. Only flag issues that would cause runtime failures, security vulnerabilities, or silently wrong behavior. Do NOT comment on style, naming, minor inconsistencies, missing docs
pkeffectCopilot instructionspkeffect/Antigravity-Architect/.github/copilot-instructions.md
updates `VERSION` constant, `pyproject.toml`, creates git commit and tag. ## Project-Specific Patterns ### 1. Sanitization & Security All user inputs MUST be sanitized via `sanitize_name()` which: - Removes special characters except
RealistSecCopilot instructionsRealistSec/mpa-first-guidelines/.github/copilot-instructions.md
Content - **Preserve the document structure** - The current flow (Prime Directive → HTML → CSS → PHP → JS → Security) is intentional - **Keep code examples modern** - Target current 2025-26 web standards (PHP 8.1+, ES2020
aiperceivableCopilot instructionsaiperceivable/apflow/.github/copilot-instructions.md
Linting - After changes, always run: - ruff check --fix . - black . - pyright . - Zero errors/warnings before commit. ### Security & Performance - Never hardcode secrets; use env/config. - Validate/sanitize inputs. - Avoid unjustified quadratic+ complexity in hot paths
bocanCopilot instructionsbocan/codex/.github/copilot-instructions.md
registered tools (pages, folders, attachments) - **Resources**: Access pages via `codex://page/{path}` URIs - **Security**: API key authentication via `MCP_API_KEY` environment variable **Tool registration pattern**: All tools imported
bradleybond512Copilot instructionsbradleybond512/crystal-ball/.github/copilot-instructions.md
dedicated Claude AI Panel. All panel summaries use the primary fallback chain above. --- ## Security Guidelines - **Never commit secrets** — use `.env.local` or Vercel/GitHub environment variables - **Secret scan is mandatory** — this
brianonbased-devCopilot instructionsbrianonbased-dev/HoloScript/.github/copilot-instructions.md
thermal_simulation @fluid_simulation NETWORKING: multiplayer @networked @synced @persistent @owned @host_only @replicated security @zero_knowledge_proof @vulnerability_scanner @audit_log @encryption ``` ## Completion Patterns ### .hsplus Object ```hsplus object @ @ { geometry: '<cube
dgenioCopilot instructionsdgenio/contextweaver/.github/copilot-instructions.md
list. - **Routing Engine** — sync-only, pure computation. Do not make async. - **Sensitivity enforcement** (`context/sensitivity.py`) — security-grade code. Never weaken defaults. See `.github/instructions/sensitivity.instructions.md`. - **Minimal core runtime deps.** Core install: `tiktoken`, `PyYAML
fusebase-devCopilot instructionsfusebase-dev/fusebase-flow/.github/copilot-instructions.md
templates, provider/runtime precedence, active project context, and update safety are indexed from `AGENTS.md`. Scoped security and validation instructions live in `.github/instructions/`. Copilot has no native Flow lifecycle hooks in this
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.
