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

# Recipes

- [Check the clipboard content](https://docs.maestro.dev/examples/recipes/check-the-clipboard-content.md): Validate OS clipboard by pasting into system search (Spotlight/Android) and asserting expected text with Maestro.
- [Choose images from the gallery](https://docs.maestro.dev/examples/recipes/choose-images-from-the-gallery.md): Select images from the device gallery in automated tests using addMedia.
- [Download and open a file](https://docs.maestro.dev/examples/recipes/download-and-open-a-file.md): Automate file download and open workflows on mobile devices with Maestro.
- [Reset device state (Android)](https://docs.maestro.dev/examples/recipes/reset-device-state-android.md): Automate the Android Files app to purge stale media and downloads. Ensure a clean device state for every test run to prevent false results.
- [Get the last matching element](https://docs.maestro.dev/examples/recipes/get-the-last-matching-element.md): Select the last element in a list using index selectors and JavaScript.
- [Custom scrolling for screen fragments](https://docs.maestro.dev/examples/recipes/custom-scrolling-for-screen-fragments.md): Scroll to elements inside fragments using custom swipe logic when scrollUntilVisible fails on partial screens.
- [Implementing the Page Object Model (POM)](https://docs.maestro.dev/examples/recipes/implementing-the-page-object-model-pom.md): Implement the Page Object Model pattern for maintainable Maestro test suites.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.maestro.dev/examples/recipes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.