creating-copilot-packages

Create Copilot instruction files in two formats: repository-wide files as plain Markdown with no frontmatter, and path-specific files with YAML frontmatter containing `applyTo` glob patterns. Repository-wide instructions apply globally; path-specific instructions target specific file types or directories using patterns like `src/api/**/*.ts`.

Repository-wide instructions are plain Markdown files with no frontmatter and apply across your entire codebase. Path-specific instructions include YAML frontmatter with `applyTo` glob patterns to target specific directories or file types, ensuring Copilot receives contextually relevant guidance for different parts of your project.

Yes, path-specific Copilot instruction files support optional `excludeAgent` controls in their YAML frontmatter. This lets you prevent specific agents, such as coding or code review agents, from applying certain instructions to targeted file patterns.

Both repository-wide and path-specific Copilot instruction files support embedded code samples and example blocks. Include these examples in your Markdown or frontmatter-based instruction files to demonstrate expected patterns and guide Copilot's behavior for specific use cases.

Use glob patterns in the `applyTo` field of path-specific Copilot instructions when you need to apply guidance to particular file types or directories. For example, use `src/api/**/*.ts` to apply API development patterns only to TypeScript files in your API source tree.

No, repository-wide Copilot instruction files must be plain Markdown with no frontmatter. Only path-specific instruction files use YAML frontmatter with `applyTo` and optional `excludeAgent` fields to target specific file patterns and agents.