k-mechanic_skill

This skill helps WoW addon developers master Mechanic tooling by guiding CLI, MCP, dashboard, and in-game modules with practical workflows.

10

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill falkicon/mechanic --skill k-mechanic

SKILL.md4.0 KB

Overview

This skill provides deep context for Mechanic, the World of Warcraft addon development hub. It explains the CLI, MCP server, web dashboard, in-game modules, and MechanicLib integration so agents can operate the full Mechanic toolchain. Load it to enable accurate commands, diagnostics, and workflows for WoW addon development.

How this skill works

The skill describes Mechanic’s architecture and how desktop components (CLI, MCP server, dashboard) synchronize with the in-game !Mechanic addon via SavedVariables. It documents MCP tools that wrap AFD commands, CLI commands for linting/formatting/testing/releasing, dashboard capabilities, and in-game modules for console, error capture, tests, and performance inspection. MechanicLib registration patterns are provided so agents can identify and interact with registered addons.

When to use it

When an agent must run or translate CLI workflows like lint/format/test/release for an addon
When interacting with MCP tools or issuing mech call commands via the MCP server
When diagnosing runtime behavior using the web dashboard or in-game console/errors/tests
When instrumenting or registering an addon with MechanicLib for in-game integration
When needing to sync SavedVariables or trigger reloads across desktop and in-game components

Best practices

Prefer MCP tools over shell commands for authoritative operations (use env.status(), addon.lint(), etc.)
Use the CLI for local workflow automation but rely on MCP for interactions that require in-game context
Keep MechanicLib registration minimal and include a Print wrapper for unified output
Use the dashboard for real-time SavedVariables sync and to view aggregated logs before acting
Run tests through addon.test(addon) and verify results in both dashboard and in-game Tests module

Example use cases

Run a full release: mech release <addon> <version> "message" to build and tag, then confirm via dashboard
Debug a Lua error captured by the Errors module and view the stack trace in the dashboard before patching code
Run lint and format: mech lint <addon> and mech format <addon>, or use addon.lint/addon.format via MCP tools
Write a MechanicLib registration snippet for an addon to ensure console aggregation and unified Print output
Use the API Bench and Inspect modules in-game to find UI performance bottlenecks and frame issues

FAQ

Use MCP tools for any operation that depends on in-game state; they are the authoritative interface. Use CLI commands for offline build, lint, format, and test automation.

How do addons integrate with Mechanic for unified logging?

Register the addon with MechanicLib and provide a Print function that calls ML:Print("MyAddon", ...). This ensures console aggregation and consistent output across desktop and in-game views.