{
  "edition": {
    "edition": "2026-09-06-draft-01",
    "language": "en",
    "publicationState": "published",
    "sourceRevision": "a7e788eb4b151fd92c1f58153e015773e3a829af",
    "projectCount": 67,
    "documentCount": 94,
    "skillCount": 10,
    "archivePath": "library.zip",
    "archiveBytes": 181812,
    "releasedAt": "2026-09-08T05:03:11.129+00:00"
  },
  "access": {
    "released": true,
    "rehearsal": false
  },
  "project": "ai-apps/tabletop-game-master.md",
  "markdown": "https://legion.tw/api/projects/packet.md/ai-apps/tabletop-game-master.md?edition=2026-09-06-draft-01",
  "documents": [
    {
      "path": "ai-apps/README.md",
      "text": "# Applications with AI operators\n\n[All project types](../README.md) · [Shared launch](../shared/launch.md)\n\nGive AI context and real tools to operate the application alongside the person. Use the existing coding agent where it supplies the needed collaboration.\n\n## Projects to build\n\n- [A route planner that helps you get home earlier](route-planner.md)\n- [A calling desk with an AI colleague](calling-desk-collaborator.md)\n- [A language-practice app with an AI teacher](language-practice-teacher.md)\n- [An AI-operated audio workshop](audio-workshop.md)\n- [A tabletop adventure with an AI game master](tabletop-game-master.md)\n\nThe [photo-to-report desk](../desktop/ai-photo-report-desk.md) already supplies a full AI-operator example and has one canonical home in the desktop collection.\n\nThe [BYOK chat app](../desktop/byok-chat.md) teaches provider access, system-prompt control, and image generation. It also has one canonical home in the desktop collection.\n\nThese are instructions for projects you can build with your coding agent.\n"
    },
    {
      "path": "ai-apps/tabletop-game-master.md",
      "text": "# A tabletop adventure with an AI game master\n\nBuild 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](../shared/launch.md).\n\nChoose 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.\n\n## Give the player a world they can act in\n\nMake 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.\n\nSupport 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.\n\nKeep 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.\n\n## Let the game master operate the game\n\nReuse 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.\n\nMake 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.\n\nDistinguish 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.\n\nGive 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.\n\n## Keep play recoverable and enjoyable\n\nSave 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.\n\nUse 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.\n\nAn existing [tabletop atmosphere controller](../desktop/tabletop-atmosphere.md) 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.\n\n## Deliver an evening of play\n\nComplete 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.\n\nTeach 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.\n"
    },
    {
      "path": "desktop/tabletop-atmosphere.md",
      "text": "# Build a tabletop atmosphere controller\n\nBuild a native Tauri application for preparing and controlling the sound and imagery of a tabletop session. Build it extremely well for someone who is also busy running the game. Follow the [shared launch](../shared/launch.md), honoring an explicit preference for another framework.\n\nLearn what the person's group plays and how they use music, maps, pictures, and sound effects. Design a complete application around that experience. If they already built the [soundboard](soundboard.md), carry its collections and capabilities into this extension.\n\n## Prepare scenes\n\nLet the person assemble a scene from ambient sound, music, a map or illustration, visual effects where useful, and individual cues they may want during play. They can choose material from their own collection, adjust its presentation, and save the result for the session.\n\nA market scene might combine a crowd, distant bells, and a street map. When the conversation turns dangerous, the host may want different music while keeping the market and map. Make scenes flexible enough to support those changes naturally.\n\nGive the person a convenient place for relevant scene notes and upcoming cues. Keep their private preparation distinguishable from material presented to players. Arrange the scene collection so they can find a place or event when the group takes an unexpected direction.\n\n## Control it while telling the story\n\nMake common actions quick to recognize and comfortable to use while attention is on the table. The host can enter a scene, adjust the mix, trigger a cue, change the displayed image, or stop the sound. Show what is actually playing and which scene is active.\n\nGive transitions appropriate care. Music may fade between scenes while an individual effect plays once. A sound intended to continue should keep doing so until the chosen transition or host action changes it. Let the host control the timing and balance so the application supports the conversation.\n\nSupport temporary changes during play and an understandable way to return to the prepared scene. If the person likes the new arrangement, they can save it deliberately.\n\nSet up the person's real audio and display arrangement. They may use laptop speakers, a separate sound system, a television, or a projector. Make the chosen setup work from the host's seat, with clear control over what the players see and hear.\n\n## Keep the preparation together\n\nSave scenes with their related material and organize them into the person's adventures or sessions. Keep imported originals available and make missing or moved media understandable. Apply the shared launch's ownership and recovery guidance so preparation survives closing the app or reorganizing work.\n\nSupply a ready-to-try example using material suitable for sharing with the project. The person should be able to feel what the app does before spending an evening preparing their own scenes.\n\n## Run a short scene\n\nDeliver the installed application and rehearse a few minutes of the person's game. Enter a location, change the mood while the conversation continues, trigger a cue, and move to another scene. Judge whether the host can do this while remaining involved with the players.\n\nExplain how a prepared scene coordinates several kinds of media, while individual controls let the host react to what actually happens. The person learns that their preferred way of running a session can determine how the software works.\n\nLater projects can deliver private clues to players' phones or add richer shared displays. Keep those additions connected to the same scenes and session. The host should retain the preparation and live controls they already know.\n"
    }
  ]
}