> For the complete documentation index, see [llms.txt](https://strydtaiwan.gitbook.io/stryd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://strydtaiwan.gitbook.io/stryd/guide-book/introduction-to-power-zones.md).

# 第二章 - 功率區間(Power Zones)

如果你過去已經接觸過科學化訓練，或許對於心率區間或配速區間並不陌生，它們就是按照你的比賽成績或心率去劃分不同的強度區間，以應用在訓練或比賽上。\
同樣地，功率區間也是根據你的個人能力-臨界功率(Critical Power)去劃分強度區間，每個區間都會對應到不同的能量系統／意義，代表不同的訓練效果。\
\
相對於心率與配速區間，功率區間可以提供你更客觀、更不受外在環境影響的強度依據，無論在平路、上坡或下坡，我們都可以按照特定的功率區間去進行訓練或比賽，不會再發生「追心率」的情況，或是上坡不知道該跑多快的問題。

![如何找出自己的跑步功率區間？](/files/-LtUu0eYMPeYXHZ2mIzi)

**Stryd Zones** 會即時同步您最近的臨界功率(Critical Power)和功率區間(Power Zones)，並告訴您您正在哪個區間中。\
\
最新Stryd App已有[**自動幫你算出臨界功率**](https://strydtaiwan.gitbook.io/stryd/qa/training-plans-and-tips#how-to-up-date-my-critiacl-power)的功能囉，這樣就可以少掉測驗的步驟！\
（自動計算，但是會需要一些時間來抓您的跑步及比賽紀錄。3個月左右，12次以上的跑步及比賽紀錄）

圖片及部分文字出自 -[羅譽寅的鐵人三項研究室](https://uiantraininglog.blogspot.com/)\
\- [如何找出自己的跑步功率區間？](https://uiantraininglog.blogspot.com/2018/07/blog-post.html) 


---

# 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://strydtaiwan.gitbook.io/stryd/guide-book/introduction-to-power-zones.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.