OpenParable
Skip to content
← Back to skills

Unity Input System

Development
unity-input-system

Unity Input System is an Agent Skill for development published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Unity New Input System configuration skill for action maps, device bindings, control schemes, and cross-platform input handling.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/specializations/game-development/skills/unity-input-system/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/unity-input-system, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Unity Input System Skill

New Input System configuration and implementation for Unity.

Overview

This skill provides capabilities for implementing Unity's New Input System, including action maps, device support, and cross-platform input handling.

Capabilities

Action Configuration

  • Create Input Action Assets
  • Define action maps and actions
  • Configure bindings and interactions
  • Set up action types (value, button, passthrough)

Device Support

  • Configure gamepad support
  • Implement keyboard/mouse handling
  • Set up touch controls
  • Handle XR controllers

Control Schemes

  • Define control schemes
  • Implement scheme switching
  • Support local multiplayer
  • Configure device requirements

Runtime Handling

  • Generate C# input classes
  • Handle input events
  • Implement rebinding UI
  • Manage device changes

Prerequisites

  • Unity 2021.3+
  • Input System package installed

Usage Patterns

Input Actions Asset

// Generated PlayerInput class usage
public class PlayerController : MonoBehaviour
{
    private PlayerInputActions inputActions;

    void Awake()
    {
        inputActions = new PlayerInputActions();
    }

    void OnEnable()
    {
        inputActions.Gameplay.Enable();
        inputActions.Gameplay.Jump.performed += OnJump;
        inputActions.Gameplay.Move.performed += OnMove;
    }

    void OnDisable()
    {
        inputActions.Gameplay.Disable();
    }

    void OnJump(InputAction.CallbackContext ctx)
    {
        // Handle jump
    }

    void OnMove(InputAction.CallbackContext ctx)
    {
        Vector2 movement = ctx.ReadValue<Vector2>();
    }
}

Rebinding

public void StartRebinding(InputAction action)
{
    action.PerformInteractiveRebinding()
        .WithControlsExcluding("Mouse")
        .OnComplete(operation => {
            operation.Dispose();
            SaveBindings();
        })
        .Start();
}

Best Practices

  1. Use Input Action Assets over direct polling
  2. Implement rebinding for accessibility
  3. Test all supported devices
  4. Handle device disconnection gracefully
  5. Save custom bindings to PlayerPrefs

References