> For the complete documentation index, see [llms.txt](https://doc.qrspace.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.qrspace.dev/zhi-shi-zheng-li-yu-zi-liao-shou-ji/mindmaps.md).

# 心智圖分析

心智圖（Mindmaps）是口袋瀏覽器內建的結構化邏輯梳理工具，用於將雜亂的網頁知識轉化為層次分明的節點樹。

***

## 為什麼需要心智圖

傳統書籤或單頁筆記只能以線性清單呈現資料，難以表達多個概念或多篇文檔之間的上下層級、分支因果與架構關聯。

心智圖頁籤讓使用者在閱讀多篇技術規範、競品分析或調查文獻時，能夠在側欄即時拉出視覺化分支。

***

## 核心操作與特性

### 1. 節點建立與階層管理

* 支援快速新增父節點、子節點與同級節點。
* 支援節點內容自由編輯、背景標色與折疊展開。
* 可透過滑鼠拖曳調整分支層級與排列順序。

### 2. 整合網頁物件

心智圖中的每個節點均可掛載網頁物件：

* **網址卡片**：將正在瀏覽的網址直接拖入心智圖節點，點擊可快速跳轉。
* **摘錄文字**：將網頁中選取的文字一鍵轉為分支說明。
* **截圖預覽**：支援將網頁局部截圖嵌入節點內部作為視覺對照。

### 3. 持久化儲存與匯出

* 心智圖繪製進度本地自動即時存檔。
* 支援將心智圖架構匯出為標準 Markdown 階層或圖片格式，方便後續轉移至其他文檔系統。


---

# 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://doc.qrspace.dev/zhi-shi-zheng-li-yu-zi-liao-shou-ji/mindmaps.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.
