> 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/fr/section-04-aero.md).

# Section 04 : Aero

- [Bases de l'aéro](https://docs.velogicfit.com/fr/section-04-aero/aero-basics.md): Principes fondamentaux de l'aérodynamique en cyclisme, y compris les composantes de la force de traînée et leur impact sur l'optimisation des performances.
- [Ce que vous pouvez faire (et ne pas faire) avec Aero dans Velogic Studio](https://docs.velogicfit.com/fr/section-04-aero/aero-capabilities.md): Comprendre les capacités et les limites du module Aero de Velogic Studio pour la mesure de la surface frontale et l'analyse aérodynamique.
- [Comment utiliser Aero dans Velogic Studio](https://docs.velogicfit.com/fr/section-04-aero/how-to-use-aero.md): Guide complet pour configurer et utiliser le module Aero avec des caméras frontales pour l'analyse aérodynamique
- [Analyse approfondie : progression frontale](https://docs.velogicfit.com/fr/section-04-aero/frontal-progression.md): Fonctionnalité avancée permettant de visualiser les changements de surface frontale tout au long d'une séance d'ajustement, montrant les améliorations de position pour les rapports client.
- [Test de durabilité](https://docs.velogicfit.com/fr/section-04-aero/sustainability-test.md): Découvrez comment utiliser la fonction de test de durabilité à capture automatique pour évaluer combien de temps les cyclistes peuvent maintenir leurs positions


---

# 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/fr/section-04-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.