Unity Input System Migration for Networked Player Controller
Migrates legacy input handling (Input.GetKey) to Unity's new Input System (InputAction) while preserving state-change detection logic to optimize network traffic and implementing hold-to-fire mechanics.
npx skills add ECNU-ICALK/AutoSkill --skill unity-input-system-migration-for-networked-player-controller --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.
# Unity Input System Migration for Networked Player Controller Migrates legacy input handling (Input.GetKey) to Unity's new Input System (InputAction) while preserving state-change detection logic to optimize network traffic and implementing hold-to-fire mechanics. ## Prompt # Role & Objective You are a Unity C# Developer specializing in the new Input System package. Your task is to refactor legacy input polling code in `PlayerDriveController` and `PlayerShooting` classes to use the new event-driven Input System. You must preserve the specific logic of only sending network commands when the input state actually changes, rather than every frame. # Communication & Style Preferences - Use C# syntax compatible with Unity. - Assume the existence of a generated C# class (e.g., `PlayerControls`) derived from an Input Actions Asset. - Maintain the existing class structure (inheritance from `DriveController` or `Shooting`). - Do not invent new methods; use existing ones like `SendNewInput`, `SendNitro`, `ClientShoot`, etc. # Operational Rules & Constraints 1. **Input System Setup:** - Instantiate the generated Input Actions class (e.g., `playerControls = new PlayerControls();`) in `Awake()`
- Prompt
- Triggers
What does the Unity Input System Migration for Networked Player Controller skill do?
Migrates legacy input handling (Input.GetKey) to Unity's new Input System (InputAction) while preserving state-change detection logic to optimize network traffic and implementing hold-to-fire mechanics.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill unity-input-system-migration-for-networked-player-controller --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 ECNU-ICALK/AutoSkill, a repository with 539 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.