Silicon-Pantheon: Skill for Claude Code

Scenario Validation Skill

You are an experienced game designer and QA engineer reviewing tactical grid combat scenarios for Silicon Pantheon.

Target

• If $ARGUMENTS is empty or blank: check ALL scenarios in games/*/config.yaml (skip _test_plugin)
• If $ARGUMENTS is a scenario name (e.g., 03_thermopylae): check only that scenario

Checks to Perform

For each scenario, read the full config.yaml and the locale/zh.yaml (if it exists), then run every check below. Report each issue with severity (CRITICAL / HIGH / MEDIUM / LOW / INFO).

1. Format & Loading (CRITICAL if broken)

• Run load_scenario(name) via Python to verify the config parses and loads without errors:

  .venv/bin/python3 -c "from silicon_pantheon.server.engine.scenarios import load_scenario; s = load_scenario('SCENARIO_NAME'); print(f'{s.board.width}x{s.board.height} {len([u for u in s.units.values() if u.owner.value==\"blue\"])}b+{len([u for u in s.units.values() if u.owner.value==\"red\"])}r')"
  

• Every terrain type used in board entries must be defined in terrain_types
• move_cost on impassable terrain must be 99 (not 1 or a string)
• passable: false must accompany move_cost: 99

2. Unit Placement (CRITICAL if broken)

• No unit placed on an impassable tile (cross-reference positions against passable: false terrain)
• No unit out of bounds (x must be 0..width-1, y must be 0..height-1)
• No two units on the same tile
• Both teams have at least 3 units
• No unit has ATK 0 or HP 0

3. Glyph & ID Consistency

• No glyph collisions of any kind (HIGH severity). The map renders blue units UPPERCASE, red units lowercase, and terrain glyphs as-is. Three collision types to check:
  1. Terrain-terrain: No two terrain_types may share the same glyph — they are visually identical on the map.
  2. Unit-terrain (rendered form): A blue unit's glyph.upper() must not equal any terrain glyph. A red unit's glyph.lower() must not equal any terrain glyph. These produce identical characters on the map and the agent cannot distinguish unit from terrain.
  3. Cross-team unit-unit: No blue unit's glyph.upper() should equal any red unit's glyph.lower() (i.e., no two units across teams should share the same base letter). While case-distinguishable, this forces the agent to rely on case alone to tell units apart, which wastes reasoning tokens. Fix by changing the conflicting unit glyph to an unused letter. Prefer meaningful mnemonics (first letter of name/role).
• No color is shared between any unit_classes entry and any terrain_types entry (MEDIUM severity when violated) — otherwise a unit parked on a same-color tile becomes visually indistinguishable from the terrain. Units should use team colors (red/bright_red, cyan/bright_cyan, magenta for accents); terrain should use environmental colors (green, blue, yellow, white, bright_black, dim). Fix by changing the terrain color to a nearby unused shade.
• Win condition unit_id values must match actual units (format: u_{b|r}_{class}_{N})
• reach_tile positions must be within bounds and NOT on impassable tiles
• seize_enemy_fort requires forts to exist
• Fort entries should use owner not team