game-feel
Add "juice" and game feel that makes actions satisfying — screen shake, hit-stop/freeze frames, tweened/eased motion, squash & stretch, knockback, and layered audio-visual feedback — as engine-neutral techniques that pair with the detected engine's tween, particle, and camera APIs. Use when the user mentions game feel, juice, "make it feel good/punchy", screen shake, hit stop, screen freeze, easing, squash and stretch, impact frames, or feedback/polish on hits, jumps, pickups, and deaths.
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill game-feel --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Game feel (juice) The difference between a mechanic that *works* and one that feels *good* is feedback: the layered, slightly-exaggerated response an action provokes. This skill covers the engine- neutral techniques — screen shake, hit-stop, easing, squash & stretch, knockback, and stacked feedback — and tells you how to apply them without burying the underlying simulation. It **adds polish on top of** an existing mechanic; it does not implement the mechanic. ## When to use - Use when an action (hit, jump, dash, pickup, death, button press) is mechanically correct but feels weak, weightless, or unsatisfying, and you want it to feel responsive and punchy. - Use to add screen shake, hit-stop/freeze frames, eased motion, squash & stretch, knockback, flashes, or to layer multiple feedback channels onto one event. - Use to decide *how much* juice is enough and where it crosses into noise. **When *not* to use:** for the raw controller math (jump height, coyote time) use the `platformer` genre and the engine movement skill. For camera *follow/deadzone/orbit* framing use `camera-systems` (this skill only triggers the shake). For mixing, ducking, and adaptive music use `audio-design`. For
- When to use
- Core principle: feedback is layered and exaggerated
- Core workflow
- Patterns
- 1. Screen shake by decaying "trauma" (smooth, not a random jitter)
- 2. Hit-stop / freeze frame (sell impact by briefly stopping time)
- 3. Squash & stretch + overshoot via an eased tween (the "pop")
- 4. A feedback bundle scaled by importance (keep juice proportional)
- Pitfalls
- References
- Related skills
What does the game-feel skill do?
Add "juice" and game feel that makes actions satisfying — screen shake, hit-stop/freeze frames, tweened/eased motion, squash & stretch, knockback, and layered audio-visual feedback — as engine-neutral techniques that pair with the detected engine's tween, particle, and camera APIs. Use when the user mentions game feel, juice, "make it feel good/punchy", screen shake, hit stop, screen freeze, easing, squash and stretch, impact frames, or feedback/polish on hits, jumps, pickups, and deaths.
How do I install it?
Run `npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill game-feel --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From gamedev-skills/awesome-gamedev-agent-skills, a repository with 406 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.