> For the complete documentation index, see [llms.txt](https://aaronia.teigenrf.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aaronia.teigenrf.org/rtsa-suite-pro-guide-for-wi-fi-pros.md).
# RTSA-Suite Pro Guide for Wi-Fi Pros
## Introduction
Welcome to my guide on using the Aaronia RTSA-Pro Software.
In this guide, I will walk you through how the factory missions work, how to modify them, and how to create your own missions from scratch. I will also share some custom missions that will be updated regularly.
The software can be a bit difficult to use, especially for Wi-Fi professionals who are accustomed to tools that handle everything automatically without offering customization options. You don’t need to own a Spectran V6 to use the software, as I will share files on this GitBook that will allow you to learn the software without the hardware. :tada:
## Quick links
{% content-ref url="/pages/aEBA6Q3Z9rZWwpgfNMlh" %}
[About RTSA-Suite Pro](/overview/about-rtsa-suite-pro.md)
{% endcontent-ref %}
{% content-ref url="/pages/7qBMH9lRc0urO3emPUGI" %}
[Spectran V6 Plus and Eco](/overview/spectran-v6-plus-and-eco.md)
{% endcontent-ref %}
{% content-ref url="/pages/NU4HJT2SevvLxJZeguXe" %}
[Protect your RF input and outputs](/overview/protect-your-rf-input-and-outputs.md)
{% endcontent-ref %}
---
# 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://aaronia.teigenrf.org/rtsa-suite-pro-guide-for-wi-fi-pros.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.
