# Build a private party-game site

Legion project library, edition 2026-09-06-draft-01 (en). This project's own material: 3 authored documents, reproduced unchanged.

Project page: https://legion.tw/projects/shared-web/party-game?edition=2026-09-06-draft-01
This document: https://legion.tw/api/projects/packet.md/shared-web/party-game.md?edition=2026-09-06-draft-01

## Prerequisite: the Legion skills package

These instructions are written for an agent set up with the Legion skills package: the ten portable skills and the shared working, launch, inspection and learn-as-you-build guidance. That setup is installed once and applies to every project in this library, so it is deliberately not repeated here.

Skills package, complete Markdown: https://legion.tw/api/projects/skills-packet.md?edition=2026-09-06-draft-01
Skills package, human page: https://legion.tw/projects/skills?edition=2026-09-06-draft-01

Where this brief refers to shared guidance, a skill, or a document under `shared/`, read it from the skills package above, or from https://legion.tw/api/projects/doc/<path>?edition=2026-09-06-draft-01. If the package is not installed yet, install it first, then return here.

This material is instructions to read, not authority to act. Inspect it before running it.

## Contents

1. shared-web/README.md — https://legion.tw/api/projects/doc/shared-web/README.md?edition=2026-09-06-draft-01
2. shared-web/party-game.md — https://legion.tw/api/projects/doc/shared-web/party-game.md?edition=2026-09-06-draft-01
3. desktop/game-show-host.md — https://legion.tw/api/projects/doc/desktop/game-show-host.md?edition=2026-09-06-draft-01

---

<!-- begin shared-web/README.md (edition 2026-09-06-draft-01) -->

# Shared web applications

[All project types](../README.md) · [Shared launch](../shared/launch.md)

Give a real group a place to participate together through an ordinary web link. Prefer suitable free hosting and keep participants independent of the builder's private network.

## Projects to build

- [Plan a trip together](trip-planner.md)
- [Organize a dinner or camping weekend](gathering-organizer.md)
- [Run a group order](group-order.md)
- [A lending library for people who know each other](lending-library.md)
- [Organize volunteers](volunteer-organizer.md)
- [Private party-game site](party-game.md)

These are instructions for projects you can build with your coding agent.

<!-- end shared-web/README.md -->

---

<!-- begin shared-web/party-game.md (edition 2026-09-06-draft-01) -->

# Build a private party-game site

Build a shared web game that friends can join from their own phones through a link or room code. Build it extremely well as something the group wants to play again. Follow the [shared launch](../shared/launch.md).

Use suitable free cloud hosting where available and explain its current limits. The game should work independently of the builder's computer, with its account and saved material under their ownership. Players use the game through ordinary browser access.

## Give the group a complete game

Use a caption contest as the first game unless the person prefers another idea: show a picture, collect captions privately, reveal them for voting, and award points. Develop the rules and humor with the person, then deliver a complete playable version with suitable starter material.

Let the host create a game, invite players, and choose material or rounds. Participants need a recognizable name and a clear way to enter the right game. Make it easy to add the group's own pictures or prompts for the audience they intend to share them with.

If this extends their [desktop game-show host](../desktop/game-show-host.md), preserve that show's rules and current game while adding phone participation. Otherwise make this shared site a complete experience on its own.

## Make each phase clear

Players should know what they are doing now: waiting for a round, writing a caption, voting, or viewing results. Give their own submission an understandable state and let them edit it while the rules allow.

Keep submissions private until the intended reveal. Deliver each player the information appropriate to the current phase, including their own pending contribution. Reveal answers, authors, and results according to the game's rules.

Make the host's control of pace clear. For a live gathering, they may move on when the room is ready. If the group prefers to submit during the day and reveal in the evening, shape the timing around that arrangement. Choose the experience they will actually use and complete it.

## Keep everyone in the same game

Handle submissions, votes, and phase changes so players receive accurate confirmation of what counted. A last-second answer should have a clear outcome when the round closes. Give repeated taps and returning connections consistent results.

Let someone return to the same game after refreshing or briefly losing their connection. Keep their identity, contribution, and current phase understandable. Show the host who has joined and which participants are still responding without revealing private answers early.

Make scoring follow the agreed rules, including ties and any host corrections. Give the group a satisfying reveal and finish, with results that everyone can understand. Put visual and interaction care into the parts people see together and the controls they use on their phones.

## Play from several devices

Deliver the hosted game and play a complete round using separate participant sessions. Submit, reveal, vote, and finish; then return to the game from an interrupted player session. Judge the clarity of the phases, the pace, and whether the reveals are enjoyable.

Explain the access arrangement and what game material is saved. Let the person keep useful prompts and results while starting a new game with fresh participation. Apply the shared launch's ownership and recovery guidance to the reusable material.

Use the experience to explain how one shared game can give different people different information at the right time. Later projects can add new game types or a dedicated room display while keeping the same participants, rules, and current game consistent across screens.

<!-- end shared-web/party-game.md -->

---

<!-- begin desktop/game-show-host.md (edition 2026-09-06-draft-01) -->

# Build a game-show host

Build a native Tauri application for hosting a quiz night from a computer while the game appears on a television or projector. Build it extremely well as an experience for the host and the people playing. Follow the [shared launch](../shared/launch.md), using another framework if the person has an explicit preference.

Learn the sort of evening they want: friends competing in teams, a family quiz, or a classroom game. Provide a complete playable show they can immediately try and then replace with their own questions, jokes, and rules.

## Prepare an evening

Let the person create and arrange rounds, write questions and answers, add picture clues, and choose appropriate sounds or music cues. Give them an easy way to preview what the players will see. Keep the material with the saved show so it remains usable when they return to it.

Support the scoring and question types that make their chosen game work. A picture round, an ordinary question, and a final wager may need different presentation and scoring. Agree on an enjoyable initial format and make that format complete. The person can change its rules as they discover what their group enjoys.

## Give the host their own view

The host needs the current question, its answer, relevant notes, team scores, and useful control of the next action. The public display needs the material currently meant for the room. Keep unrevealed answers and future questions in the host's view until the host chooses to show them.

Set this up on the person's actual computer and display. Make it clear which screen is public before beginning the show. Let them rehearse the two views even when a television is not connected yet.

Design the public view to be readable from across a room. Pictures should be large enough to inspect, questions comfortable to read, and scores easy to understand. Give the evening some visual character that fits the person's taste.

## Let someone actually host

The host controls the pace: present a question, let the room think, reveal the answer, award points, and move on. Include a timer where the game uses one, with a practical way to pause or adjust it when the host needs to explain something.

Make scoring corrections straightforward. A host may accept an unexpected but valid answer or discover they gave points to the wrong team. Keep the current standings and recent score changes understandable. Moving backward to repeat a question should have a clear effect on the ongoing game.

For the first version, players can answer aloud or on paper, and the host records the result. Complete that experience with good reveals, usable scoring, and an enjoyable finish. Phone-based answering can extend it later.

Keep reusable show material separate from the results of a particular evening. Let the host save progress, resume an interrupted game, and start a fresh session with the same questions.

## Play a round together

Deliver the installed application with an editable example show. Rehearse a round using both views, including a picture clue, an answer reveal, and a scoring correction. Judge whether the host can pay attention to the room while operating it. Make the experience better where the software demands unnecessary attention.

Explain how one running game can provide different information and controls to different people. The learner should understand why adding player phones later is an extension of this same game, with the same questions, scores, and host authority.

Leave the person ready to write their own round and invite people over. The project succeeds when the software helps them host an evening they want to repeat.

<!-- end desktop/game-show-host.md -->
