---

name: s-work description: > 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.

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:

1. Ask the user to /reload in WoW (or trigger via keybinding CTRL+SHIFT+R)
2. Wait for the user to confirm the reload is complete
3. Then use the addon.output MCP tool (agent_mode=true) to get errors, tests, and console logs

CRITICAL: Do NOT call addon.output immediately after changes. The timing between reload and SavedVariables sync is unpredictable. Always wait for user confirmation before pulling output.

Ecosystem Components

Essential MCP Tools

AFD Core Principles

Mechanic follows Agent-First Development (AFD) — github.com/Falkicon/afd

1. Tool-First: All functionality must exist as an MCP tool before being added to any UI.
2. Structured Results: All tools return predictable JSON schemas with success, data, and error.
3. Agent Mode: Use agent_mode=true for distilled, AI-optimized output.

Routing Logic