ReignsAgent AGENTS.md

ReignsAgent System Specification & Agent Guidelines

0. Project Goal

ReignsAgent is a production-oriented, Reigns-like agentic game product for generating, testing, editing, previewing, and shipping card-based narrative experiences.

This is not only a developer middleware project. The final system must be usable by real content creators through a functional frontend where they can import content, configure or connect AI generation, edit generated cards, structure narrative progression, preview gameplay, inspect narrative and balance diagnostics, and prepare deployable game builds. Architecture must remain separated, but the product goal includes a complete user-facing creation and publishing workflow.

The long-term goal is a self-improving loop:

• Core runs the game rules headlessly and stays small, deterministic, and UI-free.
• Reviewer stress-tests card sets through Monte Carlo simulation and emits objective JSON diagnostics for coverage, pacing, endings, dead paths, and balance.
• Pipeline imports local content, calls generation connectors, and uses Reviewer diagnostics to propose or generate corrections.
• Interface provides the production frontend for content development, AI configuration, editing, preview, diagnostics, and deployment preparation while preserving module boundaries.

The project should optimize for pure left/right card interaction, inspectable data, automated narrative/balance feedback, and modular evolution. The player-facing game must remain the cleanest possible Reigns-style swipe experience, but the authored content may still contain data-driven chapters, themes, story arcs, endings, and stateful narrative evolution.

Narrative progression and Anti-RPG boundary: the system may support data-driven story progression through author-defined tags, variables, metadata, chapters, themes, arcs, endings, and configurable state/gauge presentation. These are narrative organization and authoring concepts, not built-in RPG management systems. The system must not ship predefined equipment, pets, inventory, shop, rarity, crafting, character-build, skill-tree, loot, or resource-management gameplay. Any such concepts may exist only as user-authored data labels interpreted by custom content, not as built-in gameplay loops, UI systems, or product features. The visible gameplay remains pure card text plus binary left/right choices.