Input Systems

Use when the user asks about a game input system, action mapping, key rebinding, gamepad input, touch gestures, IME text input, haptics or input latency. Produces device-agnostic input architecture tied to the simulation tick. Not for menu accessibility audits (use design-accessibility) or Unity-specific setup (use unity).

45 stars 6 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill input-systems
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/game/client-engine/input-systems ~/.claude/skills/input-systems

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Input Systems — Deep Engineering Guide

## Purpose
Input is the player's handshake: it must be lag-free, remappable, device-agnostic and deterministic. This skill covers device abstraction, action mapping, raw sampling vs event flows, text/IME, touch/gestures, haptics and the input-to-simulation timing that separates "responsive" from "floaty".

## Agent Protocol

### Trigger
"input system", "action mapping", "key rebinding", "gamepad input", "touch gestures", "IME text input", "haptics", "input latency".

### Input Context
- Engine and platforms (PC, console, mobile)
- Device set (keyboard/mouse, gamepad, touch)
- Networked or local (determinism of input stream)

### Output Artifact
Input architecture and code for sampling, mapping and dispatch. No file unless requested.

### Response Format
```
Devices: {list}
Actions: {action -> bindings}
Timing: {sample point vs sim tick}
Code: {snippet}
Risks: {latency, lost events, rebinding conflicts}
```

## 1. The Three Layers

```
device world (keyboard/mouse/stick/controller/gamepad/touch)
  → InputProvider (concrete device driver)
  → InputSystem (maps physical → logical actions, accumulates)
  → Game (consumes actions; sim at fixed tick)
```

The **action abstraction** is what makes one input system serve every device + remap UIs.

## 2. Device Abstraction

```cpp
struct InputEvent { Device device; DeviceId id; float3 raw; ButtonState state; };
```

| Device | Raw data | Notes |
|--------|----------|-------|
Read the full skill on GitHub

Details

Skill name
input-systems
Path
skills/game/client-engine/input-systems/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Input Systems skill do?

Use when the user asks about a game input system, action mapping, key rebinding, gamepad input, touch gestures, IME text input, haptics or input latency. Produces device-agnostic input architecture tied to the simulation tick. Not for menu accessibility audits (use design-accessibility) or Unity-specific setup (use unity).

How do I install the Input Systems skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill input-systems. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Input Systems popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Nextjs Internals

45

j4flmao/agent-skills

Use when the user asks why a Next.js route is dynamic, how the App Router renders and streams, the RSC payload, partial prerendering, Cache Components / 'use cache', the router cache or the request lifecycle. Produces a diagnosis of static vs dynamic rendering and stale data in Next.js 15/16. Not for everyday App Router features (use react-nextjs).

Frontend & Design

Htmx

45

j4flmao/agent-skills

Use when the user asks about htmx, hx-get, hx-post, hx-swap, hx-target, hypermedia/HATEOAS apps or server-driven partial page updates. Produces htmx attributes, HTML-fragment server responses and CSRF-safe request handling. Not for client-side reactivity inside a page (use alpinejs).

Frontend & Design

Preact

45

j4flmao/agent-skills

Use when the user asks about Preact, Preact signals, preact/compat, Preact vs React, Preact SSR or cutting bundle size with a React-compatible library. Produces Preact components, signal-based state and compat aliasing. Not for React-specific architecture (use react-architecture).

Frontend & Design

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.