copilot-file-specs

Document authoritative specifications for AI coding assistant customization files.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/Reign-software/hyforged --skill copilot-file-specs-reign-software
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilot-file-specs
Source: https://github.com/Reign-software/hyforged/tree/main/.github/skills/copilot-file-specs
Command: npx skills add https://github.com/Reign-software/hyforged --skill copilot-file-specs-reign-software

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authoritative, centralized specifications for AI coding assistant customization files across providers.

Core Features & Use Cases

  • Reference complete file-type formats, required fields, and provider-specific locations for agents, prompts, instructions, and skills.
  • Guide integration: reuse across Copilot, Claude Code, Codex, and OpenCode environments.
  • Use cases include verifying directory structures, frontmatter schemas, and file-type mappings when building custom configurations.

Quick Start

Consult the official file-specs to reference correct formats and locations when creating or modifying customization files.

Frequently Asked Questions about copilot-file-specs

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

FAQPage Schema
What are the required frontmatter fields for a SKILL.md customization file?

Standardized file-specs define mandatory frontmatter fields for SKILL.md files, requiring attributes like name and description. This ensures AI coding assistant configurations are correctly parsed across different provider environments.

How do I configure AI coding assistant files for multiple providers like Copilot and Claude Code?

To configure AI coding assistant files across providers like Copilot and Claude Code, reference centralized specifications for correct file-type formats, required fields, and provider-specific directory locations to ensure proper integration.

Where are the correct file locations for agents, prompts, and instructions in GitHub Copilot?

Correct file locations for agents, prompts, and instructions in GitHub Copilot are documented in authoritative file-specs. These specifications reference exact directory structures and file-type mappings required for custom configurations.

Does the file-specs schema work with OpenCode and Codex environments?

The file-specs schema explicitly applies to OpenCode and Codex environments. It provides standardized formats, required fields, and file locations to guide seamless integration and reuse across these specific provider ecosystems.

Why do my AI coding assistant customizations fail to load across different provider ecosystems?

Customizations fail when file formats, frontmatter schemas, or directory structures do not match provider specifications. Consulting authoritative file-specs helps verify correct file-type mappings and required fields for your target environment.