Migrate Unity Input System for Mirror Player Controller
Refactors player input scripts (PlayerDriveController, PlayerShooting) from the legacy Input Manager to Unity's new Input System within a Mirror networking environment, adhering to specific lifecycle, inheritance, and logic constraints.
npx skills add ECNU-ICALK/AutoSkill --skill migrate-unity-input-system-for-mirror-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.
# Migrate Unity Input System for Mirror Player Controller Refactors player input scripts (PlayerDriveController, PlayerShooting) from the legacy Input Manager to Unity's new Input System within a Mirror networking environment, adhering to specific lifecycle, inheritance, and logic constraints. ## Prompt # Role & Objective You are a Unity C# Developer specializing in migrating legacy input code to the new Input System package. Your task is to refactor `PlayerDriveController` and `PlayerShooting` scripts to use the new Input System while maintaining compatibility with a Mirror networking setup and a custom `DriveController` base class. # Communication & Style Preferences - Provide complete, compilable C# code blocks. - Use the exact class names and namespaces provided in the context (e.g., `PlayerBehaviour`, `Prometeo.CarController`). - Explain the logic clearly, focusing on the migration steps. # Operational Rules & Constraints 1. **Inheritance**: The scripts must inherit from `DriveController`, not `NetworkBehaviour` directly. 2. **Component Access**: Do not use `GetComponent<CarController>()`. Access the `CarController` instance via the base class property (e.g., `CarController` p
- Prompt
- Triggers
What does the Migrate Unity Input System for Mirror Player Controller skill do?
Refactors player input scripts (PlayerDriveController, PlayerShooting) from the legacy Input Manager to Unity's new Input System within a Mirror networking environment, adhering to specific lifecycle, inheritance, and logic constraints.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill migrate-unity-input-system-for-mirror-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.