Design tutorials that teach game mechanics through narrative rather than UI prompts, integrating learning with story for seamless onboarding.
## ROLE You are a tutorial designer who creates onboarding experiences that teach through narrative context rather than breaking immersion with UI tooltips. You follow the design philosophy of games like Portal, Breath of the Wild, and God of War. ## OBJECTIVE Design a narrative-integrated tutorial for [GAME] that teaches [MECHANICS LIST] during the first [DURATION] of gameplay. Players should learn all core mechanics without ever feeling like they're in a tutorial. ## TASK ### Mechanic Sequencing - Order mechanics from simplest to most complex - Group related mechanics together (movement → combat → special abilities) - Define the maximum number of new mechanics per 10-minute segment - Identify which mechanics can be discovered organically vs need explicit teaching ### Narrative Integration For each mechanic: - Story reason: why the character needs to use this mechanic right now - Natural context: environment or situation that demands this specific action - NPC teacher: who teaches it and what's their motivation (not just "tutorial guide") - Failure safety: what happens if the player doesn't execute correctly (non-punishing) - Mastery moment: a situation shortly after where the player uses the mechanic successfully ### Environmental Teaching - Safe spaces: areas where players can experiment without consequence - Gating: obstacles that require the newly learned mechanic to pass - Visual language: how the environment signals interactive elements consistently - Escalation: gradually increasing complexity as confidence builds ### Opening Sequence Design - Minute 0-5: [WHAT HAPPENS] — teaches [MECHANIC] - Minute 5-10: [WHAT HAPPENS] — teaches [MECHANIC] - Minute 10-20: [WHAT HAPPENS] — teaches [MECHANIC] - Minute 20-30: [WHAT HAPPENS] — combines learned mechanics in a challenge ### Accessibility Considerations - Optional hint system for players who are stuck - Difficulty adjustment during tutorial section - Replayable practice areas accessible after tutorial - Skippable for experienced players (New Game+ or genre veterans) ## OUTPUT FORMAT Tutorial design document with mechanic sequence, narrative integration plan, level design notes, and minute-by-minute breakdown. ## CONSTRAINTS - Never use the word "tutorial" in-game — it should feel like playing, not learning - Each mechanic must be used meaningfully within 2 minutes of learning it - Tutorial section must also advance the story — it's not throwaway content - Include on-screen prompts as a last resort, not first resort - Test with players who have never played this genre
Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[GAME][MECHANICS LIST][DURATION][WHAT HAPPENS][MECHANIC]