make-instruction

Create GitHub Copilot instruction files with applyTo patterns and DO/DON'T rules.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/Luscii/terraform-fluentbit-luscii-presets --skill make-instruction-luscii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-instruction
Source: https://github.com/Luscii/terraform-fluentbit-luscii-presets/tree/main/.github/skills/make-instruction
Command: npx skills add https://github.com/Luscii/terraform-fluentbit-luscii-presets --skill make-instruction-luscii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams create GitHub Copilot instruction files with proper applyTo patterns and prescriptive rules, ensuring consistent guidance across codebases.

Core Features & Use Cases

  • Create properly structured .instructions.md with YAML frontmatter and prescriptive DO/DON'T patterns.
  • Enforce file-type scoping via applyTo frontmatter patterns to target specific languages or ecosystems.
  • Cross-reference related skills to extend guidance and avoid duplication.
  • Quick-start templates and scaffolding for common file types and projects.
  • Use cases include when a user asks to "create instruction", "scaffold instruction", or when building file-type-specific rules that should always apply.

Quick Start

Create a new instructions file under .github/instructions/{name}.instructions.md and populate it with a frontmatter block that includes an applyTo pattern, followed by prescriptive rules (DOs/DON'Ts). Ensure the content is concise (100-800 lines) and includes cross-references to related skills.

Frequently Asked Questions about make-instruction

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create GitHub Copilot instructions with applyTo patterns for specific file types?

GitHub Copilot instruction files require YAML frontmatter with an applyTo pattern for file-type scoping, followed by prescriptive DO and DON'T rules. You generate these as .instructions.md files to enforce consistent guidance across your codebase.

What is the applyTo frontmatter pattern used for in Copilot instruction files?

The applyTo frontmatter pattern scopes GitHub Copilot instructions to specific file types or languages within a project, ensuring generated guidance only applies when developers edit matching files in that ecosystem.

How do I scaffold prescriptive DO and DON'T rules for a new codebase?

Scaffold prescriptive rules by creating a file under .github/instructions/{name}.instructions.md, populating it with required frontmatter, and defining explicit DO and DON'T sections to enforce strict coding standards for Copilot.

Does GitHub Copilot instruction generation work with cross-references to other instruction files?

Yes, GitHub Copilot instruction generation supports cross-references to related skills within the prescriptive rules, extending guidance across different file types while avoiding duplicated instructions across your GitHub projects.

What are the line length limitations for GitHub Copilot instruction files?

GitHub Copilot instruction files must stay within 100 to 800 lines to remain concise. Exceeding this limit risks diluting the prescriptive rules and reducing the effectiveness of the applyTo scoping patterns.

When do I need to generate custom Copilot instructions instead of using default suggestions?

You need custom Copilot instructions when your team requires strict file-type-specific rules that always apply. Generating custom .instructions.md files enforces consistent prescriptive guidance that default Copilot suggestions cannot guarantee.