How do I install the Wow Addon Structure skill?

Run npx skillmds@latest add gabrielmoreira/wow-addon-structure in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Wow Addon Structure safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Wow Addon Structure?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Wow Addon Structure free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Wow Addon Structure?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Wow Addon Structure by gabrielmoreira

Name: Wow Addon Structure
Rating: 4.666666666666667 (3 reviews)
Author: gabrielmoreira

Wow 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.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

WoW AddOn Structure (Retail)

Scope

Retail only, current as of Patch 12.0.0.
Focuses on folder layout, .toc metadata, loading order, and SavedVariables.
Avoid deprecated or removed APIs and call out restricted directives.

When to use this skill

Use this skill when you need to:

Design or review an AddOn folder layout.
Author or audit a .toc file.
Reason about file load order and login events.
Wire SavedVariables or troubleshoot persistence.
Query or load AddOns via C_AddOns APIs.

How to use this skill

Start with layout and naming rules in references/ADDON_STRUCTURE.md.
Build the .toc file using references/TOC_FORMAT.md.
Plan initialization order with references/LOADING_LIFECYCLE.md.
Wire persistence with references/SAVED_VARIABLES.md.
Use C_AddOns metadata APIs from references/C_ADDONS_API.md.
Cross-check patterns in Blizzard UI source from references/VIEWING_BLIZZARD_UI.md.

Reference files

references/ADDON_STRUCTURE.md - Folder layout rules, naming, and common patterns.
references/TOC_FORMAT.md - .toc syntax, directives, and file order rules.
references/LOADING_LIFECYCLE.md - Load order, events, and login timeline.
references/SAVED_VARIABLES.md - Persistence rules and file locations.
references/C_ADDONS_API.md - Key C_AddOns metadata and load APIs.
references/VIEWING_BLIZZARD_UI.md - How to inspect Blizzard UI source.

Key rules and reminders

The AddOn folder name and .toc filename must match.
The .toc file is required and defines file load order.
Files load top to bottom in the .toc list.
SavedVariables are available after ADDON_LOADED unless LoadSavedVariablesFirst is used.
Use LoadOnDemand and C_AddOns.LoadAddOn for heavy modules.
Some .toc directives are restricted to Blizzard AddOns and are not available to third-party AddOns.

Sources

---name: wow-addon-structuredescription: 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.--- # WoW AddOn Structure (Retail) ## Scope - Retail only, current as of Patch 12.0.0. - Focuses on folder layout, .toc metadata, loading order, and SavedVariables. - Avoid deprecated or removed APIs and call out restricted directives. ## When to use this skill Use this skill when you need to: - Design or review an AddOn folder layout. - Author or audit a .toc file. - Reason about file load order and login events. - Wire SavedVariables or troubleshoot persistence. - Query or load AddOns via `C_AddOns` APIs. ## How to use this skill 1. Start with layout and naming rules in references/ADDON_STRUCTURE.md. 2. Build the .toc file using references/TOC_FORMAT.md. 3. Plan initialization order with references/LOADING_LIFECYCLE.md. 4. Wire persistence with references/SAVED_VARIABLES.md. 5. Use `C_AddOns` metadata APIs from references/C_ADDONS_API.md. 6. Cross-check patterns in Blizzard UI source from references/VIEWING_BLIZZARD_UI.md. ## Reference files - references/ADDON_STRUCTURE.md - Folder layout rules, naming, and common patterns. - references/TOC_FORMAT.md - .toc syntax, directives, and file order rules. - references/LOADING_LIFECYCLE.md - Load order, events, and login timeline. - references/SAVED_VARIABLES.md - Persistence rules and file locations. - references/C_ADDONS_API.md - Key `C_AddOns` metadata and load APIs. - references/VIEWING_BLIZZARD_UI.md - How to inspect Blizzard UI source. ## Key rules and reminders - The AddOn folder name and .toc filename must match. - The .toc file is required and defines file load order. - Files load top to bottom in the .toc list. - SavedVariables are available after `ADDON_LOADED` unless `LoadSavedVariablesFirst` is used. - Use `LoadOnDemand` and `C_AddOns.LoadAddOn` for heavy modules. - Some .toc directives are restricted to Blizzard AddOns and are not available to third-party AddOns. ## Sources - https://warcraft.wiki.gg/wiki/TOC_format - https://warcraft.wiki.gg/wiki/AddOn - https://warcraft.wiki.gg/wiki/AddOn_loading_process - https://warcraft.wiki.gg/wiki/SavedVariables - https://warcraft.wiki.gg/wiki/Viewing_Blizzard%27s_interface_code - https://warcraft.wiki.gg/wiki/World_of_Warcraft_API - https://github.com/Gethe/wow-ui-source/tree/live/Interface/AddOns/Blizzard_APIDocumentationGenerated

Frequently asked questions