# Guides (/docs/guides)

---
title: Guides
description: One job each, start to finish. Where the reference pages tell you what a thing does, these build something with it and leave you a working result.
kind: guide
package: questpie
---

Each page here answers one question by building the answer. They assume you have
an app running, so if you do not, start with
[your first app](/docs/learn/first-app).

| Guide                                                      | The question it answers                                                 |
| ---------------------------------------------------------- | ----------------------------------------------------------------------- |
| [Connect an AI agent](/docs/guides/connect-an-agent)       | How does an agent call my app under the rules I already wrote?          |
| [Collaborative documents](/docs/guides/collaborative-docs) | How do two people edit the same article without overwriting each other? |
| [Trace a slow request](/docs/guides/debug-a-slow-request)  | Which part of this request is actually slow?                            |
| [Multi-tenancy](/docs/guides/multi-tenancy)                | How do I serve many tenants from one app?                               |
| [Build a plugin](/docs/guides/build-a-plugin)              | How do I teach QUESTPIE a new file convention of my own?                |

## Guides against reference

A guide gives you one path that works, not the whole surface. When you want
every option instead of one worked example, go to the group pages.
[Schema](/docs/schema) covers what you declare. [Code](/docs/code) covers what
you write beside it.