create-custom-instruction

Create and review VS Code custom instruction files with frontmatter and glob rules.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Binh230199/ai --skill create-custom-instruction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-custom-instruction
Source: https://github.com/Binh230199/ai/tree/main/.github/skills/create-custom-instruction
Command: npx skills add https://github.com/Binh230199/ai --skill create-custom-instruction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create, update, and review VS Code custom instruction files so Copilot applies the right coding guidance in the right place.

Core Features & Use Cases

  • It explains the correct file formats for always-on project instructions and file-scoped instruction files.
  • It clarifies where to place instructions for workspace-wide standards, language-specific rules, and folder-specific conventions.
  • It guides you on writing effective frontmatter, choosing precise glob patterns, and structuring rules that are easy for Copilot to discover and apply.
  • It is useful when you need to add team coding standards, update project guidance, or target instructions to a specific file type or module.

Quick Start

Ask for a VS Code custom instruction file that targets your intended scope and follows the correct .github placement and frontmatter rules.

Frequently Asked Questions about create-custom-instruction

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

FAQPage Schema
How do I create VS Code custom instructions for Copilot coding standards?

To create VS Code custom instructions for Copilot, generate a copilot-instructions file with correct frontmatter and applyTo glob patterns, placing it in the .github directory for project-wide standards or using file-scoped rules for specific languages and folders.

What is the applyTo frontmatter field in Copilot custom instruction files?

The applyTo frontmatter field defines glob rules that target where Copilot applies specific coding guidance, allowing file-scoped instructions to auto-apply based on language, framework, or folder-specific patterns within the workspace.

Where should I place Copilot instruction files for workspace-wide standards?

Workspace-wide Copilot instruction files should be placed in the .github directory using correct naming conventions, while file-scoped instruction files are structured for specific languages, frameworks, and folder-specific patterns to ensure discoverability.

Can I target Copilot instructions to a specific file type or module?

Yes, you can target Copilot instructions to specific file types or modules by writing effective frontmatter with precise applyTo glob patterns, structuring the rules so Copilot can automatically discover and apply them to the intended scope.

What is the best way to structure file-scoped Copilot instructions for a framework?

The best way to structure file-scoped Copilot instructions for a framework is to use correct frontmatter, choose precise glob patterns for the applyTo field, and follow proper naming and placement conventions for discoverable auto-applied rules.

Why are my Copilot custom instructions not applying to the correct files?

Copilot custom instructions may not apply correctly if the frontmatter is missing, the applyTo glob patterns are imprecise, or the instruction files are not placed in the correct .github directory or folder-specific locations for discoverability.