agentleFS
jammyfujammyfu/open-game-skills/skills/disciplines/enemy-kit-balance/SKILL.md

enemy-kit-balance

Skill13 starsChanged 24 days agoMITView on GitHub

Use when an enemy moveset has unreadable pressure, weak punish opportunities, repetitive loops, excessive overlap with nearby enemies, or balance changes are leaking into unrelated player timing systems.

The file

Files
SKILL.md

Enemy Kit Balance

This skill owns individual enemy move budgets and kit trade-offs. attack-tell owns warning channels, group-tactics owns multi-enemy concurrency, and difficulty-design owns difficulty scaling policy.

Modes

ModeKit emphasis
poke-guardfrequent low-commitment pressure with authored gaps
burst-duelisthigher commitment burst and punish windows
swarm-chaffsimple low-cost moves intended for groups
artilleryrange pressure with authored close-range weaknesses

Move budget

For every move publish logical startup/tell handoff, active interval, recovery, repeat/cooldown resource, damage/reaction, range and any armor/guard interaction. Values are project data; clip length does not substitute for the logical table.

A kit may have one or several high-impact moves depending on encounter role. What matters is that their combined frequency, overlap, coverage and counterplay fit the encounter budget. Do not impose a universal “one scary move” law.

Punishability is defined by the selected game's legal response windows: movement escape, block/parry, interrupt, reposition, resource response, single hit, combo, and so on. Do not require every whiffed heavy to permit a universal two-hit confirm.

Encounter interaction

When multiple enemies can pressure simultaneously, combine the kit table with group-tactics concurrency limits. A move that is fair in a duel may be invalid when several copies overlap. Tune the enemy or encounter budget before secretly shrinking player dodge, input buffer, hitstop or recovery contracts.

Acceptance

Record move-table data and the intended counter for each high-impact action. Test the kit alone and in representative encounter compositions from group-tactics. Measure warning-to-activation, punish windows, repeat cadence and overlapping unavoidable threat. A patch should be explainable as kit/encounter data changes rather than hidden edits to unrelated player timing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.