---
name: "copilot-workspace-instruction-spec"
description: "Author `.github/copilot-instructions.md` for consistent team-wide AI code generation."
metadata:
  author: "GitHub"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "create copilot instructions file"
  - "configure .github/copilot-instructions.md"
  - "set team copilot standards"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# GitHub Copilot Custom Repository Instructions

Configures repository-level guidance for GitHub Copilot in `.github/copilot-instructions.md`: architectural conventions, testing standards, package manager rules, and security guidelines.

## When to Invoke
Invoke this skill whenever you need to:
- create copilot instructions file
- configure .github/copilot-instructions.md
- set team copilot standards

## Execution SOP & Rules
1. Place instruction file at the standardized path: .github/copilot-instructions.md.
2. Document the designated package manager (pnpm, yarn, npm, bun) to prevent lockfile conflicts.
3. Detail preferred testing frameworks, mocking libraries, and test file naming conventions.
4. Keep instructions concise, actionable, and free of vague generalizations.

## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.