Resolving picks
Picking is half of it. The other half is what your agent does with the picks.
The loop
- Pick the elements you want changed.
Alt+Q, then click each one. - Annotate them: click a badge and write what should happen. "make this full width on mobile", "this heading is too tight", "same padding as the card above".
- Say it once:
resolve the picks.
The agent reads .quello/picks.json, works through every entry that has a note in id order,
locates each element's source, and carries the note out against it.
Picks without a note are just bookmarks — the agent leaves them alone unless you say otherwise.
What the agent is told
On first run quello writes a fenced section into your agent file. It explains the shape of a pick and what resolving means:
<!-- quello:start -->
## quello — visual element picks
When the user references `PICK <n>` (or says "quello"), read `.quello/picks.json` and resolve the
entry whose `id` is `<n>` to locate the source element/component. Each entry carries:
- `note` — **an instruction written by the user for you**, when present
- `selector` / `domPath` — where the element sits in the DOM
- ...
### "Resolve the picks"
When the user asks you to resolve the picks, read `.quello/picks.json` and work through every entry
that has a `note`, in `id` order:
1. Locate the element's source from `framework.file` / `framework.line` …
2. Carry out that entry's `note` as an instruction scoped to that element.
3. Move on to the next one.
<!-- quello:end -->
The markers mean the section is written once and never rewritten, so anything you add around it stays put.
Talking to the agent
You do not have to use the phrase. All of these work, because the agent has the file:
- "make PICK 2 sticky"
- "PICK 1 and PICK 4 should share the same spacing"
- "quello" — the section tells the agent this refers to the picks
- "resolve the picks" — work through all the annotated ones
When there is no repository
If your agent has no access to the codebase — a chat in a browser tab — turn on Copy on pick and paste instead. The clipboard payload uses the same JSON shape as the file.
A note on trust
Notes travel through a file, which is a weaker channel than talking to your agent directly. The instructions quello writes tell the agent to treat a note as a request from you, and to check before acting on one that asks for something unrelated to the element it is attached to.