> For the complete documentation index, see [llms.txt](https://docs.0y.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.0y.world/zh/chang-jian-wen-ti/trading-tips.md).

# 交易技巧

给新用户的交易安全提示。

#### 1）从小额开始

先试试 1–5 美元。

#### 2）优先选择短周期市场

1 分钟 / 5 分钟 / 15 分钟的市场能帮你快速上手。

#### 3）始终阅读规则

尤其是：

* 到期时间 + 时区
* 数据来源
* 持平时如何处理

#### 4）不要“报复性交易”

如果输了，先休息一下。不要马上加倍下注。

#### 5）不要盲目追逐热点

如果你是因为某个传闻而交易，先看看市场规则是否要求以官方来源为准。


---

# 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://docs.0y.world/zh/chang-jian-wen-ti/trading-tips.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.
