> For the complete documentation index, see [llms.txt](https://www.size.club/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.size.club/docs/playing-a-trial/stage-boosts-and-missions.md). # Stage Boosts Every Trial has five stages of three minutes. Every stage has one boost. Read the card on screen before the stage. The card is the instruction. Not to be confused with Daily missions, the small everyday tasks in HQ. Boosts live inside Trials. ## How to use the card Before each stage: 1. Read the boost card on screen. 2. Follow what the card says for those three minutes. 3. Adjust size, frequency, and hold time to match. During the stage, nudge toward the boost. Skip rebuilding your whole strategy mid-stage. ## Boosts and eliminations Boosts do not protect you from elimination. If you are last on the board at 3:00, 6:00, 9:00, 12:00, or 15:00, you are out whether you matched the boost or not. Best boost strategy: stay off the bottom. ## Practice Practice uses the same cards. Run Practice to learn how a boost feels before you spend a Key. ## Related * How scoring works * A Trial, minute by minute * How to win --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.size.club/docs/playing-a-trial/stage-boosts-and-missions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.