agent-file-specs
AI Coding Assistant Customization File Specifications
This skill provides the authoritative, up-to-date specifications for all AI coding assistant customization file types. Each file type has its own dedicated reference document with complete attribute tables, validation rules, examples, and best practices.
Standard: These specs align with the Agent Skills open standard and the VS Code Copilot customization documentation.
How to Use This Skill
- Read the Quick Reference below to identify the file type you need.
- Follow the link to the dedicated reference document for full details.
- Use the File Locations reference when you need to know where files go for a specific provider.
- Use the Settings reference for VS Code configuration.
Important: Detailed specifications live in the
references/folder — not in this file. This keeps the main skill file lightweight for efficient context loading per the progressive disclosure model.
Quick Reference
| Type | Extension | Purpose | Reference |
|---|---|---|---|
| Agent | .agent.md / .md |
Custom AI personas with specialized behaviors, tool restrictions, and handoff workflows | AGENTS.md |
| Skill | SKILL.md (directory-based) |
Reusable, portable capabilities with scripts and resources — follows the Agent Skills open standard | SKILLS.md |
| Prompt | .prompt.md |
Reusable prompt templates invoked as slash commands | PROMPTS.md |
| Instruction | .instructions.md |
Contextual guidance applied automatically by file type or description | INSTRUCTIONS.md |
| File Locations | — | Provider folder mapping, directory structure, naming conventions | FILE-LOCATIONS.md |
| VS Code Settings | — | Settings that control customization file discovery and behavior | SETTINGS.md |
Provider Support
These specifications work across multiple AI coding assistant providers. Each provider uses its own base folder but the file formats are consistent:
| Provider | Base Folder |
|---|---|
| GitHub Copilot | .github/ |
| Claude Code | .claude/ |
| Codex | .codex/ |
| OpenCode | .config/opencode/ |
See FILE-LOCATIONS.md for the complete directory structure and provider-specific details.
File Type Selection Guide
Use this decision tree to choose the right file type:
-
"I want coding standards applied everywhere" → Use always-on instructions (
.github/copilot-instructions.mdorAGENTS.md). See INSTRUCTIONS.md. -
"I want different rules for different file types" → Use file-based instructions (
.instructions.mdwithapplyTopatterns). See INSTRUCTIONS.md. -
"I have a reusable task I run repeatedly" → Use a prompt file (
.prompt.md) invoked as a slash command. See PROMPTS.md. -
"I need a multi-step workflow with scripts and resources" → Use an Agent Skill (directory with
SKILL.md). Portable across tools. See SKILLS.md. -
"I need a specialized AI persona with tool restrictions" → Use a custom agent (
.agent.md). Supports handoffs for multi-step workflows. See AGENTS.md.
Authoritative Sources
More from jburlison/wowaddonapiagents
wow-lua-api
Verbose guide to Lua 5.1 functions available in WoW, including Blizzard-specific differences and WoW-only additions. Use for core Lua behavior in the WoW addon environment.
33wow-addon-structure
Verbose guide for WoW Retail AddOn structure, .toc metadata, loading order, SavedVariables, and C_AddOns metadata and load APIs. Use when planning addon folder layout, file order, or SavedVariables wiring.
23wow-api-currency-economy
Complete reference for WoW Retail Currency, Auction House, Token, Store, Trading Post, Black Market, Mail, and Player Trading APIs. Covers C_CurrencyInfo (currency data, tracking, backpack), Auction House (full listing/bidding/buying/selling/search/commodity), C_WowTokenPublic (WoW Token market), AccountStore (in-game shop), CatalogShop, C_PerksProgram (Trading Post — Trader's Tender), BlackMarket (BMAH), TradeInfo (player trading), MailInfo (mailbox), and related events. Use when working with currencies, auction house UI, WoW Tokens, the in-game store, Trading Post, black market, mail, or player-to-player trading.
15wow-api-map-navigation
Complete reference for WoW Retail Map, Navigation, Area POI, Taxi, Vignette, Minimap, Nameplate, Waypoint, Zone Ability, Fog of War, and Exploration APIs. Covers C_Map (50+ functions for map data, coordinates, map IDs, area info), C_MapExplorationInfo, C_AreaPoiInfo, C_TaxiMap (flight paths), C_Vignette, C_SuperTrackManager, C_Navigation (in-game navigation), C_ZoneAbility, C_FogOfWar, Minimap functions, C_NamePlateManager, and coordinate conversion. Use when working with maps, coordinates, waypoints, flight paths, minimap, nameplates, vignettes, exploration, zone abilities, or in-game navigation.
11wow-api-combat
Complete reference for WoW Retail Combat, Damage Meter, Threat, Loss of Control, Combat Text, Combat Audio Alert, Secret Values, and Spectator APIs. Covers the 12.0.0 combat log removal (CLEU no longer available to addons), C_DamageMeter built-in damage meter, C_Secrets secret predicates, C_CurveUtil/C_DurationUtil for secret value visualization, C_LossOfControl, C_CombatText, C_CombatAudioAlert, ENCOUNTER_STATE_CHANGED, threat functions, and the new COMBAT_LOG_MESSAGE event. Use when working with combat data, damage meters, threat, loss of control, combat text, encounter events, or any combat-related addon functionality.
10wow-api-lua-environment
Complete reference for the WoW Lua 5.1 runtime environment, restrictions, secure execution, taint system, addon security model, timers, hooks, frame scripting, logging, and restricted actions. Covers hooksecurefunc, C_Timer, securecallfunction, issecurevariable, taint propagation, combat lockdown, protected frames, InCombatLockdown, C_RestrictedActions, C_Log, and the FrameScript sandbox. Use when working with Lua restrictions, secure code, taint, timers, hooks, addon security, debugging, or the WoW Lua sandbox.
10