| name | make-instructions |
| description | Create VS Code file-based instructions (.instructions.md files). Use when asked to create, scaffold, or add file-based instructions for Copilot. Generates .instructions.md with YAML frontmatter and background knowledge content. |
Create File-Based Instructions
This skill helps you scaffold VS Code file-based instructions (.instructions.md files) that provide background knowledge to Copilot about specific parts of the codebase. These files are applied automatically based on glob patterns or semantic matching, giving Copilot domain-specific context when working on matching files.
When Not to Use
- Setting project-wide instructions — use
.github/copilot-instructions.md or AGENTS.md instead
- Creating reusable agent workflows with structured steps — use Agent Skills instead
- Adding instructions that need to be invokable on demand — use Agent Skills instead
Workflow
Step 1: Investigate the topic
Build understanding of the area the instructions should cover. Identify:
If the scope is unclear or overlaps with existing instructions, ask the user for clarification.
Step 2: Choose the file location
Instructions files go in .github/instructions/ by default. Pick a descriptive filename:
.github/instructions/<topic>.instructions.md
Examples: csharp-style.instructions.md, query-pipeline.instructions.md, test-conventions.instructions.md
Step 3: Generate the file with YAML frontmatter
Create the file with the required YAML frontmatter header:
---
name: '<Display Name>'
description: '<Short description>'
applyTo: '<glob pattern>'
---
Common applyTo patterns:
**/*.cs — all C# filestest/** — files under a specific folder
Step 4: Write the body content
Write concise, actionable Markdown content. Follow these principles:
- Be concise — instructions share the context window; only include what the agent wouldn't already know
- Be specific — use concrete rules, not vague guidance
- Include examples — short code snippets showing preferred vs. avoided patterns are very effective
- Explain why — when a rule exists for a non-obvious reason, state it so the agent applies it correctly in edge cases
- Skip linter-enforced rules — don't repeat what formatters and linters already catch
- Use Markdown links to reference specific files or URLs for additional context
Recommended sections (adapt as needed):
- — one-line heading describing the domain
- Context paragraph — brief explanation of what this area is and why these rules matter
- Guidelines / Conventions — bullet list of concrete rules
- Examples — short code blocks showing do/don't patterns (optional)
- Key Files — table of important files for orientation (optional)
- Common Pitfalls — traps to avoid (optional)
Step 5: Validate
After creating the file, verify:
Common Pitfalls
| Pitfall | Solution |
|---|
applyTo too broad | Use specific globs; ** applies to every file and wastes context |
Missing applyTo | Without it, instructions won't auto-apply — they require manual attachment or semantic matching via description |
| Vague guidance | Replace "write good tests" with something like "add both positive and negative test cases using [ConditionalFact] methods" |
