rpg-roadmap

Define RPG-style roadmaps mapping AI interactions to game mechanics and UI rules.

11|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/recca0120/code-quest --skill rpg-roadmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rpg-roadmap
Source: https://github.com/recca0120/code-quest/tree/main/.claude/skills/rpg-roadmap
Command: npx skills add https://github.com/recca0120/code-quest --skill rpg-roadmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you plan and communicate a long-term “RPG layer” vision for a Claude Code web client, so teams can align on mechanics, UI structure, and progression systems without confusing the roadmap with current implementation.

Core Features & Use Cases

  • RPG mechanics blueprint: Maps AI interactions to RPG elements like HP/MP/EXP/Gold, quests, battle triggers, and reward loops.
  • World & system design: Defines CodeLand’s regions and outlines 11 core systems (map, scene, stores, worktree, battle, partners, summons, events, async battle, multi-model integration, UI rules).
  • Design documentation navigation: Points you to specific UI design docs under docs/ui-design for deeper system-level proposals and narrative alignment.

Quick Start

Use the rpg-roadmap skill to generate a future-game-design plan that translates a proposed UI or session feature into RPG mechanics and progression rules.

Frequently Asked Questions about rpg-roadmap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map AI session interactions to RPG game mechanics like HP, MP, and EXP?

To map AI interactions to RPG game mechanics, you can define a roadmap translating web client sessions into progression rules, battle triggers, and resource systems like HP, MP, EXP, and Gold. This approach structures future UI features as game mechanics.

What is an RPG roadmap for product design and how does it work?

An RPG roadmap for product design is a non-implemented vision that translates proposed UI or session features into game mechanics and progression rules. It works by defining AI-to-RPG mappings and structuring world regions like CodeLand to align teams on future direction.

How do I plan quest progression and world building for a gamified web client?

You can plan quest progression and world building by defining a long-term game layer vision that outlines core systems like maps, scenes, stores, and battle mechanics. This ensures teams align on world structure without confusing the roadmap with current implementation.

Can I use this RPG vision to structure UI system mapping for future features?

Yes, you can use the RPG vision to structure UI system mapping by referencing specific UI design documents for system-level proposals. This ensures consistency with existing architecture while defining 11 core systems including map, scene, worktree, and multi-model integration rules.

Does this RPG roadmap approach require existing implementation docs to work?

The RPG roadmap approach requires references to related UI design documents for consistency with existing architecture. It explicitly functions as a non-implemented vision, meaning it guides future feature direction rather than depending on current code execution.