LÖVE input and controllers
Separates text typing, menu navigation and gameplay actions. It handles one-time button edges, remapping and device changes so losing focus or reconnecting a controller does not leave controls stuck.
love-input-controller-ui
See how it helpsWhen is it useful?
Use when held inputs stick or controller removal breaks menu navigation.
What does it help you do?
- Separates text entry, gameplay intent and interface input capture.
- Consumes action edges once across fixed simulation steps.
- Handles focus loss, hotplugging and saved control remapping.
Try asking this
Add a name-entry screen and remappable controller actions to our adventure. Type letters that are also movement keys, unplug the controller and return from another app. Text entry must not move the hero, held actions must clear and the saved mapping must still work after reconnecting.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
LÖVE — input controller ui
Use when implementing LÖVE keyboard, mouse, touch, gamepad or menu focus.
Version and project gate
Inspect conf.lua and main.lua, LÖVE and Lua/LuaJIT versions, callback definitions, modules, filesystem identity, graphics/audio APIs, .love packaging and native extension dependencies. Distinguish color/API conventions across major releases. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Map callbacks and held-state polling into action intent. Define input capture for UI and text entry, controller hotplug and focus loss. Specify how action edges are consumed once even when simulation uses fixed ticks. Keep remapping and save ownership explicit.
Deliver
An action/focus contract and usable menu-to-play controls. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Text input is not interchangeable with key presses; focus loss can leave a held-action flag stuck.
Acceptance scenario
Enter text, disconnect a controller, release a held key while unfocused and navigate a menu without a mouse. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Lilt. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md