smithery/falkicon

s-develop

Core WoW addon development patterns using Ace3 framework and Blizzard UI APIs. Covers event-driven design, SavedVariables, frame architecture, and API resilience. Use when building addons, designing systems, or integrating libraries.

Installation

$ npx skills add smithery/falkicon --skill s-develop

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/falkicon · top by installs.

npx skills add smithery/falkicon

Browse all from smithery/falkicon

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,850 B
  • docs SUMMARY.md 327 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Developing WoW Addons

Expert guidance for building World of Warcraft addons with a focus on testability and maintenance.

Related Commands

  • [c-develop](../../commands/c-develop.md) - Build or extend addon features workflow

CLI Commands (Use These First)

MANDATORY: Always use CLI commands before manual exploration.

Task Command
Create Addon mech call addon.create -i '{"name": "MyAddon"}'
Sync Junctions mech call addon.sync -i '{"addon": "MyAddon"}'
Validate TOC mech call addon.validate -i '{"addon": "MyAddon"}'
Check Libraries mech call libs.check -i '{"addon": "MyAddon"}'
Sync Libraries mech call libs.sync -i '{"addon": "MyAddon"}'

Capabilities

  1. Event-Driven Design — Register events, handle callbacks, bucket patterns
  2. Frame Architecture — Three-layer design (Core/Bridge/View), layouts, templates
  3. SavedVariables — Database design, AceDB, versioning, defaults
  4. Combat Lockdown — Protected functions, taint avoidance, secure handlers
  5. API Resilience — Defensive programming, C_ namespaces, secret values

Routing Logic

Request type Load reference
Addon architecture, layers [../../docs/addon-architecture.md](../../docs/addon-architecture.md)
Event registration, callbacks [references/event-patterns.md](references/event-patterns.md)
Frame creation, UI engineering [references/frame-engineering.md](references/frame-engineering.md)
SavedVariables, AceDB [references/saved-variables.md](references/saved-variables.md)
Combat lockdown, secure code [references/combat-lockdown.md](references/combat-lockdown.md)
Blizzard API, C_ namespaces [references/api-patterns.md](references/api-patterns.md)
MechanicLib integration [../../docs/integration/mechaniclib.md](../../docs/integration/mechaniclib.md)
Performance profiling [../../docs/integration/performance.md](../../docs/integration/performance.md)

Quick Reference

Create New Addon

mech call addon.create -i '{"name": "MyAddon", "author": "Name"}'
mech call addon.sync -i '{"addon": "MyAddon"}'

Core Principles

  1. Headless Core: Keep logic in pure Lua functions (Layer 1)
  2. Event-Driven: Avoid OnUpdate polling; use events (Layer 2)
  3. Defensive API: Always check for nil and use pcall for uncertain APIs
  4. Combat Aware: Never modify protected frames in combat