Game Feel Pass

I'll load the game-feel-pass skill to see what it does.

I'll run the scanner on the "before" demo and read the pattern reference and checklist template.

A game feel pass on the Coin Hopper demo

1. Try it yourself. Open these two files in a browser, side by side. They're the same small game, and only the second one has juice and a comfort-settings panel.

• .claude/skills/game-feel-pass/assets/demo/before.html
• .claude/skills/game-feel-pass/assets/demo/after.html

2. What the scanner found in before.html. It's a read-only pattern search, so it misses events with unusual names and flags some lines that aren't events. Counts: jump 5, landing 2, collision 1, pickup 1, death 1.

Some of the hits are real events and some aren't:

So there are four real moments: jump, landing, pickup and death. Tell me if you think it missed any.

3. Effects per event. These come from the skill's strength table.

Shake is deliberately small for a landing and biggest for death. If everything shakes, nothing stands out.

Here is one excerpt from references/patterns-html5.md. Screen shake uses "trauma", where each event adds some, the offset grows with trauma squared, and trauma decays every frame:

function addShake(amount) {
  var strength = settings.reduceMotion ? 0 : settings.shake;   // 0 = off
  if (strength <= 0) return;
  trauma = Math.min(1, trauma + amount * strength);
}
function shakeOffset() {
  var t = trauma * trauma, max = 10;
  trauma = Math.max(0, trauma - 0.04);
  return { x: (Math.random() * 2 - 1) * max * t, y: (Math.random() * 2 - 1) * max * t };
}

The score and menus are drawn after the transform is reset, so text never shakes. Only drawing changes. Hitboxes, speeds and jump values stay the same.

4. Filled checklist. The "After" entries below restate what the skill documents. I haven't opened after.html or re-run its tests in this session.

Not checked:

• How any of it feels, since only someone playing can judge that.
• Whether the strengths are right for this game.
• Whether the gameplay is unchanged. The skill reports that headless-Chromium tests confirmed it before release, but those tests aren't in the package and I haven't re-run them.

The settings make the effects switchable. They don't make the game accessible or WCAG-compliant by themselves.

5. Want this on your game? Tell me:

• which engine you use,
• where the code is,
• which moments matter most,
• how strong you want the effects, and
• whether I should edit your files or just show a diff.

Or say "skip" and I'll use the defaults, which show a diff only. The HTML5 patterns are tested. The Phaser and Godot ones are untested sketches, so you'd need to check their calls against your engine version's docs.