> For the complete documentation index, see [llms.txt](https://rules.gatcg.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rules.gatcg.com/general-rules/general-rules-parts-of-a-card/parts-of-a-card-text-box.md).

# Parts of a Card - Text Box

General Rules: 

1. The text box of each card is reserved for rules text as well as flavor text. Rules text is written in a non-italicized font, and any reminder texts or flavor texts are written in an italicized font.
2. The only text used for consideration of effects and gameplay is non-italicized.
   1. Reminder text functions to remind players of keyword definitions or intention for effect resolution.
   2. Italicized text apart from label keywords has no impact on gameplay.
3. Line breaks for effects and abilities separate independent abilities. Triggered abilities separated by line breaks are treated as separate triggers; a triggered ability without line breaks is considered a single ability.
4. Yellow bubbles with numerals within the rules text can be used to represent reserve costs, either as costs for abilities or as costs as part of an effect.
5. Names of some cards may be shortened within their rules text. Instances of a shortened name in this fashion are treated as if they were the full name of the card.


---

# 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://rules.gatcg.com/general-rules/general-rules-parts-of-a-card/parts-of-a-card-text-box.md?ask=<question>&goal=<endgoal>
```

`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.