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

# 第 04 节：Aero

- [Aero 基础知识](https://docs.velogicfit.com/zh/di-04-jie-aero/aero-basics.md): 骑行空气动力学的基本原理，包括阻力的组成部分及其对性能优化的影响。
- [在 Velogic Studio 中能做什么以及不能做什么（Aero）](https://docs.velogicfit.com/zh/di-04-jie-aero/aero-capabilities.md): 了解 Velogic Studio 的 Aero 模块在正面面积测量和空气动力学分析方面的能力与局限。
- [如何在 Velogic Studio 中使用 Aero](https://docs.velogicfit.com/zh/di-04-jie-aero/how-to-use-aero.md): 设置并使用带有前置摄像头的 Aero 模块进行空气动力学分析的完整指南
- [深入解析：正面进展](https://docs.velogicfit.com/zh/di-04-jie-aero/frontal-progression.md): 用于可视化一次拟合过程中正面面积变化的高级功能，可展示位置改进，便于客户报告。
- [耐力测试](https://docs.velogicfit.com/zh/di-04-jie-aero/sustainability-test.md): 了解如何使用自动采集的耐力测试功能来评估骑手能维持姿势多久


---

# 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.velogicfit.com/zh/di-04-jie-aero.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.
