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

wow-api-widget

Skill75 starsChanged 13 days agoMITView on GitHub

Curated guide to the WoW Widget API (Retail). Focuses on core

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 11
  2. Distinctive:

    Every UI element needs the controller-support assessment, including focus/reachability and applicable activation, back, scrolling and text …

    line 15
  3. Distinctive:

    Verify frame type/method availability, inherited methods, widget script arguments, protected state and loaded templates.

    line 25
  4. Distinctive:

    Read the relevant row in compatibility guidance.

    line 27
  5. Distinctive:

    Use the pinned source schemas for complete generated contracts in this domain, including typed arguments, returns, event payloads and …

    line 31
  6. Distinctive:

    Use the current UI source and inheritance guide before treating a generated ScriptObject name as a frame type or applying a shared method …

    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 widget

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

Every UI element needs the controller-support assessment, including focus/reachability and applicable activation, back, scrolling and text entry. Preserve native gamepad behavior and visible state hints when changing widget scripts or artwork; verify the selected client's contracts before wiring input.

For choosing and assembling native controls, read native UI composition. For modifying Blizzard-owned windows, read UI skinning. Keep this skill for the underlying widget contracts and object methods.

For Forever 1.60.1.70707, also consult the current API and UI changes before applying earlier build guidance.

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

Preserve the accepted appearance with the custom artwork/native-control and screenshot comparison guide. Functional stock widgets are not a visual substitute for a materially different mock-up; verify both appearance and interaction.

Verify frame type/method availability, inherited methods, widget script arguments, protected state and loaded templates. Prefer simple verified primitives when a specialized widget is unavailable.

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 source schemas for complete generated contracts in this domain, including typed arguments, returns, event payloads and restrictions. Query only the needed symbols. Source declarations leave loading, runtime behavior and addon permission unresolved unless separately verified.

Use the current UI source and inheritance guide before treating a generated ScriptObject name as a frame type or applying a shared method to an arbitrary widget.

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:

  • ADVANCED WIDGETS
  • ANIMATION WIDGETS
  • BASE WIDGETS
  • FONT WIDGETS
  • FRAME CONTROLS
  • FRAME MODELS
  • FRAME SPECIALIZED
  • FRAME WIDGETS
  • SCRIPT HANDLERS
  • TEXTURE WIDGETS

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