Which parts of player experience does it cover?

Controls, input demands, menu focus, HUD, onboarding, feedback, camera interaction and relevant accessibility options. It delivers concrete states, labels and acceptance journeys.

Will it change my game's intended difficulty?

It preserves settled mechanics and intended challenge. If an assistance or interaction proposal changes a rule, it identifies that decision for you rather than applying it silently.

Can it work from text rather than screenshots?

Yes, it can write an interaction specification from supplied rules and context. Visual inspection and layout checks need images or a build; player comfort needs observations.

Do I need the rest of the Game Squad?

No. This complete method and reference work independently. The same underlying role is also included in Game Squad Agent Skills; companion skills are optional.

What does the preview show?

An illustrative control and settings journey, including focus and recovery. It demonstrates the output format rather than a recorded model session or accessibility certification.

Can I use this for a commercial game?

Yes. You may use it for personal or commercial project deliverables. Purchased source materials remain personal and non-transferable under Agensi terms; keep them private.

Player Experience Designer Specialist

Illustrative preview: this representative editorial result is not a recorded runtime session.

Make settings reachable with the same devices used to play. Hold/toggle changes activation demand; it must not change energy consumption or falling/reset rules.

Player interaction packet GLIDE-PX-01 v1
Status: COMPLETE_LOCAL for the populated specification; implementation/layout/player checks NOT_RUN.
Producer: Player Experience Designer Specialist. Recipient: implementation owner.
Inputs: offline local pause, active-glide energy cost, fall/reset rule, requested modes and supplied mouse-only settings issue. Default keys below are proposed, not current bindings.

Action / context	Proposed keyboard / controller	Demand and feedback	Recovery
Menu navigation	arrows / D-pad	one focus move per navigation event; focused label plus outline	keep the focused row visible through digital scrolling
Confirm	Enter / primary face button	commit selected menu action once	menu events never replay as gameplay actions
Back	Escape / secondary face button	close current panel; return focus to its opener	do not silently discard a proposed remap
Glide / play	Space / shoulder button	Hold: active while held. Toggle: press changes active state. Both use the same active energy cost	on fall/reset, proposed activation clears; reset policy needs confirmation
Pause / play	Escape / menu button	open modal pause, focus Resume; gameplay frozen	resume restores gameplay and consumes the menu confirm event

Actual relevant labels
Main: Start, Options, Quit.
Options: Controls, Display & Camera, Audio, Back.
Controls: Glide mode — Hold / Toggle; Remap controls; Restore proposed defaults; Back.
Pause: Resume, Options, Restart room, Return to main menu.
Energy cue: named Energy meter plus active-glide status; an exhausted-energy state must follow the actual mechanic rather than a cosmetic animation.

Complete state path
Boot focuses Start. Up/down or D-pad reaches Options; Confirm opens Options with Controls focused. Controls is navigable and scrolls the focused row into view. Back restores Controls focus in Options, then Options focus in Main. Start enters gameplay using the chosen mode. Pause captures menu input and focuses Resume; Options returns to pause with Options focused. Resume closes pause, clears the activating menu event and hands input back to play. Quit/return confirmation, if adopted, must retain Cancel and restore opener focus; no quit-save behavior is assumed.

Remapping
Select Glide → show “Press a new input for Glide” with Cancel available. On conflict, show both affected actions: “This input is used by [actual action]. Replace that binding or cancel?” Replacement is committed only after explicit confirmation; cancel preserves both old bindings. Update menu labels, tutorials and HUD prompts from the same binding record. Do not remove a binding needed to reach Controls without warning and a navigable recovery route.

Device-change recovery, proposed
Pause automatically on controller disconnect in this offline game only if the owner accepts the policy. Show “Controller disconnected. Reconnect it or continue with keyboard.” Keyboard Confirm/Back remains available. Resume requires a deliberate new action and retains the chosen mode; no surprise glide activation. Input device changes update prompts without redefining the underlying action.

Persistence proposal
Apply settings for the current session when confirmed. If durable save fails, show “Settings applied for this session, but could not be saved. Retry saving or continue.” Do not claim persisted success. Keep the selected settings in memory; exact storage/error ownership is an implementation dependency. Restored controls must match persisted values after a successful reload.

Criteria GL-PX1–6

Keyboard-only and controller-only boot→controls→start→pause→options→resume paths retain focus and a visible focused row.
Hold/toggle consume energy identically during equal active intervals; neither bypasses the mechanic.
Cancelled conflicting remap retains prior bindings; confirmed remap updates all prompts.
Resume does not replay Confirm as Glide or another gameplay action.
Disconnect and persistence-failure paths follow ratified proposals and preserve a usable recovery.
Largest supported text and long menu content retain focus visibility and critical energy information on the actual display.

Source-to-spec reasoning preserves supplied rules; all candidate, layout and player checks are NOT_RUN. A first-player observation should distinguish inability to activate, misunderstanding the mode and understood-but-failed challenge. Next action: owner confirms reset/disconnect/persistence policies; implementer builds the journey and records platform/input/display proof.

About this skill

Let players take on the challenge you designed.

Player Experience Designer Specialist helps you shape the path from opening the game to understanding, controlling and recovering within it. Use it when controls feel disconnected, settings are hard to reach, feedback is unclear or a tutorial explains buttons without teaching play.

The method starts with player actions and their meaning, then connects input, focus, HUD, menus, learning and options. It preserves the intended challenge while addressing barriers that get in its way. Hold and toggle modes, remapping, device changes and pause/resume become defined behaviors rather than isolated feature requests.

Your deliverables can include

An action map with input demands, bindings, feedback and remap behavior.
Complete menu and gameplay flows with focus, cancellation and recovery states.
HUD, onboarding and cue specifications, plus journeys to check across the relevant devices and displays.

For example, ask it to make a controller-only settings journey reachable from the first menu. It can define navigation, conflict messages, restored focus and prompt updates while keeping the underlying gameplay rules intact.

Bring your intended experience, controls, relevant screens or states, target devices and known constraints. The standalone method and reference are included. You supply AI access; text specifications can be developed without a build, while visual inspection, interaction checks and player accessibility evaluation need the corresponding images, tools and participants.

Player Experience Designer Specialist