← ClaudeAtlas

unity-input-systemlisted

Use when handling player input in Unity via the Input System package — Action Maps, PlayerInput, control schemes, or device switching. Grounds answers in the local Unity 6.3 docs over pretrained knowledge.
IceMasterT/Unity-6.3_SKILLS · ★ 0 · AI & Automation · score 70
Install: claude install-skill IceMasterT/Unity-6.3_SKILLS
# Unity Input System **Local docs gap (re-verified 2026-08-19)**: this doc mirror still lacks the Input System package's own manual — there is no `Manual/InputSystem*` chapter tree, no Action Maps / Input Actions asset walkthrough, no PlayerInput component reference, and no control-scheme documentation anywhere under `Manual/` or `ScriptReference/`. `Manual/com.unity.inputsystem.html` was re-checked directly (698 words total) and is confirmed to be nothing but the Package Manager listing stub: it states the package name (`com.unity.inputsystem`), version (1.20.0, released for Unity Editor 6000.3 / Unity 6.3 LTS), a one-line description ("A new input system which can be used as a more extensible and customizable alternative to Unity's classic input system in UnityEngine.Input"), and keywords (`input, events, keyboard, mouse, gamepad, touch, vr, xr`) — it has zero usage content, no code samples, and no links into a deeper Input System manual. Treat every Input System package workflow/API claim below (Action Maps, PlayerInput, control schemes, device pairing) as **pretrained knowledge, explicitly flagged as such** — verify precision against the in-Editor Package Manager docs (Window > Package Manager > Input System > View Documentation) or the package's own `Documentation~` folder/Samples before shipping code from this skill unmodified. Everything about the **legacy Input Manager** and the general input landscape (mobile, XR, Web, UI Toolkit) below is grounded in real, re-verif