IgorWarzocha/act-start
.agents/skills/act-start/SKILL.md
Use this at the start of an act, or whenever act-level planning resets after a compaction summary or major state change. Trigger it to re-evaluate deck shape, route goals, elite readiness, and act-specific priorities.
$ install --global
skillsauthnpx skillsauth add IgorWarzocha/AI-plays-Slay-The-Spire-2 act-startInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 12:52 AM27.6s4 files scanned
SKILL.md
- name:
- act-start
- description:
- Use this at the start of an act, or whenever act-level planning resets after a compaction summary or major state change. Trigger it to re-evaluate deck shape, route goals, elite readiness, and act-specific priorities.
Act Start
Use this when an act begins or when the run needs a fresh act-level plan.
Required Reading
Read these before acting:
/home/igorw/Work/STS2/.agents/skills/act-start/references/planning.md/home/igorw/Work/STS2/.agents/skills/act-start/references/rewards-and-deck-shape.md/home/igorw/Work/STS2/.agents/skills/boss-and-elite-fights/references/prep.md/home/igorw/Work/STS2/.agents/skills/merchant/references/heuristics.md- the current character skill for the run
- the current run log under
/home/igorw/Work/STS2/vault/runs - the current act skill's boss or elite notes if the incoming act contains a known hard-fight threat
Core Doctrine
- Start each act by identifying what the deck is good at, what still kills it, and what the act is most likely to test next.
- Route in chunks, not node by node.
- Do not send the run into elites just because a new act begins with full healing or fresh optimism.
- Decide whether the act plan is to exploit current strength, patch a fatal weakness, or buy time for scaling to come online.
- Boss preparation starts immediately. The act boss is not a floor-16 problem.
Act Start Checklist
- Reconstruct the real deck: draw quality, frontload, scaling, AoE, block, exhaust, potion support, and relic spikes.
- Identify the worst realistic fight in the act and whether the deck already has a plan for it.
- Mark which rewards or shops would genuinely change pathing permission.
- Decide how many elites the deck has earned right now, not in theory.
- Decide what must be fixed before the boss.
- Late in an act, do not over-preserve if the deck is already ahead of the act's tests and the route still has recovery or potion outs.
- A route with strong relics, upgraded control, spare potion capacity, and a fire before the boss often has earned one more elite even at imperfect HP.
- If the route is already forcing a hard fight, spend current HP, gold, and potion capacity to improve that fight instead of preserving fake safety into it.
Decision Standard
- Prefer routes that preserve multiple outs.
- Avoid plans that require several future hits in sequence just to become reasonable.
- When two paths are close, choose the one that fits the current deck's tested strengths.
- If the act presents unknowns, favor lines that gather information without forcing high-risk commitments too early.
Maintenance
This skill and its references are living documents. Improve them as new things are found. Do not append drift. Edit and rewrite to keep them sharp and short, and add references when needed.
Related Skills
IgorWarzocha/merchant
development
VerifiedTrustedCommunity
Use this when the current screen is a merchant or when planning a shop line from map pressure, gold, deck state, relics, and potions. Trigger it before buying, before leaving a shop, and when a forced elite or boss makes the shop an immediate survival checkpoint. Shops are hard decisions, so prefer reading them with `--hard`.
1SKILL.mdUpdated Apr 16, 2026
IgorWarzocha/learning-loop
testing
VerifiedTrustedCommunity
Use this when playing in this repo and you need to keep the run log, reference notes, mechanic notes, and strategy notes updated as durable learning. Trigger it during live runs, immediately after meaningful floors, immediately after elite or boss fights and boss rewards, when a new boss/elite/event/mechanic appears, when a fight needs STS1 parallels to understand what it is testing, and when ending a run so the post mortem can be reconciled against Compendium -> Run History before the final rewrite.
1SKILL.mdUpdated Apr 16, 2026
IgorWarzocha/ironclad
testing
VerifiedTrustedCommunity
Use this when the current run is Ironclad. Trigger it on new runs, after automated compaction summaries, and for Ironclad card, route, shop, reward, and combat decisions.
1SKILL.mdUpdated Apr 16, 2026
IgorWarzocha/events
development
VerifiedTrustedCommunity
Use this when the current screen is an event or when planning an event line from the real run state. Trigger it before choosing any event option, especially when the event offers generated cards, relics, gold-for-HP trades, removes, transforms, or branch-defining risk/value choices.
1SKILL.mdUpdated Apr 16, 2026