Input Mapper
$ARGUMENTS
Read the GDD or user request, determine which input actions are needed,
and write the correct [input] section entries into project.godot.
Step 1 — Extract Required Actions
Source actions from one of:
- GDD Mechanics table — each mechanic implies input actions
(e.g., "Player can jump" →
jumpaction). - Genre preset — use a preset from Step 3 as a starting point.
- Explicit request — user or dispatching role specifies exact actions.
For ea
[Description truncada. Veja o README completo no GitHub.]