What problem does it solve? It gives developers a map of the Payload engine-builder codebase so they can safely add or change parts, blueprints, jams, difficulties, and quotas without breaking determinism, fairness, or the parity tests that guard the scoring maths. ## Core Features & Use Cases - Engine architecture map: Explains the split between the pure rules engine in src/game (types, content, simulate, run, rng, daily, preview) and the React views in src/ui that replay the event log. - Content declaration guide: Step-by-step rules for adding parts to PARTS and applyPart, blueprints to BLUEPRINTS, jams to DIFFICULTIES, and full difficulty definitions, including pool placement and compendium sync. - Invariant enforcement: Documents the five invariants that keep runs deterministic and fair, such as seeded Fisher-Yates shuffling, guaranteed scaler drafts, and visible event logging for every score change. - Use Case: When a drop scores wrong or marbles animate out of sync with what fired, use this Skill to trace simulateDrop, the DropEvent log, and the playback regrouping to find whether the bug lives in the rules or the renderer. ## Quick Start Ask the AI to use the payload-engine skill to add a new part type to the game and walk through the required changes in PARTS, applyPart, and the difficulty pools.
