# Build a ridiculous tournament simulator Legion project library, edition 2026-09-06-draft-01 (en). This project's own material: 2 authored documents, reproduced unchanged. Project page: https://legion.tw/projects/desktop/ridiculous-tournament?edition=2026-09-06-draft-01 This document: https://legion.tw/api/projects/packet.md/desktop/ridiculous-tournament.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/?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. desktop/README.md — https://legion.tw/api/projects/doc/desktop/README.md?edition=2026-09-06-draft-01 2. desktop/ridiculous-tournament.md — https://legion.tw/api/projects/doc/desktop/ridiculous-tournament.md?edition=2026-09-06-draft-01 --- # Native desktop applications [All project types](../README.md) · [Shared launch](../shared/launch.md) Build a native Tauri application around the person's work or interests. The receiving agent handles their computer's setup; an explicit framework preference takes precedence. ## Projects to build - [Calling and follow-up desk](calling-follow-up-desk.md) - [Quote and estimate builder](quote-estimate-builder.md) - [Photo-to-report desk with an AI colleague](ai-photo-report-desk.md) - [Orders and production board](orders-production-board.md) - [Equipment checkout and maintenance book](equipment-checkout-book.md) - [Booking and session desk](booking-session-desk.md) - [Meme and GIF studio](meme-gif-studio.md) - [Soundboard](soundboard.md) - [Game-show host](game-show-host.md) - [Music playground](music-playground.md) - [Animated desktop pet](desktop-pet.md) - [Tabletop atmosphere controller](tabletop-atmosphere.md) - [Ridiculous tournament simulator](ridiculous-tournament.md) - [Personal AI chat app with bring-your-own-key access](byok-chat.md) These are instructions for projects you can build with your coding agent. --- # Build a ridiculous tournament simulator Build a native Tauri application for inventing contestants and watching them compete under rules the person can change. Build it extremely well as a game that is fun to set up, watch, and argue about afterward. Follow the [shared launch](../shared/launch.md), honoring an explicit framework preference. Offer a complete, amusing first competition. A race between household appliances is a good starting point: give the toaster, vacuum cleaner, and other contestants distinct strengths and let the person make the idea their own. ## Make the contestants matter Let the person create and name contestants, choose their appearance, and give them attributes relevant to the competition. Explain those attributes through their effect on play. Speed, reliability, and the ability to handle a particular obstacle should produce differences the person can recognize. The person can introduce friends, pets, fictional creatures, or their own invented competitors. Let them tune the competition: the course or events, what counts as winning, how attributes affect performance, and the amount of chance. Give changes a clear scope so they understand which competition uses which rules. Help them make an interesting contest with opportunities for both a strong favorite and an unlikely upset. ## Let people watch it happen Present the competition as a sequence of events with visible progress. In a race, the person should see who is ahead, notice an obstacle changing the positions, and follow a competitor's recovery. Choose presentation and pacing that make the outcome enjoyable to watch. Give commentary the actual events to describe. A toaster taking the lead after the vacuum gets stuck is funny because the player saw it happen. The running account and final standings should agree about the competition. Make the relationship between rules and results inspectable. After a surprising finish, the person should be able to understand what contributed: a contestant's strength, a risky choice in the rules, or a chance event. Preserve enough of the run to revisit an exciting moment and compare it with another attempt. ## Run a tournament Let the person choose entrants, run a complete competition or series, and see standings and a winner. Support the tournament format you develop together, including the way tied results are resolved. Keep the results of one run intact when the person changes the rules for the next. Make it easy to replay, adjust the speed of presentation, or pause while friends discuss what happened. Give the winner an appropriate celebration and the rest of the field a result worth inspecting. The tone should fit the group's sense of humor. Save contestant collections, rule sets, and memorable results. Give the person something simple to share, such as an exported result card or recap, and keep editable work under the ownership arrangements in the shared launch. ## Change a rule and play again Deliver the installed application with a complete example tournament. Run it, change a meaningful rule or contestant attribute, and try again. Judge whether the effect is understandable, whether watching is entertaining, and whether the person wants to invent another entrant. Use the experience to explain how rules, chance, and presentation work together. The learner discovers that they can describe an imaginary competition and build software that lets them explore it. Their role includes deciding what makes the game interesting. Later projects can let friends submit contestants or follow a live tournament from their phones. Richer commentary can also be added. Preserve the existing competition and its results so every participant is following the same game.