> For the complete documentation index, see [llms.txt](https://guide.strikepack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.strikepack.com/horizon/strikepack-horizon-app-guide/shooter-studio-guide/1-feeling-lost.md).
# 1 - Feeling Lost?
Feeling Lost?
STRIKEPACK HORIZON™ Gaming Adapters
We understand that Shooter Studio has a completely new User Interface, which may feel a little intimidating at first.
We recommend following the next pages in this guide. After creating your **Game Profile**, follow the in-app **Initial Setup**, followed by the in-app **Getting Started** onboarding tasks. These will give you a basic understanding of where the most important settings are and help you configure Shooter Studio to work well with your game. The app will also keep track of your progress and mark each task as you complete it.
Once you’ve completed the onboarding, you should have the basics covered, including:
* Your in-game **Controller Layout** settings matched.
* Your **Action Buttons (Paddles)** mapped.
* An understanding of how to set up your **Accessibility Configuration Macros**.
* Your **Loadout** configured, including **Slot Layout** and **Visible Slots**, to work well with your game.
---
# 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://guide.strikepack.com/horizon/strikepack-horizon-app-guide/shooter-studio-guide/1-feeling-lost.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.
