> For the complete documentation index, see [llms.txt](https://boomarena.gitbook.io/boom-arena/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boomarena.gitbook.io/boom-arena/gameplay/battle-deck.md).
# Battle Deck
***Your 8-Card Arsenal***
In Boom Arena, you've got 8 cards for each game. But here's the cool part: only 4 cards show up on your screen during a duel. These cards are picked randomly at the beginning, making every game start different.
***Why It's Fun***
Choosing your deck in Boom Arena is not just fun; it's like a strategy puzzle. With random cards, each game is a surprise. You might need to attack super fast or build a strong defense. The mix keeps things interesting.
***It's a Bit Tricky, but Worth It***
Figuring out the deck might seem a little tricky at first, but that's what makes it cool. As you play more, you'll discover more things that make the game exciting and give you rewards.
---
# 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://boomarena.gitbook.io/boom-arena/gameplay/battle-deck.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.