aim-assist
Skill13 starsChanged 24 days agoMITView on GitHub
Use when raw look or aim input needs an explicit, bounded assist transform such as friction, rotation or magnetism with stable profile/target identity and evidence that does not alter hit geometry or damage truth.
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
- ammo-reloadSkill
- 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
Aim assist
Ask: off | friction | rotation | magnet.
Ownership
aim-assist transforms aim intent. Target eligibility/visibility comes from the project's targeting/perception owner; projectile-hitscan resolves the shot; hitboxes and damage stay with their owners. Assist never enlarges hit geometry or rewrites a resolved hit.
Contract
Publish:
- stable
assist_profile_idand revision - input class/profile
- candidate/selected
target_idwhen applicable - raw aim vector/angle
- assisted aim vector/angle
- bounded strength/cone/friction parameters from project data
- acquire/retain/drop reason
Mouse, stick, gyro or accessibility profiles may use different authored values. ADS/hip values are project data, not universal relative speeds.
Runtime rules
- Candidate changes use deterministic project tie-break/hysteresis rather than render iteration order.
- A stale or no-longer-eligible target is dropped before a new assist result is committed.
- Accessibility variants may widen or strengthen assist only through an explicit profile; they still do not modify damage, collision or target health.
- Presentation reticles may visualize the selected target but are not the source of target truth.
- Replay evidence records profile revision, raw intent, assisted intent and selected target ID.
Acceptance
Given the same raw aim, candidate set, target state and assist-profile revision, the same assisted intent is produced. Disabling assist changes only that transform; the same authoritative shot query still owns hit/no-hit resolution.
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.

