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

# Overview

This section covers the parts of Patcher you will actually use regularly.

If the docs homepage explains what Patcher is, these pages show how it works in practice.

## The shortest version

Patcher works best when you move through it in this order:

1. browse modules
2. build your collection
3. plan racks
4. capture patches
5. share selected work when it is ready

That is the simplest way to build a workspace worth returning to.

## The main pages

* [Modules](/core-workflows/modules.md)
* [Collection](/core-workflows/collection.md)
* [User Area](/core-workflows/user-area.md)
* [Search and Discovery](/core-workflows/search-and-discovery.md)
* [Racks](/core-workflows/racks.md)
* [Patches](/core-workflows/patches.md)
* [Public Profiles](/core-workflows/public-profiles.md)
* [Account and Privacy](/core-workflows/account-and-privacy.md)

## Where to start

* If you are new, begin with [Quick start](/getting-started/quick-start.md).
* If you already know the product, jump straight to [User Area](/core-workflows/user-area.md) or [Modules](/core-workflows/modules.md).


---

# 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:

```
GET https://docs.patcher.xyz/core-workflows/learn-patcher.xyz.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.