cover-space
Skill13 starsChanged 24 days agoMITView on GitHub
Use when level geometry needs explicit cover affordances, stable anchors, stance/peek capabilities, occupancy and clearance evidence. It owns cover-space data, not input bindings, shooting, or the actor's cover state machine.
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
- 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
- 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
Cover space
Ask: geometry-only | stick-cover | none.
Ownership
cover-space owns authored/queryable cover affordances. cover-shooter consumes them for actor state transitions; projectile-hitscan owns shot resolution; input-design / kb-mouse-map own actions and bindings.
Contract
Each cover affordance publishes:
- stable
cover_anchor_id - source geometry/collision revision
- supported stance/peek/fire-side capabilities
- usable approach/exit regions
- clearance and occupancy policy
- optional neighbor/link IDs
High/low, blind-fire, lean, vault or other capabilities are project data. Do not infer them only from rendered mesh height.
Runtime rules
- A cover query returns anchor ID + revision + capabilities.
- Streaming/destruction/geometry changes invalidate or revise affected anchors.
- Occupancy is explicit where required; two actors cannot silently claim an exclusive slot.
- Input keys and mouse buttons never live in this skill.
- Cover affordance does not grant invulnerability, alter health, or resolve shots.
Acceptance
For one geometry revision and actor capability profile, the same query resolves the same valid cover anchors. A stale or blocked anchor is rejected before attachment, and cover presentation cannot make non-cover geometry authoritative.
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.

