Teach one rule at the moment it matters
Show the primary input beside the first place it applies. If the player must drag to aim and release to fire, separate those steps visually rather than presenting a paragraph of controls. Let the first action happen in a low-pressure situation where a mistake is recoverable. Once the player has seen the result, introduce the next rule only when a new obstacle depends on it.
Let the interface carry some explanation
Use labels, highlights or a brief animation to connect an input area with its effect. Make the goal visible during play, not only in a pre-game screen that may be dismissed. A tutorial that requires memorizing a sequence can fail when the player reaches the actual control. Prefer a cue that remains available at the relevant moment, while keeping it out of the way after the player has learned the action.
Check learning through play
After the first example, present a similar decision without the instruction and watch what happens. If players repeat the taught action correctly but fail when one condition changes, clarify that condition instead of repeating the whole tutorial. Offer a way to review controls when the game supports it. Test with people who have not watched development; familiarity makes designers underestimate what the screen leaves unexplained.
Questions about game onboarding design
How long should a game tutorial be?
As short as the rules allow. Teach the first necessary action, then add information when the player reaches a situation that needs it.
Should tutorials allow mistakes?
A low-cost first attempt can help players discover the result of an action. Protect them from irreversible losses while they are still learning the basic control.