wow-api-index
Skill75 starsChanged 13 days agoMITView on GitHub
Find source-pinned WoW functions, events, object methods, structures, enums and domain guidance across Retail, Forever and Classic progression. Use the packaged narrow-query tool and complete ownership routing before implementation.
In this repository42 other files it gives its agents.
- skills/agent-file-specs/references/AGENTS.mdAGENTS.md
- agent-file-specsSkill
- analyze-agent-overlapSkill
- generate-agent-docsSkill
- validate-agent-filesSkill
- wow-addon-developmentSkill
- wow-addon-structureSkill
- wow-api-achievementsSkill
- wow-api-calendar-eventsSkill
- wow-api-collectionsSkill
- wow-api-combatSkill
- wow-api-currency-economySkill
- wow-api-encountersSkill
- wow-api-escape-sequencesSkill
- wow-api-eventsSkill
- wow-api-framexmlSkill
- wow-api-group-lfgSkill
- wow-api-guildSkill
- wow-api-housingSkill
- wow-api-items-inventorySkill
- wow-api-lua-environmentSkill
- wow-api-map-navigationSkill
- wow-api-misc-systemsSkill
- wow-api-professionsSkill
- wow-api-pvpSkill
- wow-api-questsSkill
- wow-api-reputationSkill
- wow-api-settings-systemSkill
- wow-api-social-chatSkill
- wow-api-spells-abilitiesSkill
- wow-api-talentsSkill
- wow-api-transmogSkill
- wow-api-unit-playerSkill
- wow-api-weekly-rewardsSkill
- wow-api-widgetSkill
- wow-api-xml-schemaSkill
- wow-client-targetsSkill
- wow-controller-supportSkill
- wow-lua-apiSkill
- wow-macro-commandsSkill
- wow-native-uiSkill
- wow-ui-skinningSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Use controller support for required UI interaction assessment, native gamepad navigation, focus, action hints and per-client controller …
- Distinctive: line 30
Use FrameXML, widgets, XML, macros, settings/CVars and
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
WoW API index
Resolve the client/build with wow-client-targets. Start addon design or porting with wow-addon-development. A namespace name, source declaration or lexical mention is not evidence that an operation loads or is permitted for addons.
Current contracts
Use the current reference guide and package-local query tool to retrieve only the desired symbol's full typed contract and security annotations. The ledger includes every generated function, event, object method, structure, enum, callback type, constant group and predicate at the pinned target commits. It retains explicit unknown load/runtime/access states.
With Node.js 22+, run node <this-skill>/scripts/query.mjs forever C_Spell.GetSpellInfo or node <this-skill>/scripts/query.mjs forever SPELL_UPDATE_COOLDOWN --kind event. Exact queries return full records; namespace searches return bounded summaries unless --full is used. No Node dependency is needed to follow the domain JSON links directly.
| Reference | Purpose |
| Namespace lookup | Every declared C_ namespace, owner, target inventory and scope classification |
| Domain routing | All installed skills and complete namespace/global/object/data-system ownership |
| Category lookup | Task-oriented categories, including Mail and Macros |
| Current reference guide | Query usage, evidence meaning, structures, enums and representation rules |
| Maintenance | Reproducible regeneration and offline semantic checks |
Non-generated surfaces
Use controller support for required UI interaction assessment, native gamepad navigation, focus, action hints and per-client controller acceptance. Source declarations alone do not show that a custom panel is reachable or operable with a controller.
For task-level UI work, use native UI composition to select and assemble controls and UI skinning to restyle Blizzard-owned windows while preserving their behavior. The generated object-method ledger supplies contracts; these skills supply composition and lifecycle guidance.
Use FrameXML, widgets, XML, macros, settings/CVars and Lua/security for their separately sourced guides. Generated object methods do not enumerate all handwritten mixins, callbacks or template dependencies.
Follow current target-specific references first. Retained historical material is a research lead; never use it to override a pinned current signature or restriction. If a symbol is absent from the ledger, its status is unknown until loaded source and runtime evidence resolve it. Offline use must disclose the pinned build and untested behavior.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

