s-working_skill

This skill guides you through Mechanic/Fen WoW addon development, providing tooling, context, and best practices for everyday addon work.

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 s-working

SKILL.md2.5 KB

Overview

This skill is a general-purpose assistant for development inside the Mechanic/Fen World of Warcraft addon ecosystem. It centralizes guidance for everyday addon work: debugging, testing, performance checks, and navigation of core libraries. Use it when you need a reliable, agent-first workflow or when you are unsure which specialized tool to use.

How this skill works

I guide you through the Mechanic workflow and recommend MCP tools for tasks like getting addon output, linting, and running tests. For code changes I enforce the Reload Loop: ask you to /reload in-game, wait for your confirmation, then run addon.output with agent_mode=true to collect errors and logs. I also map requests to appropriate FenCore, FenUI, and Mechanic tools and return structured, actionable steps.

When to use it

After making code changes to verify behavior and capture runtime errors
When you need to gather logs, run tests, or lint Lua addon code
Exploring FenCore APIs or locating UI components in FenUI
Performing routine performance checks and debugging in-game
When you are unsure which specialized skill or tool to invoke

Best practices

Always perform the Reload Loop: ask user to /reload, wait for confirmation, then call addon.output (agent_mode=true)
Prefer MCP tools first: make functionality available as a tool before adding UI
Expect and parse structured JSON responses with success, data, and error fields
Run addon.lint and addon.test regularly during development
Use fencore.search and api.search to find stable APIs before implementing logic

Example use cases

You changed a widget in FenUI: trigger the Reload Loop, then collect addon.output to see errors and runtime traces
Investigating a logic bug: run fencore.search for functions and use addon.test to run unit checks
Performance regression after a patch: use env.status and addon.output to capture CPU/memory peaks
Building a new addon feature: register core functionality as an MCP tool, then expose a FenUI panel for QA
Quick API lookup: use api.search to find Blizzard API signatures and fencore.info for library details

FAQ

SavedVariables and internal state can lag immediately after a reload. Waiting for your confirmation ensures logs and saved data are synchronized so addon.output returns accurate results.

What does agent_mode=true do?

agent_mode=true requests distilled, AI-optimized output from MCP tools using the AFD conventions, producing predictable JSON suited for automated processing.