> 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-typeline.md).

# Parts of a Card - Typeline

General Rules: 

1. Cards have a card type listed on the left side of the middle segment of the card in the typeline. The types are [Champion](/general-rules/general-rules-card-types/card-types-champion.md), [Ally](/general-rules/general-rules-card-types/card-types-ally.md), [Action](/general-rules/general-rules-card-types/card-types-action.md), [Attack](/general-rules/general-rules-card-types/card-types-attack.md), [Weapon](/general-rules/general-rules-card-types/card-types-weapon.md), [Domain](/general-rules/general-rules-card-types/card-types-domain.md), [Item](/general-rules/general-rules-card-types/card-types-item.md), and [Phantasia](/general-rules/general-rules-card-types/card-types-phantasia.md).
   1. By default, Champion cards have a life stat; Ally cards have both power and life stats; Action cards have a speed stat; Weapon cards have both power and durability stats; Attack cards have a power stat.
   2. [Functional Subtypes](/general-rules/general-rules-card-types/card-types-functional-subtypes.md) may grant additional stats that are not normally found on these card types.
2. Ally, Action, Weapon, and Attack cards generally have class subtyping.
   1. A class subtype will be the first subtype listed on the typeline.
   2. Cards can have multiple subtypes with multiple class subtypes divided by a “/” on the card.
   3. Cards can be activated regardless of class typing.

{% hint style="info" %}
E.g., a player can activate Assassin cards even if their champion is a Warrior.
{% endhint %}

3. Cards sometimes have characteristic subtyping such as “Reaction,” “Skill,” “Harmony,” or “Melody.” These characteristics may be referenced by abilities as conditions for certain effects.


---

# 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-typeline.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.