> 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-tw/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-tw/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.