Index of every page on this site: llms.txt
All skills
elithrar avatar

/wow-addon-development

@eb4f994
by Matt Silverlockelithrar/dotfiles226 stars
16
Run it yourself

Build, improve, debug, port, or review World of Warcraft Retail and official Forever add-ons. Use for addon Lua/XML, packaging, settings, persistence, performance, and in-game UI. Not for gameplay advice, addon recommendations, or WoW-themed websites.

Use this Skill: https://skilld.dev/gh/elithrar/dotfiles/wow-addon-development

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈69 tokens for metadata: the name and description. ≈1.2k when used: this file. ≈7.6k more on demand in 8 files.

Description uses 3.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈275 characters, or 3.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

WoW Add-on Development

Develop the requested behavior within the add-on's supported clients and repository conventions. Use the current checkout and latest accepted requirements as the baseline; older plans and screenshots may be superseded. Preserve planning or review-only scope; for implementation, continue from accepted decisions through verification.

Read what the task needs

Work Reference
Choose or change clients, APIs, events, or templates Clients and sources
Create/change a manifest or release package Manifest and packaging
Build or improve visual design, copy, controls, menus UI and settings
Persist or migrate settings/session state; switch or share profiles Profiles and transfer
Change animation, scheduling, caching, or CPU/memory use Performance and ownership
Change anchors, scaling, resizing, or scrolling Layout
Diagnose errors, check changed behavior, or investigate a regression Debugging and validation

Read the matching references before changing those areas. Load only the guidance needed for the task.

Choose the starting point

  • Existing feature or fix: Read the TOC, affected module, and nearest working example. Identify the state owner and actual user/event entry point. Preserve working conventions; establish the expected result or reported failure before editing.
  • New add-on: Establish the supported client, packaging needs, and the user's named reference or nearest working project convention. Reuse its applicable construction patterns for the first complete interaction; separate model logic, client adapters, and UI construction as those responsibilities arise.
  • Client port: Start with clients. Compare the affected APIs, events, templates, and saved-data meaning across targets. Isolate semantic differences in adapters; update packaging where needed.
  • Review: Read the changed paths and relevant references. Check requested behavior and repository conventions separately; report defects with evidence instead of applying unrequested edits.

Implement and verify

Verify unfamiliar or changed client contracts from matching documentation, reusing evidence checked for the same build. For implementation work, complete one behavior through its entry point, state change, and visible result before expanding it. Include persistence and recovery where the feature requires them.

Choose evidence for the behavior at risk: source and working references for construction, focused execution for logic and lifecycle, and in-client checks for unresolved engine behavior or requested visual acceptance. Fix source-identifiable defects without waiting for live access. Use the relevant validation checks to establish the requested outcome. Re-run the original scenario after a fix and check nearby behavior. Re-review the complete affected interaction against current requirements, including its settled appearance and transitional states; passing isolated checks is not acceptance of the whole feature. For a port, account for each affected contract on each supported client. A review finding should identify its location, trigger, and consequence.

Finish with the result, checks actually performed, and specific unresolved client checks. Distinguish inspected source, offline execution, and observed in-game behavior; identify any requested behavior still incomplete.

Shared constraints

  • Keep functions local or in the add-on namespace. Load prerequisites explicitly; do not depend accidentally on another installed add-on.
  • Initialize SavedVariables after restoration, in the matching ADDON_LOADED handler or the framework's documented initialization hook. Avoid capturing a file-scope defaults table that restoration later replaces.
  • Give frames, callbacks, recurring work, and cached data clear owners and lifetimes. Reuse UI objects and reconcile obsolete state when configuration changes.
  • Treat saved and imported configuration as versioned data. Validate before use, preserve valid user settings, and never evaluate an import string as Lua.
  • Separate secret-value restrictions from protected actions and combat lockdown. Check the target contract before consuming restricted values or changing protected UI; Blizzard implementation code may have privileges add-ons lack.

This skill supplies documentation only. Keep task-specific tests in the add-on's development environment.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts15d3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill provides comprehensive and secure guidance for World of Warcraft add-on development, following industry best practices and emphasizing security measures like input validation and avoiding dynamic code execution.

  • Socket15d

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at eb4f994. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated last month

README badge

README badge for elithrar/dotfiles/wow-addon-development