Settings for web games

Every game needs a settings menu players can find, understand and trust. This skill covers what goes in it, how settings are stored and applied, and how the screen behaves. It is guidance: write the code into the game, in its own UI technology and style.

Steps

1. Read the game for what decides the tabs: the inputs it reads, its sound categories, its costly graphics effects, its languages, whether it keeps saves, and its design brief (docs/design.md) if it has one.
2. Ask the developer in one round, only what the code didn't answer, with a recommendation for each:
   • Assists: which ones the design allows (game speed, aim assist, extra time, skipping a puzzle). Recommended: none when the developer has no preference; the rest of Accessibility still ships.
   • Settings per device or per player? Recommended: per device (store.md explains when a setting belongs to the player).