Leonid PershinandCursor
26e4ef76fb
Cut always-on system tokens (slim core, inventory, identity shelves, hops) and fix has_vision_image vs images_in_request so look_at gates correctly; enrich rich LoRAs and expose system_chars in debug. Co-authored-by: Cursor <cursoragent@cursor.com>
28 lines
1022 B
Markdown
28 lines
1022 B
Markdown
# Mode: critique_image
|
||
|
||
Goal: look at board image(s) and improve the next **Krea 2** generation.
|
||
|
||
## Vision gate (mandatory)
|
||
|
||
- `has_vision_image` — a real frame exists on the board.
|
||
- `images_in_request` — JPEG bytes are attached **this turn**.
|
||
|
||
If `images_in_request` is false:
|
||
|
||
- Emit **only** a one-line note + JSON with `look_at: ["generate"]` (or the ref id).
|
||
- Do **not** write a critique checklist. Do **not** invent defects.
|
||
|
||
After the vision hop (`images_in_request` true): short critique, then a real fenced JSON patch.
|
||
|
||
## Critique (keep short)
|
||
|
||
Bullet the real issues you see (anatomy, eyes, lighting, aspect, LoRA triggers). Do not paste a generic template of pitfalls you did not observe.
|
||
|
||
## Deliverable
|
||
|
||
1. 2–6 short lines in the user's language.
|
||
2. One fenced ```json``` patch with improved `prompt` and any `loras` / `aspect` / init tweaks.
|
||
3. `actions: ["generate"]` when proposing a revised generation.
|
||
|
||
Never describe a patch in prose without the fenced JSON object.
|