s-work
General-purpose skill for Mechanic/Fen ecosystem work. Covers ecosystem context, development tools, component overview, and AFD principles. Use for everyday addon work, exploration, or when unsure which specialized skill to use. Triggers: work, build, develop, create, mechanic, fen, fencore, fenui, ecosystem, addon.
When & Why to Use This Skill
This Claude skill is a comprehensive development assistant designed for the Mechanic and Fen World of Warcraft addon ecosystem. It streamlines the entire development lifecycle—from architectural planning to real-time debugging—by integrating Agent-First Development (AFD) principles with specialized MCP tools. It provides expert guidance on FenCore logic, FenUI components, and automated testing, ensuring developers can build, lint, and optimize addons efficiently within a structured framework.
Use Cases
- Case 1: Streamlining WoW addon development by utilizing the Mechanic/Fen ecosystem's core libraries (FenCore and FenUI) for rapid component integration.
- Case 2: Implementing a robust debugging workflow using the 'Reload Loop' and 'addon.output' tool to capture and resolve in-game Lua errors and console logs.
- Case 3: Adopting Agent-First Development (AFD) principles to create tool-centric addon architectures that are optimized for AI-assisted coding and structured data handling.
- Case 4: Navigating complex ecosystem documentation and API references to find specific UI widgets, layout patterns, or bridge library functions like RegisterAddon.
| name | s-work |
|---|---|
| description | > |
| Triggers | work, build, develop, create, mechanic, fen, fencore, fenui, ecosystem, addon. |
Fen Ecosystem
Expert guidance for working in the Mechanic/Fen WoW addon development ecosystem.
The Reload Loop (MANDATORY)
After ANY addon code change, you MUST verify the changes in-game:
- Ask the user to
/reloadin WoW (or trigger via keybinding CTRL+SHIFT+R) - Wait for the user to confirm the reload is complete
- Then use the
addon.outputMCP tool (agent_mode=true) to get errors, tests, and console logs
CRITICAL: Do NOT call
addon.outputimmediately after changes. The timing between reload and SavedVariables sync is unpredictable. Always wait for user confirmation before pulling output.
Ecosystem Components
| Component | Purpose | Key Tools |
|---|---|---|
| Mechanic | Development hub | env.status, addon.output, reload.trigger |
| FenCore | Pure logic library | fencore.catalog, fencore.search, fencore.info |
| FenUI | UI widget library | Layout, Panel, Tabs, Grid, Buttons |
| MechanicLib | Bridge library | RegisterAddon, Print, RegisterTest |
Essential MCP Tools
| Task | MCP Tool |
|---|---|
| Get Addon Output | addon.output (agent_mode=true) |
| Lint Code | addon.lint |
| Run Tests | addon.test |
| Search APIs | api.search |
| Search FenCore | fencore.search |
| Env Status | env.status |
AFD Core Principles
Mechanic follows Agent-First Development (AFD) — github.com/Falkicon/afd
- Tool-First: All functionality must exist as an MCP tool before being added to any UI.
- Structured Results: All tools return predictable JSON schemas with
success,data, anderror. - Agent Mode: Use
agent_mode=truefor distilled, AI-optimized output.
Routing Logic
| Request type | Load reference |
|---|---|
| Component details, architecture | references/components.md |
| Daily workflows, patterns | references/workflow.md |
| Quick API reference | references/quick-api.md |
| MCP tool reference | ../using-mechanic/references/afd-commands.md |