This skill adds a feedback layer to a mechanic that already works. Several small, brief, exaggerated responses fire together on one event, and a three-tier table (small, medium, large) sets trauma, hit-stop length and particle counts so the whole game stays proportional.
It never changes the simulation: shake moves the camera and hit-stop scales time, and neither moves bodies or stalls gameplay logic. Code is given for Godot and Unity.
What You Get
- A tier table with trauma, hit-stop duration and particle ranges for small, medium and large events
- A Godot trauma-shake camera script and the Cinemachine equivalent for Unity
- Hit-stop code in GDScript and C# that survives overlapping hits
- A squash, stretch and overshoot tween pattern that returns to its rest value
Common Use Cases
- Making a sword hit or landing feel satisfying
- Tuning screen shake so light hits barely move the camera and heavy hits punch
- Fixing a hit-stop that never ends or restores time during a second freeze
- Adding reduce-shake and reduce-flashing options for accessibility
What Makes It Unique
It treats juice as a budget: most channels per event are limited, hit-stop and shake are kept for impacts, and freezes stay under about 0.15 s so input does not feel laggy. Its gotchas cover real-time versus scaled-time decay, timers that never fire at time scale 0, time scale not slowing audio, and the three-flashes-per-second limit from WCAG 2.3.1.
Under The Hood
The skill is instructions and one reference file of feedback recipes, with no scripts. It tells the agent to find the project’s event hooks, add signals or events when none exist, and write a headless check that fires an event twice 30 ms apart and asserts time scale and trauma return to rest, which runs the project’s own code. It then asks the user to play the result. It does not fetch web pages or call APIs. It edits gameplay and camera code in the project.