ammo-reload
Skill13 starsChanged 24 days agoMITView on GitHub
Use when weapons need magazine/chamber/reserve ammunition, shot consumption and reload transfer with atomic resource updates, interruption/cancel policy and semantic input actions.
In this repository195 other files it gives its agents.
- llms.txtllms.txt
- hd-sprite-sequenceSkill
- pixel-animationSkill
- skin-weightsSkill
- spine-skeletalSkill
- sprite-atlasSkill
- sprite-catalogSkill
- sprite-skinSkill
- art-bibleSkill
- asset-pack-intakeSkill
- character-rigSkill
- materialsSkill
- model-pipelineSkill
- open-asset-fixtureSkill
- vfx-generateSkill
- a11y-controlsSkill
- ability-gateSkill
- action-feelSkill
- ad-breakSkill
- adventure-toolSkill
- aggro-tableSkill
- aim-assistSkill
- analytics-funnelSkill
- animation-blendSkill
- animation-graphSkill
- asset-runtimeSkill
- attack-tellSkill
- audio-busesSkill
- audio-feelSkill
- avatar-createSkill
- balance-designSkill
- boss-designSkill
- browser-inputSkill
- camera-anti-clipSkill
- camera-modestySkill
- camera-shotsSkill
- cert-handoffSkill
- chemistry-verbsSkill
- climb-vaultSkill
- cloud-saveSkill
- collision-layersSkill
- combo-designSkill
- cover-shooterSkill
- cover-spaceSkill
- crafting-loopSkill
- currency-dualSkill
- cutscene-handoffSkill
- day-nightSkill
- death-carrySkill
- debug-slateSkill
- deck-buildSkill
- dialogue-beatSkill
- dialogue-flagsSkill
- difficulty-designSkill
- dodge-iframeSkill
- durability-economySkill
- encounter-designSkill
- enemy-aiSkill
- enemy-fireSkill
- enemy-kit-balanceSkill
- The first 60 shown.
The file
Files
Ammo and reload
Compatible modes
infinite | mag-and-reserve | one-shot-chamber
Resource contract
Publish weapon/ammo resource IDs, magazine/chamber capacity, reserve ownership, fire consume boundary, reload transfer policy, cancel/interruption state and a stable reload transaction ID for each committed transfer.
Rules
- Fire/reload are semantic actions routed through
input-design; do not require reload and interact to use universally different physical keys. - A shot consumes ammo once at the authoritative fire/shot-commit event. Muzzle flash/audio/animation never spends ammunition.
- Reload magazine/reserve movement is atomic at the published commit boundary (or explicit staged transfers when the design uses them). Cancellation cannot invent or destroy rounds.
- Repeated/resimulated reload callbacks use the same reload transaction identity and remain idempotent.
- Firing/ADS/hip/cancel behavior during reload is project action-graph data; shared/split ammo pools are declared rather than assumed.
- Inventory/shop/economy replenishment uses their own transaction owners and stable ammo resource ID.
Accept
Reconcile magazine/chamber/reserve across fire, exact-empty, partial reload, cancel before/after commit, duplicate callback, weapon swap and insufficient reserve. Total ammo changes only through named consumption/grant transactions.
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
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.

