> For the complete documentation index, see [llms.txt](https://ray-evolv.gitbook.io/ray_evolv-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ray-evolv.gitbook.io/ray_evolv-docs/scenes.md).

# 场景体验与教程

每篇围绕一件完整事情展开：你想做什么，怎样告诉 Nora，过程中怎样补充和确认，最后看见什么结果。

这些场景也对应后续 B 站详细功能介绍的内容单元。当前图文可独立阅读，视频完成后会嵌入相应场景页；无需等待视频才能开始使用。

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>一句话整理账户和资金</strong></td><td>从建档、入金到调整分配，让资金归属清楚。</td><td><a href="/ray_evolv-docs/scenes/scene-money.md">一句话整理账户和资金</a></td></tr><tr><td><strong>把交易文字或截图交给 Nora</strong></td><td>从原始材料得到可核对、可保存的交易记录。</td><td><a href="/ray_evolv-docs/scenes/scene-trades.md">把交易文字或截图交给 Nora</a></td></tr><tr><td><strong>用对话安排后续定投</strong></td><td>说清未来安排，再查看、暂停或恢复。</td><td><a href="/ray_evolv-docs/scenes/scene-plan.md">用对话安排后续定投</a></td></tr><tr><td><strong>从一个问题到一份报告</strong></td><td>在对话中明确方向、修改大纲并跟踪研究。</td><td><a href="/ray_evolv-docs/scenes/scene-research.md">从一个问题到一份报告</a></td></tr><tr><td><strong>与 Nora 一起读报告</strong></td><td>围绕一句结论、一个图表或一条依据继续追问。</td><td><a href="/ray_evolv-docs/scenes/scene-reading.md">与 Nora 一起读报告</a></td></tr><tr><td><strong>保存认识并在下次用上</strong></td><td>保留有用内容，下一次用不同说法也能查找。</td><td><a href="/ray_evolv-docs/scenes/scene-knowledge.md">保存认识并在下次用上</a></td></tr><tr><td><strong>在桌面看资料时继续讨论</strong></td><td>把眼前材料与已有知识联系起来。</td><td><a href="/ray_evolv-docs/scenes/scene-desktop.md">在桌面看资料时继续讨论</a></td></tr><tr><td><strong>公司与家庭电脑接续使用</strong></td><td>通过网盘同步，让已提交的资料到另一台电脑。</td><td><a href="/ray_evolv-docs/scenes/scene-sync.md">公司与家庭电脑接续使用</a></td></tr></tbody></table>


---

# 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://ray-evolv.gitbook.io/ray_evolv-docs/scenes.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.
