juice-scan

Audit a game's code for juice and game feel; write a prioritized report. Detects the engine (Unity, Godot, Roblox, web, Pygame, LOVE, Unreal), maps the feel moments (input, jump, attack, hit, death, pickup, score, menus, transitions, camera, audio), checks each one's feedback (visual, motion, camera, audio, UI, haptic, hit-stop, coyote time, input buffering), flags gaps and over-juicing, and ranks fixes by impact/effort with file, function, principle, parameters and a code sketch. Use it first, before reading any game code yourself and even for a tiny project (it carries the principles, parameters and engine traps the answer needs), whenever the user asks why some part of a game feels flat, floaty, weak, stiff or unsatisfying, or asks to make a game feel better: 'make my game feel better', 'add juice', 'why does combat feel flat', 'my jump feels floaty', 'polish pass', or 'refresh juice-scan' / 'is juice-scan stale'. Theory without code is juice-principles; implementing a picked suggestion is juice-apply.