> For the complete documentation index, see [llms.txt](https://help.daak2.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daak2.com/zh-tw/kai-shi-shi-yong/quick-start.md).

# 首次設定

## 1. 建立帳本

1. 開啟 **帳本**。
2. 點一下右上角 **新增**。
3. 輸入帳本名稱，選擇幣別和需要的設定。
4. 點一下 **儲存**。

一個日常帳本已經可以開始使用。家庭、旅行或工作需要分開統計時，再建立其他帳本。

## 2. 新增帳戶

1. 開啟 **資產**，點一下右上角 **管理**。
2. 點一下 **新增帳戶**。
3. 填寫帳戶名稱、類型、幣別和目前餘額。
4. 儲存後，帳戶會顯示在資產頁面和記錄帳單時的帳戶選擇器中。

{% hint style="warning" %}
**帳戶目前餘額**應填寫開始使用 Daak 當天的實際餘額，不要重複輸入已經包含在餘額中的歷史帳單。餘額屬於帳戶；帳本只用於分類、篩選和共享帳單，不設定餘額。
{% endhint %}

## 3. 記錄第一筆帳單

1. 點一下頁面右下角 **記帳按鈕**。
2. 選擇 **支出**或**收入**。
3. 輸入金額，選擇帳戶、帳本和分類。
4. 點一下數字鍵盤右下角 **儲存**。

## 4. 檢查結果

| 頁面          | 需要檢查的內容         |
| ----------- | --------------- |
| **首頁 > 帳單** | 剛才儲存的帳單內容是否正確   |
| **資產**      | 付款或收款帳戶餘額是否正確變動 |
| **首頁 > 統計** | 收支金額和分類分布是否正確更新 |

{% hint style="success" %}
完成以上設定後，就可以正常記帳；預算、存錢罐、分期和投資等功能可依需要繼續設定。
{% endhint %}


---

# 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://help.daak2.com/zh-tw/kai-shi-shi-yong/quick-start.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.