fps-shooter
Designs first-person shooter combat in any engine: hitscan vs projectiles, time-to-kill, damage falloff, recoil patterns, ADS sensitivity and lag-compensated hits. Use for a Doom- or Counter-Strike-like, or guns that feel weak or shots that do not register.
Install / Use
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill fps-shooterInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of fps-shooter
fps-shooter scores 94/100 on our quality scale, 92nd of 642 Marketing skills we index (top 15%).
Its SKILL.md is 6.0 KB long, well organised into 15 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 8,904 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 4 days ago, so fps-shooter is actively maintained.
- Our last check on 2026-11-16 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
fps-shooter compared with similar skills
All 4 of these similar skills score higher than fps-shooter; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| fps-shooter (this skill)by gamedev-skills | 94 | 8.9k | 4d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install fps-shooter?
- Run
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill fps-shooter. The install tabs above show the steps for each supported agent. - Which AI agents does fps-shooter work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is fps-shooter safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is fps-shooter still maintained?
- The repository was last updated 4 days ago, so fps-shooter is actively maintained.
Skill content
View source on GitHubname: fps-shooter description: > Build a first-person shooter: move+mouse-look controller, hitscan or projectile shooting, weapons, health, and enemy AI. Use for an FPS, or tuning aim feel, time-to-kill, recoil, or spread.
FPS Shooter
A playbook for first-person shooters — the look/move controller, the shooting model, weapon feel, and combat. This is a compositional skill: it wires a 3D controller, input, and AI into a shooter. It does not re-teach 3D nodes or raycasts; it defines the shooting model and the feel knobs (TTK, recoil, spread) that decide whether the guns feel good.
When to use
- Use when building a first-person game whose core verb is aim and shoot — arena shooter, tactical FPS, PvE shooter, boomer-shooter.
- Use when deciding hitscan vs. projectile, tuning time-to-kill, recoil, spread, or aim feel.
When not to use: third-person/2D shooting → reuse the shooting model here but build the
camera/controller from the relevant genre. Wave survival with towers → tower-defense.
For the camera/character body itself, use godot-3d-essentials / unreal-cpp-gameplay.
Core loop
Scan → acquire a target → aim and fire → confirm the kill (feedback) → reposition / reload / advance. The whole experience rests on the aim-and-fire micro-loop feeling crisp: responsive look, clear hit feedback, and a death that reads instantly.
Must-have systems
- First-person controller — move (WASD/stick) + mouse/stick look, gravity, jump/crouch.
- Camera — eye-height view, configurable FOV and sensitivity, recoil kick.
- Shooting model — hitscan raycast and/or projectile spawn; one impact path for feedback.
- Weapons + ammo — damage, fire rate, magazine, reload, switching.
- Health + damage — HP, hit/headshot multipliers, death; player and enemy share the model.
- Enemy AI — perceive → alert → attack → search; cover and reaction delays (
game-ai). - Feedback — hitmarkers, impact decals/particles, hit sounds, screen shake, kill confirms.
- Objectives — what you do besides shoot: clear, capture, survive, escort.
Design knobs
| Knob | Effect | Sane default | |------|--------|--------------| | Time-to-kill (TTK) | lethality, forgiveness | Tune dmg × fire-rate × HP together (refs). | | Hitscan vs projectile | aim skill type | Hitscan = flick; projectile = lead/dodge. | | Damage falloff | range limiting | Full to ~20 m, floor by ~60 m. | | Headshot multiplier | skill reward | ~1.5–2.0×. | | Recoil pattern | learnable kick | Fixed pattern > pure random. | | Spread (bloom) | suppress laser-accuracy | First shot accurate; grows while firing. | | Fire rate / magazine / reload | rhythm, downtime | Reload = vulnerability window. | | Mouse sensitivity / FOV | comfort, readability | Always expose both as options. | | Aim assist (pad) | controller parity | Magnetism/slowdown near targets. |
Patterns
1. Hitscan shot (instant ray, the workhorse)
# Pseudocode. Cast from the camera; first hit takes damage scaled by range + headshot.
direction = apply_spread(camera.forward, current_spread)
hit = raycast(camera.world_position, direction, max_dist=RANGE, mask=SHOOTABLE)
if hit:
dmg = base_damage * falloff(hit.distance)
if hit.is_head: dmg *= HEADSHOT_MULT
hit.actor.take_damage(dmg)
spawn_impact_fx(hit.point, hit.normal) # decal + sound + hitmarker
2. Projectile shot (dodgeable, leads the target)
# Pseudocode. Spawn a moving body; it deals damage on its own collision.
p = spawn(projectile_scene, at=muzzle.world_position)
p.velocity = camera.forward * PROJECTILE_SPEED
p.on_hit = lambda other, point: (other.take_damage(base_damage), explode_fx(point))
p.lifetime = RANGE / PROJECTILE_SPEED # despawn so shots don't live forever
3. Time-to-kill (balance the trio together)
# Pseudocode. TTK falls out of HP, per-shot damage, and fire rate — tune as one system.
shots_to_kill = ceil(target_hp / damage_per_shot)
ttk_seconds = (shots_to_kill - 1) / fire_rate_per_second # first shot at t=0
Pitfalls / failure modes
- Look tied to frame rate or unscaled by
dt→ sensitivity changes with FPS. Look should be driven by raw mouse delta; movement integration usesdt(seephysics-tuning). - Pure random recoil/spread → feels uncontrollable and unfair. Use a learnable recoil pattern; keep the first shot accurate.
- Hitscan with no falloff → pistols snipe across the map. Add range-based damage falloff.
- No hit feedback → players can't tell if shots land. Always show hitmarkers, impact FX, and a distinct kill confirm.
- Mismatched TTK → too low feels twitchy/unfair; too high feels spongy. Tune damage, fire rate, and HP as one system (Pattern 3).
- Trusting the client in multiplayer → cheating and "I shot first" disputes. Keep authority server-side; use lag compensation (refs) and defer netcode to the engine multiplayer skill.
- No FOV / sensitivity options → motion sickness and accessibility failures. Always expose them.
Composition (build it from these skills)
- Controller + camera:
godot-3d-essentials(Godot) orunreal-cpp-gameplay/unreal-blueprints; Unity usesunity-physics+ a character controller. - Input:
input-systems(orunreal-enhanced-input) for look/move, rebinding, and gamepad aim assist. - Shooting physics:
godot-physics/unity-physicsfor raycasts and projectile collision. - Enemies:
game-aiwithunity-navmesh/unreal-behavior-trees/ Godot navigation. - Camera & feel:
camera-systemsfor FOV/recoil kick and look smoothing;game-feelfor hit-stop, screen shake, and impact juice. - Polish:
audio-designfor weapon/impact sound;shader-programmingfor muzzle/impact VFX. - Process:
prototype-fastto validate aim feel before building content.
References
- For hitscan vs. projectile trade-offs, damage falloff, recoil/spread, TTK math, hit
registration/lag compensation, and enemy AI states, read
references/shooting-and-feel.md.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
