🎯

k-ecosystem

🎯Skill

from falkicon/mechanic

VibeIndex|
What it does

Provides comprehensive context and tooling for World of Warcraft addon development across Mechanic, FenCore, FenUI, and MechanicLib components.

πŸ“¦

Part of

falkicon/mechanic(15 items)

k-ecosystem

Installation

pip installInstall Python package
pip install -e .
πŸ“– Extracted from docs: falkicon/mechanic
1Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

>

Overview

# 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](https://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

Related Knowledge

  • [k-mechanic](../k-mechanic/SKILL.md) - Deep dive into Mechanic tools
  • [k-fencore](../k-fencore/SKILL.md) - FenCore library details
  • [k-fenui](../k-fenui/SKILL.md) - FenUI widget library