agentleFS
Sign inStart free
JBurlisonJBurlison/WoWAddonAPIAgents/skills/wow-api-xml-schema/SKILL.md

wow-api-xml-schema

Skill75 starsChanged 13 days agoMITView on GitHub

Look up the World of Warcraft XML schema — all XML elements,

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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
  1. Distinctive:

    Use for any selected combination of Retail, Forever, and Classic progression.

    line 19
  2. Distinctive:

    Use visual fidelity for custom artwork, native controls, layering and comparison with the accepted mock-up.

    line 25
  3. Distinctive:

    Verify the selected branch XML schema, templates, includes, script handlers and client load conditions.

    line 27
  4. Distinctive:

    Read the relevant row in compatibility guidance.

    line 29
  5. Distinctive:

    Use the pinned per-client schemas and template loading guide for current evidence.

    line 33

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

api xml schema

Use for any selected combination of Retail, Forever, and Classic progression. First resolve the target and pinned source with wow-client-targets.

Target-specific decisions

For visible UI changes, use the mock-up choice and UIForever workflow before production implementation and during visual testing.

Use visual fidelity for custom artwork, native controls, layering and comparison with the accepted mock-up. A schema-valid template does not establish that its appearance matches the design.

Verify the selected branch XML schema, templates, includes, script handlers and client load conditions. A valid XML element in Retail may not be available in another client.

Read the relevant row in compatibility guidance. Verify only the APIs needed for this task, using commit-pinned definitions and loaded client code. Missing evidence means unknown, not supported or removed. When offline, disclose the snapshot version/date and unresolved behavior.

Detailed lookup material

Use the pinned per-client schemas and template loading guide for current evidence. XML type inheritance, template inheritance and Lua mixins must be checked separately.

The historical Retail baseline retains the original API listings and examples. It is a research aid, not current or cross-client verification. Open only relevant supporting references:

  • XML ANIMATIONS
  • XML FONTS
  • XML FOUNDATION
  • XML FRAME TYPES
  • XML REGIONS

For implementation and release validation, use wow-addon-development.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free