> For the complete documentation index, see [llms.txt](https://spirit-cards.gitbook.io/spirit-cards-docs-zh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spirit-cards.gitbook.io/spirit-cards-docs-zh/spirit-cards-zhong-wen-wen-dang.md).

# Spirit Cards 中文文档

**Spirit Cards（代币符号 SPC）** 是一款「灵兽卡牌 + 对战」的 Robinhood Chain 链上游戏：卡牌**不能买，只能挖**，稀有度与战斗数值由链上种子确定性推导。

建议先读 [**简介**](/spirit-cards-docs-zh/introduction.md) 了解世界观与游戏循环，再读 [**对战总览**](/spirit-cards-docs-zh/battle.md) 理解核心机制；[合约与地址](/spirit-cards-docs-zh/project/contracts-and-addresses.md) 给出当前部署信息。

> \[!NOTE] 本空间面向**中文加密社区**。技术标识符、合约名、函数名保留英文；每个观点都带标签：`[proven]`（已链上验证）、`[assumed]`（推断/估计）、`[planned]`（待实现）。


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://spirit-cards.gitbook.io/spirit-cards-docs-zh/spirit-cards-zhong-wen-wen-dang.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.