> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/shade-academy/shade-academy-zh/gong-zuo-qu-he-qu-dong-qi/folder-templates.md).

# 文件夹模板

用于在你反复使用相同文件夹结构时的文件夹模板。这在每个新建项目都采用给定文件夹结构的项目中最为常见。目前，文件夹模板只支持固定的文件夹结构，不能同时包含文件。一个模板最多可包含 100 个文件夹。

### 创建文件夹模板

1. 在 Drive 中，在父文件夹内创建所需的文件夹结构，或者导航到父文件夹内已存在的文件夹结构
2. 右键单击包含所需文件夹结构的父文件夹
3. 选择 **将文件夹保存为模板**
4. 选择一个图标并为你的模板命名
5. 添加可选描述，以便他人了解该模板的用途
6. 启用 **保存到工作区** 如果该模板应可在工作区内的任何/所有 Drive 中使用。此选项仅适用于工作区管理员。
7. 点击 **创建模板** 以保存

### 使用文件夹模板

在 Drive 中

1. 在文件夹层级中导航到该文件夹应放置的位置
2. 右键单击并悬停在 **创建新文件夹**
3. 从弹出菜单中选择你的模板

### 管理现有文件夹模板

删除模板会立即生效，不会有确认步骤。

#### Drive 级模板

1. 右键单击一个 Drive
2. 点击 **查看文件夹模板**
3. 重命名或删除你的 Drive 级文件夹模板

#### 工作区级模板

1. 前往 设置 > 常规 > 文件夹模板
2. 点击 **管理模板**
3. 重命名或删除你的工作区级文件夹模板


---

# 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://academy.shade.inc/shade-academy/shade-academy-zh/gong-zuo-qu-he-qu-dong-qi/folder-templates.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.