> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pdfm-ug/v27-zh-tw/parallels-desktop-for-mac-27-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/hua-shu-chu-kong-shi-gui-ji-ban-yu-jian-pan/jian-li-xin-de-jian-pan-kuai-su-jian.md).
# 建立新的鍵盤快速鍵
您可按下稱為鍵盤快速鍵的某些複合鍵來快速觸發 Parallels Desktop 中的各種功能。例如，您可按下 Command-Control-F 切換 Windows 到全螢幕 (Full Screen) 模式。您可以使用現有的鍵盤快速鍵 (您可以在「**Parallels Desktop**」>「**偏好設定**」>「**快速鍵**」>「**應用程式快速鍵**」窗格中看到這些快速鍵)，也可以建立自己的快速鍵。
要建立新的鍵盤快速鍵：
1. 記下您想要一個快速鍵執行的命令在 Parallels Desktop 功能表中顯示的名稱。例如，如果您想要建立新的快速鍵以便切換到全螢幕模式，開啟 Parallels Desktop 的「**檢視**」功能表即可看見功能表項目的名稱為「**進入全螢幕**」：
2. 在 macOS 中，選擇「**Apple 功能表**」>「**系統偏好設定**」。
3. 在「系統偏好設定」中，按一下「**鍵盤**」與「**鍵盤快速鍵**」。
4. 在側邊欄中選定「**應用程式快速鍵**」並按一下「新增」按鈕 。
5. 如果你想要建立只適用於 Parallels Desktop 的新快速鍵，可從「**應用程式**」功能表選擇 Parallels Desktop。如果您保留選定「**所有應用程式**」，快速鍵將用於任何有相同命令名稱且且當前處於活躍狀態的應用程式。
6. 從第 1 步輸入功能表項目目名稱。\
\
**重要：**您輸入的命令名稱必須與在 Parallels Desktop 功能表中顯示的完全一樣，否則無法使用新的快速鍵。
7. 在「**鍵盤快速鍵**」欄位，按下您想要觸發功能的按鍵組合。
{% hint style="info" %}
**附註：**您必須根據 Parallels Desktop 的狀態為在功能表中變更的命令建立個別的快速鍵，例如「**進入全螢幕**」與「**結束全螢幕**」。
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.parallels.com/landing/pdfm-ug/v27-zh-tw/parallels-desktop-for-mac-27-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/hua-shu-chu-kong-shi-gui-ji-ban-yu-jian-pan/jian-li-xin-de-jian-pan-kuai-su-jian.md?ask=&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.
