core-loop-specifier

Specify incremental game core loops with breakpoints and write CORE_LOOP.md documentation.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/hoonzinope/skills --skill core-loop-specifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core-loop-specifier
Source: https://github.com/hoonzinope/skills/tree/main/game-skill/core-loop-specifier
Command: npx skills add https://github.com/hoonzinope/skills --skill core-loop-specifier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Specify the core gameplay loop as action -> reward -> next choice with breakpoints and write the result to .documents/game/CORE_LOOP.md for consistent documentation across game designs.

Core Features & Use Cases

  • Provides a concise, repeatable loop definition (Action -> Reward -> Next Choice) with explicit breakpoints.
  • Integrates with the scaffolding workflow (scripts/scaffold_doc.py) and templates (assets/TEMPLATE.md) to produce a ready-to-use document at .documents/game/CORE_LOOP.md.
  • Supports both initial creation and dated append updates to capture design iterations and decisions.

Quick Start

Create a CORE_LOOP.md skeleton using the template and save it under .documents/game/CORE_LOOP.md.

Frequently Asked Questions about core-loop-specifier

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

FAQPage Schema
How do I define a core gameplay loop for an idle game?

Idle game core loop definition structures the Action -> Reward -> Next Choice sequence with explicit breakpoints, producing a scaffolded CORE_LOOP.md document to capture the design.

What is an action reward next choice loop with breakpoints in incremental games?

An action reward next choice loop with breakpoints is a core incremental game design pattern structuring player interactions into a repeatable cycle with defined milestones for evaluating progression.

How do I generate game design documentation for core loops using markdown templates?

Generating game design documentation applies markdown templates to scaffold a CORE_LOOP.md file, saving the structured loop definition and breakpoints under the game's documents directory.

Can I append dated updates to existing core loop documentation?

Yes, appending dated updates to existing core loop documentation captures design iterations and decisions over time within the generated CORE_LOOP.md file.

Does the core loop specification workflow require any external dependencies?

No, the core loop specification workflow requires no external dependencies, running internal scaffold scripts and markdown templates to produce gameplay loop documentation.