verify-daemon-parity

Verify turn daemon and NPC AI parity against legacy PHP implementations.

Updated May 29, 2026
One-click install
npx skills add https://github.com/peppone-choi/opensamguk --skill verify-daemon-parity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-daemon-parity
Source: https://github.com/peppone-choi/opensamguk/tree/main/.claude/skills/verify-daemon-parity
Command: npx skills add https://github.com/peppone-choi/opensamguk --skill verify-daemon-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that the new turn daemon and NPC AI logic in the backend accurately replicate the behavior of the original legacy PHP implementation, preventing regressions and ensuring game balance.

Core Features & Use Cases

  • State Model Verification: Confirms the turn daemon's lifecycle (Idle, Running, Flushing) matches documentation.
  • Execution Order Check: Validates that turn processing follows the established sequence (General Commands -> Nation Commands -> Monthly Processing).
  • NPC AI Logic Parity: Verifies that NPC decision-making algorithms mirror the legacy GeneralAI.
  • Deterministic RNG Validation: Ensures random number generation for AI is consistent with the legacy system.
  • Daemon Control Testing: Checks that commands like run, pause, and resume function as expected.

Quick Start

Run the verify-daemon-parity skill to check if the turn daemon and NPC AI logic align with the legacy system's behavior.

Frequently Asked Questions about verify-daemon-parity

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

FAQPage Schema
How do I verify NPC AI logic parity after migrating from a legacy PHP backend?

To verify NPC AI logic parity after a legacy PHP migration, you need to check that the new decision-making algorithms accurately mirror the original GeneralAI. This ensures game balance and prevents regressions in NPC behavior.

What is the correct execution order for turn daemon processing?

The correct execution order for turn daemon processing follows a specific sequence: General Commands first, then Nation Commands, and finally Monthly Processing. Validating this sequence ensures the turn daemon behaves identically to the legacy system.

How do I validate deterministic RNG in a migrated game backend?

To validate deterministic RNG in a migrated game backend, you must ensure that random number generation for AI remains strictly consistent with the legacy system. This consistency is essential for maintaining predictable game logic outcomes.

What states should I check when testing turn daemon lifecycle behavior?

When testing turn daemon lifecycle behavior, check that its state model accurately transitions through Idle, Running, and Flushing phases. Confirming these states match documentation guarantees functional equivalence after engine updates.

How can I test daemon control commands like run, pause, and resume?

To test daemon control commands like run, pause, and resume, validate that each directive functions exactly as expected within the new backend. This testing ensures that daemon control interactions maintain parity with the legacy implementation.