k-ecosystem

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.

⭐6stars🔀0forks📁View on GitHub🕐Updated Jan 7, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill provides a comprehensive development context for the Mechanic/Fen World of Warcraft (WoW) addon ecosystem. It streamlines the creation, debugging, and testing of addons by integrating FenCore logic, FenUI components, and Agent-First Development (AFD) principles with specialized MCP tools for a seamless, agent-optimized workflow.

Use Cases

  • Case 1: Initializing and structuring new WoW addons using the Mechanic/Fen framework and AFD principles to ensure maintainable code.
  • Case 2: Executing the mandatory reload-and-verify loop to debug in-game addon behavior using the addon.output MCP tool for real-time error tracking.
  • Case 3: Designing complex in-game user interfaces using the FenUI widget library, including layouts, panels, grids, and interactive buttons.
  • Case 4: Implementing pure logic and searching for utility functions within the FenCore catalog to minimize UI dependencies.
  • Case 5: Utilizing specialized MCP tools for automated code linting and unit testing to ensure addon stability and performance.
namek-ecosystem
description>
Triggersecosystem, fen, fencore, fenui, mechanic, addon, context.

Fen Ecosystem

The Mechanic/Fen ecosystem is a unified platform for WoW addon development.

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.

Ecosystem Components

Component Purpose Key Tools
Mechanic Development hub (CLI, MCP, Dashboard) env.status, addon.output, addon.lint, addon.test
FenCore Pure logic library (no UI dependencies) fencore.catalog, fencore.search, fencore.info
FenUI UI widget library (frames, layouts) Layout, Panel, Tabs, Grid, Buttons
MechanicLib Bridge library (addon ↔ Mechanic) RegisterAddon, Print, RegisterTest

Component Relationships

┌─────────────────────────────────────────────────────┐
│                    Your Addon                        │
├─────────────────────────────────────────────────────┤
│  Core Layer     │  Bridge Layer   │  View Layer     │
│  (Pure Logic)   │  (Events/Data)  │  (UI Frames)    │
│                 │                 │                 │
│  Uses: FenCore  │  Uses: Ace3     │  Uses: FenUI    │
└─────────────────────────────────────────────────────┘
         │                 │                 │
         └────────────┬────┴─────────────────┘
                      │
              ┌───────▼───────┐
              │  MechanicLib  │  (Registers addon with Mechanic)
              └───────┬───────┘
                      │
              ┌───────▼───────┐
              │   Mechanic    │  (Development hub)
              └───────────────┘

Essential MCP Tools

Task MCP Tool
Get Addon Output addon.output(agent_mode=true)
Lint Code addon.lint(addon="MyAddon")
Run Tests addon.test(addon="MyAddon")
Search APIs api.search(query="*Spell*")
Search FenCore fencore.search(query="clamp")
Env Status env.status()

AFD Core Principles

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

  1. Tool-First: All functionality exists as an MCP tool before any UI
  2. Structured Results: Tools return predictable JSON with success, data, error
  3. Agent Mode: Use agent_mode=true for AI-optimized output