> For the complete documentation index, see [llms.txt](https://docs.arcadiaos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcadiaos.ai/platform-aspects.md).

# Platform Aspects

- [Agent-Powered Asset Development](https://docs.arcadiaos.ai/platform-aspects/quickstart.md): Utilizing agents to call on various protocols to compile gaming assets for immediate developer use.
- [Agent-Driven Game Prototyping](https://docs.arcadiaos.ai/platform-aspects/publish-your-docs.md): With fast paced trends changing, and users wanting more now quickly, agents shall now enable developers to ship products quickly.
- [Seamless Deployment](https://docs.arcadiaos.ai/platform-aspects/seamless-deployment.md): Prompt to product has never been easier, and creative freedom shall now exist with the help of agents.
- [Adaptive Agent Evolution](https://docs.arcadiaos.ai/platform-aspects/adaptive-agent-evolution.md): Agents must learn and understand common behaviors and trends gradually improving upon itself over time.
- [Generative Templates](https://docs.arcadiaos.ai/platform-aspects/generative-templates.md): Pre-designed templates, for nearly instant prototyping, web3 friendly, and web2 viable.
- [Web3 Contract Generation](https://docs.arcadiaos.ai/platform-aspects/web3-contract-generation.md): Enabling agents to apply web3 generated contracts to prototypes, enabling users to develop game-fi related products.


---

# 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.arcadiaos.ai/platform-aspects.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.