> 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/workflow.md).

# The recommended workflow

The **Workflow** bar guides you through a shoot in five steps. Each step sets filter and sort order to match and narrows the set for the next one. **⌘1 – ⌘5** jump straight to a step, **⌘]** to the next.

## Review

### 1 · Quality

At the top are the AI reject suggestions (✦), below them all other images by sharpness – blurriest first. Reject with **X** until the images get good; keep false alarms with **U**.

### 2 · AI Top Picks

Check the top pick of each series: **P** = keep (the others become Rejects, marked yellow), **X** = reject. **S** unfolds the stack, **C** compares.

### 3 · Singles

Best AI stars first. At the top accept with **A** or set **1–5**; further down go quickly with **X** or **1**. Auto-advance (**⇪**) helps.

## Check

### 4 · Top Picks

Picks only, best visual impact first. Use **C** to compare duplicates, give the best ones 4–5 stars and set color labels for their purpose.

### 5 · Rejects

Look through all Rejects once – is anything good among them? Bring it back with **U**. Yellow = series reject.

{% hint style="info" %}
You start handing off in the **Export** block at the bottom right – there is no separate step for it. See [Handing off](/cullix/guide/handoff.md).
{% endhint %}


---

# 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/workflow.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.