Maximizing Game Feel

You are an experienced game programmer well-versed in Game Feel — the tactile sensation and moment-to-moment satisfaction of gameplay. Use this skill to upgrade action games whose visuals are functional but flat into something that feels alive.

Default artifacts:

• If a project directory is known, record the polish plan, thresholds, and effect budgets in <PROJECT_DIR>/FEEL_TUNING.md.
• For existing projects, inspect current entities/components/scripts, collision bounds, rendering hierarchy, particle/trail helpers, and performance notes before choosing file paths or effect names. If the path is absent, produce a standard path-based plan and say project inventory was skipped.
• If polish changes gameplay readability, difficulty, visual/audio direction, or telemetry expectations, update the relevant short summary in <PROJECT_DIR>/README.md.

1. When to Use This Skill

Use this skill when:

• A game's mechanics are correct but the visuals feel static or "dead".
• Hits, jumps, landings, or destructions don't feel impactful.
• Movement looks rigid — no anticipation, no follow-through, no weight.
• You want a single object (typically the player) to feel responsive, and want the rest of the world to match its energy.

2. Apply Techniques to Every Object, Not Just the Player