k-docs

10

Falkicon

Index of Mechanic documentation with summaries and links. Load this to understand what documentation exists and where to find detailed information on specific topics. Triggers: docs, documentation, reference, guide, help.

s-research

10

Falkicon

Research WoW addon development topics using CLI tools, Blizzard UI source, and documentation. Covers API discovery, pattern research, and Ace3 usage. Use when investigating unfamiliar APIs, finding Blizzard patterns, or learning. Triggers: research, find, search, API, Blizzard UI, documentation, Ace3.

s-release

10

Falkicon

Prepare and execute an addon release, including version bumping, changelog updates, git tagging, and validation. Use when ready to publish a new version. Triggers: release, version bump, changelog, git tag, publish.

s-audit

10

Falkicon

Comprehensive quality analysis for WoW addons. Combines security, complexity, deprecation, and dead-code analysis into a single audit workflow. Triggers: audit, quality, analysis, review, check, scan.

k-mechanic

10

Falkicon

Context for Mechanic - the WoW addon development hub. Covers the CLI, MCP server, dashboard, in-game modules, and MechanicLib. Load this for deep understanding of Mechanic tooling. Triggers: mechanic, mech, cli, mcp, dashboard, tools, development hub.

k-fenui

10

Falkicon

Context for FenUI - the UI widget library for WoW addons. Covers frames, layouts, buttons, panels, and theming. Load this when building addon UI or working with FenUI widgets. Triggers: fenui, ui, widget, frame, layout, panel, button, tabs.

s-clean

10

Falkicon

Find and remove dead code and stale documentation. Covers unused functions, orphaned files, dead links, and outdated references. Use for maintenance, pre-release cleanup, or codebase hygiene. Triggers: clean, dead code, unused, orphan, stale, cruft, maintenance.

s-test

10

Falkicon

Write and run unit tests for WoW addons using Busted and the Mechanic test framework. Covers test structure, mocking WoW APIs, and coverage analysis. Use when adding tests, fixing bugs with regression tests, or improving coverage. Triggers: test, unit test, coverage, Busted, mock, TDD, sandbox.

s-develop

10

Falkicon

Core WoW addon development patterns using the 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. Triggers: addon, WoW, Lua, Ace3, frame, event, SavedVariables, architecture.

k-fencore

10

Falkicon

Context for FenCore - the pure-logic library for WoW addons. Covers utility functions, math helpers, table operations, and environment detection. Load this when working with FenCore or needing utility functions. Triggers: fencore, utility, math, table, logic, pure functions.

s-lint

10

Falkicon

Ensure code quality using Luacheck linting and StyLua formatting. Covers common warnings, style rules, and auto-formatting. Use when checking code quality, fixing style issues, or preparing code for review. Triggers: lint, format, style, luacheck, stylua, code quality, warnings.

k-ecosystem

10

Falkicon

Context for the Mechanic/Fen WoW addon development ecosystem. Covers all components (Mechanic, FenCore, FenUI, MechanicLib), their relationships, and AFD principles. Load this at the start of addon work. Triggers: ecosystem, fen, fencore, fenui, mechanic, addon, context.

k-create-skill

10

Falkicon

Meta knowledge for creating Claude skills. Provides templates, best practices, and patterns for building effective skills with routing tables and reference files. Load this when creating new skills or understanding the skill system. Triggers: create skill, new skill, skill template, skill architecture, SKILL.md.

s-debug

10

Falkicon

Diagnose and fix bugs using an evidence-based investigation. Requires collecting runtime evidence before making fixes—never guess from code alone. Covers hypothesis-driven debugging, runtime instrumentation and structured logging, Lua error and stack-trace analysis, taint issues and combat lockdown, and API failures or deprecations (e.g., Midnight 12.0 preparation). Triggers: error, bug, debug, fix, crash, taint, nil value, diagnose, hypothesis, runtime, evidence, instrumentation.