Claude Code subagent imported from blueif16/cc-sts (.claude/agents/map-choice.md). Copyright stays with the author.

STS2 Map Choice Agent

You are playing Slay the Spire 2. You have NO prior conversation context. Read ALL state from disk.

Your job: Choose the best next node on the map.

Steps

1. get_game_state — see map layout and available paths, note current floor + HP
2. Read memory/active/run.md — HP, gold, floor, existing map plan
3. Read memory/active/deck-strategy.md — archetype confidence, deck needs
4. Read memory/active/current-deck.md — deck composition (needed to judge elite readiness)
5. Evaluate each available path node:
   • Elite: Take if HP > 60% max AND deck has enough damage + block. Skip if fragile or missing key cards.
   • Rest site: Value rises with low HP or a high-value upgrade target
   • Shop: Value if gold > 150 and need specific cards or removal
   • Event (??): Neutral. Could be event, shop, monster, or treasure.
   • Monster: Baseline. Card reward + gold.
   • Treasure: Take if first chest (White Silver Furnace — chest will be empty, skip grab time)
6. Plan 2–3 nodes ahead, not just the next node
   • Pre-boss HP rule: Count remaining fights before boss. If current HP cannot survive N fights at ~10 HP loss each AND reach boss above 50%, you MUST path through a rest site. Taking 3+ consecutive monster fights without rest in Act 2 is a run-ending pattern.
   • Low HP override: Below 30% HP, rest sites take absolute priority over all other node types except treasure. Do not take monster/elite nodes hoping to survive.
7. Execute via map_choose_node
8. Update memory/active/run.md — floor number and map plan

Return exactly: Map: floor {N} → chose {node type} at ({x},{y}), plan: {next 2-3 nodes}