A tabletop adventure with an AI game master

Build a native Tauri adventure app in which the person's existing coding agent can run a game using the application's map, characters, inventory, dice, and campaign record. Build it extremely well. The player should be able to try something unexpected and see its consequences become part of the game. Follow the shared launch.

Choose a tone and rules suitable for the person, and deliver a complete opening adventure. Solo play is a useful starting arrangement; shape local group play around the people actually participating. Prepare characters, places, objects, and a situation that invites choices, with enough material for a satisfying session.

Give the player a world they can act in

Make the present situation understandable: where they are, who is present, what they know, and what their character can use. Let them inspect possessions, revisit discoveries, and look at the map without interrupting the conversation to reconstruct basic facts.

Support ordinary-language actions and direct use of the interface. A player might ask a suspicious ferryman a question, inspect the bridge, or try an object in their bag. Let the game master respond creatively to their intent and apply the chosen rules when an outcome needs resolving.

Keep player decisions with the players. Give the game master freedom to portray characters, introduce complications, and decide reasonable consequences while leaving room for approaches the adventure's author did not anticipate.

Let the game master operate the game

Reuse the existing agent's installation and account. Give it proper tools to read relevant campaign context, inspect the current scene, resolve dice, move characters, award or spend items, record discoveries, and advance events. Keep the tools connected to the same state the player sees.

Make a narrated event and its recorded consequences agree. When the party gives away a key, the inventory should reflect the exchange. When a roll resolves an uncertain action, the narration should continue from the actual result. Let the player see the rule or event behind a consequential change.

Distinguish what the players know from what the game master knows. Hidden places, character motives, and unrevealed information should remain available to the game master through appropriate context while the player-facing map and record show what has been discovered.

Give the agent room to invent details as play develops, and preserve those that become established. Later scenes should remember the bargain made with the ferryman, including if the player returns several sessions afterward.

Keep play recoverable and enjoyable

Save the campaign's meaningful events, current situation, and working game-master context. Make ending a session and resuming it comfortable. Help the person correct a mistaken state change or return to a prior save with a clear understanding of the game they are continuing.

Use pacing, readable presentation, and appropriate sound or art to serve the chosen atmosphere. Let the person pause, change the tone, or ask how a rule works. Make any additional model or asset access clear during setup.

An existing tabletop atmosphere controller can supply prepared sound and scenes if the person has built it. Connect useful work already present and keep this adventure playable on its own.

Deliver an evening of play

Complete the installed app, agent tools, and opening adventure. Play through consequential choices, resolve an uncertain action, use an acquired item, and resume from a saved session. Judge the experience as a game: whether choices matter, characters respond coherently, and the person wants to find out what happens next.

Teach how creative model judgment can cooperate with exact game records. A later shared-screen or phone extension can give several players their own views of this same campaign.