메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | k-mechanic |
| description | 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. |
Mechanic is the unified platform for WoW addon development, providing CLI tools, MCP integration, a web dashboard, and in-game diagnostics.
┌─────────────────────────────────────────────────────┐
│ Mechanic Desktop │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ CLI (mech) │ │ MCP Server │ │ Dashboard │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
└─────────────────────────┬───────────────────────────┘
│ SavedVariables Sync
┌─────────────────────────▼───────────────────────────┐
│ !Mechanic Addon │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Console │ │ Errors │ │ Tests │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
└─────────────────────────────────────────────────────┘
MANDATORY: ALWAYS use MCP tools directly instead of the shell.
| Task | MCP Tool |
|---|---|
| Env Status | env.status() |
| Get Addon Output | addon.output(agent_mode=true) |
| Lint Addon | addon.lint(addon="MyAddon") |
| Format Addon | addon.format(addon="MyAddon") |
| Run Tests | addon.test(addon="MyAddon") |
| Sync Addon | addon.sync(addon="MyAddon") |
| Search APIs | api.search(query="*Spell*") |
mech)Command-line interface for all operations:
mech lint <addon> - Run Luacheckmech format <addon> - Run StyLuamech test <addon> - Run Busted testsmech release <addon> <version> "<message>" - Full release workflowExposes 53 AFD commands as MCP tools for AI agents. All functionality available via mech call <command> is also available as MCP tools.
Web UI at http://localhost:5173:
The !Mechanic addon provides:
Addons register with Mechanic via MechanicLib:
local ML = LibStub("MechanicLib")
ML:RegisterAddon("MyAddon", {
version = "1.0.0",
Print = function(...) ML:Print("MyAddon", ...) end,
})
| Request type | Load reference |
|---|---|
| CLI commands | references/cli-commands.md |
| AFD commands | references/afd-commands.md |
| In-game modules | references/ingame-modules.md |
| MechanicLib | references/mechaniclib.md |
| Dashboard | references/dashboard.md |
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 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.
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.
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.