> For the complete documentation index, see [llms.txt](https://whitepaper.vitalveda.fit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.vitalveda.fit/ecosystem-and-key-products/vitalveda-training-app-design.md).

# VitalVeda Training App Design

The VitalVEDA app is to keep rolling with various gym workouts which are adopted in this app.

Having a workout plan provides you with a structure so that you aren't wondering what to do next or just reverting back to the ol' cardio equipment - our app tells you which exercise to do, how many reps, how many sets, etc. - the activity screen can help you keep track of Personal Data and progress, It is easy to add parameters and change with a progress chart or compare visual metrics.

Watch the short demo Video as how VitalVEDA Application works:

{% embed url="<https://www.youtube.com/watch?v=xjlrqhDsmb4>" %}


---

# 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://whitepaper.vitalveda.fit/ecosystem-and-key-products/vitalveda-training-app-design.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.