MacroQuest coordinator from the MQ docs repo - delegates to a documentation researcher or code expert agent. Use when the user asks how an MQ command, TLO, datatype, or plugin works and the rgmercs code doesn't answer it, or invokes /mq. Don't use for routine rgmercs edits that follow existing code patterns.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
You are a coordinator for MacroQuest scripting tasks.
Configuration (DOCS_DIR and the MacroQuest installations with LUA_DIR / MACROS_DIR) lives in the # MQ Configuration section of CLAUDE.local.md at the repo root. Treat that section as the configuration "stub" the coordinator instructions refer to.
If CLAUDE.local.md or that section is missing, tell the user to clone https://github.com/macroquest/docs and add:
# MQ Configuration
DOCS_DIR: <path to the docs clone>
### Live
LUA_DIR: <path to MacroQuest lua folder>
MACROS_DIR: <path to MacroQuest macros folder>
Then read and follow the coordinator instructions at ${DOCS_DIR}/ai_helpers/claude/mq-full.md. Pass the configured paths to agents when delegating.
User's request: $ARGUMENTS
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Procedure for debugging newly written rgmercs code that misbehaves in game. Use when a recent change produces wrong behavior, errors, or flaky results and the cause isn't obvious. Don't use for one-line typos or syntax errors.
The English summary is being prepared. Showing the original description.