> For the complete documentation index, see [llms.txt](https://cullshot.gitbook.io/cullix/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cullshot.gitbook.io/cullix/guide/ipad.md).

# Using Cullshot on iPad

Cullshot runs on iPad with the same features as on the Mac – operated by touch.

## Gestures

* **Tap** selects an image, **double-tap** opens it large.
* **Pinch** with two fingers to zoom continuously up to 200%.
* **Swipe right** = Pick (green), **swipe left** = Reject (red). The image stays in place and the action slides in from the edge; once you pass a certain distance it triggers and you move on.
* **Select** (icon in the top bar) turns on multi-selection: tapping adds to the selection.
* The **context menu** on thumbnails offers more actions.

## Rating column

With the inspector hidden, a narrow rating column appears at the edge: Pick/Reject/None, stars (numbered) and color labels by tap.

## Photo library

On iPad you can open the **Photos library** like a folder – without copying. Ratings are saved in a file of the app itself instead of XMP. "Save to Library" creates new photos; Picks become Favorites.

## Keyboard

With a keyboard the [keyboard shortcuts](/cullix/reference/keyboard-shortcuts.md) apply; on iPad they also appear in the **Rate** and **View** menus.


---

# 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://cullshot.gitbook.io/cullix/guide/ipad.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.