菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Meta knowledge for creating Claude skills. Provides templates, best practices, and patterns for building effective skills with routing tables and reference files. Load this when creating new skills or understanding the skill system. Triggers: create skill, new skill, skill template, skill architecture, SKILL.md.
Index of Mechanic documentation with summaries and links. Load this to understand what documentation exists and where to find detailed information on specific topics. Triggers: docs, documentation, reference, guide, help.
Context for FenCore - the pure logic library for WoW addons. Covers utility functions, math helpers, table operations, and environment detection. Load this when working with FenCore or needing utility functions. Triggers: fencore, utility, math, table, logic, pure functions.
Context for FenUI - the UI widget library for WoW addons. Covers frames, layouts, buttons, panels, and theming. Load this when building addon UI or working with FenUI widgets. Triggers: fenui, ui, widget, frame, layout, panel, button, tabs.
Context for Mechanic - the WoW addon development hub. Covers the CLI, MCP server, dashboard, in-game modules, and MechanicLib. Load this for deep understanding of Mechanic tooling. Triggers: mechanic, mech, cli, mcp, dashboard, tools, development hub.
Comprehensive quality analysis for WoW addons. Combines security, complexity, deprecation, and dead code analysis into a single audit workflow. Triggers: audit, quality, analysis, review, check, scan.
| name | k-ecosystem |
| description | 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. |
The Mechanic/Fen ecosystem is a unified platform for WoW addon development.
After ANY addon code change, you MUST verify the changes in-game:
/reload in WoW (or trigger via keybinding CTRL+SHIFT+R)addon.output MCP tool (agent_mode=true) to get errors, tests, and console logsCRITICAL: Do NOT call
addon.outputimmediately after changes. The timing between reload and SavedVariables sync is unpredictable. Always wait for user confirmation.
| 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 |
┌─────────────────────────────────────────────────────┐
│ 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)
└───────────────┘
| 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() |
Mechanic follows Agent-First Development (AFD) — github.com/Falkicon/afd
success, data, erroragent_mode=true for AI-optimized output