Quest Keeper Master Orchestration
Orchestrates the development of the Quest Keeper AI ecosystem by coordinating the Tauri frontend, RPG-MCP backend, and project documentation.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Mechanical Honesty philosophy for strict data validation and storage
- Integrated TDD loop for systematic issue tracking and resolution
- Full-stack orchestration across frontend (Tauri/React) and backend (RPG-MCP)
- Unified management of the Repository Trinity (Engine, Game, and Library)
- Mandatory Git Pulse workflow for consistent commit standards
Use cases
- Coordinating feature parity between the Tauri game client and the MCP backend
- Building and testing new RPG mechanics within the Quest Keeper engine
- Managing complex project state and documentation across multiple local directories
FAQ
What does the Quest Keeper Master Orchestration skill do?
This skill acts as the central coordinator for the Quest Keeper AI ecosystem. It synchronizes development across the 'Repository Trinity': the RPG-MCP backend (The Physics), the Tauri/React frontend (The Flight), and the project documentation (The Library).
What technical stacks does this skill support?
It is optimized for full-stack orchestration involving Tauri and React for the desktop frontend, Node.js for the RPG-MCP backend binaries, and markdown-based documentation for systemic project tracking.
What is the 'Mechanical Honesty' philosophy?
Mechanical Honesty is a strict data validation framework where the LLM describes an action, the MCP validates the logic, and the Database serves as the final, immutable source of truth, preventing state desync between the AI and the game engine.
How does this skill improve my AI coding workflow?
It enforces a rigorous development standard through the 'Git Pulse' workflow and a mandatory Test-Driven Development (TDD) loop. This ensures that every fix is validated by a failing test before implementation and documented in the Discovery Log.
When should I use this skill?
You should use this skill whenever you are working on any part of the Quest Keeper project. It triggers automatically on mentions of 'rpg-mcp', 'Quest Keeper', or when referencing the project's Agents/ folder to ensure cross-stack consistency.