Skip to content

nddipiazza/robos / games/quest-warrior-dragon/.agents/skills/game-data-pipeline

game-data-pipeline

Verified

Workflow and instructions for editing JSON Schemas, validating game data, understanding live vs reference datasets, and generating typed GDScript model classes under src/generated/v1/.

πŸ“Š Game Data Pipeline & Schema Generation Skill

Use this skill when modifying game data schemas, JSON datasets (monsters, items, spells, shops, maps), or regenerating typed GDScript data classes.

πŸ—‚οΈ Three Layers of Project Data

  1. Scraped Source Pages (monsters/, spells/, arms/, items/, locations/, etc.): Reference material scraped from strategy guide archives. Treat as read-only background documentation.
  2. Consolidated Clean JSON (data/v1/*.json):
    • Live Runtime Datasets: Loaded dynamically at runtime by scripts (data/v1/monsters.json, data/v1/spells.json, data/v1/weapons.json, data/v1/armor.json, data/v1/shields.json, data/v1/items.json, data/v1/shops.json, data/v1/combat_formulas.json, data/v1/encounter_zones.json).
  3. Per-Map Registries (data/v1/chest_registry.json, data/v1/door_registry.json, data/v1/npcs.json, data/v1/stair_registry.json, data/v1/dialogue.json):
    • Reference coordinate & dialogue records. Note that some older maps hardcode tile interactions directly in GDScript; keep data JSON and scripts aligned.

πŸ“ Schema Architecture & GDScript Generation

  • JSON Schemas: schemas/v1/*.json
  • Game Data Files: data/v1/*.json
  • Generated GDScript Classes: src/generated/v1/*.gd
  • Generator Script: ./generate-schema-classes.sh

πŸ”„ Regenerating GDScript Data Models

Whenever you add, modify, or remove fields in schemas/v1/:

  1. Run the generation script:
    ./generate-schema-classes.sh
    
  2. Verify that updated GDScript files in src/generated/v1/ compile clean without syntax errors.

[!WARNING] Do NOT manually edit files under src/generated/v1/ as they will be overwritten by generate-schema-classes.sh.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path β€” even casually (like "the xlsx in my downloads") β€” and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexVerifiedInstall