> For the complete documentation index, see [llms.txt](https://morphic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://morphic.com/docs/zh/getting-started/assets.md).

# 素材

你上传或生成的所有内容存放在哪里，以及你的团队如何从任意文件访问它。

你在 Morphic 中上传或生成的所有内容都会保存在你的资源库中。它在整个组织内共享，并可在每个文件中使用，因此你在某处添加的任何内容都会在所有地方显示。

随时可在以下位置打开你的资源库： [studio.morphic.com/library](https://studio.morphic.com/library)，或从 `素材` 左侧边栏中的“标签”选项卡。你可以从三个位置使用资源：

* 该 [`素材`](https://studio.morphic.com/library) 仪表板中的页面。
* 该 `素材` 任何文件内的面板。
* [Copilot 聊天](https://studio.morphic.com/chat).

本节涵盖：

* [上传资源](/docs/zh/getting-started/assets/upload-assets.md)：将你自己的文件导入 Morphic。
* [标签与收藏](/docs/zh/getting-started/assets/tags-and-favorites.md)：对资源进行标记并列入收藏，以便更容易查找。
* [管理多个资源](/docs/zh/getting-started/assets/manage-multiple-assets.md)：选择多个资源并一次性对它们执行操作。

***

如果您遇到任何问题或有任何疑问，欢迎随时联系我们。我们很乐意为您提供帮助。请写信至 [**support@morphic.com**](mailto:support@morphic.com)**.**


---

# 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://morphic.com/docs/zh/getting-started/assets.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.