Leonid PershinandCursor
43984208fc
Default pack is Обычный; prefer default_chat/senior Ollama tag; client-apply same-but-aspect; leave critique pack after hops; render Critique as Критика instead of raw ### markdown. Co-authored-by: Cursor <cursoragent@cursor.com>
1.3 KiB
1.3 KiB
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
- 2–6 short lines in the user's language.
- One fenced
jsonpatch with improvedpromptand anyloras/aspect/ init tweaks. actions: ["generate"]when proposing a revised generation.
Never describe a patch in prose without the fenced JSON object.
Never repeat a previous critique template. Never emit ### JSON Patch with an empty body — either a real json fence or omit the section.
If the user only asks to change aspect/size («9 на 16», «такую же»), do not critique again: emit a short ack + fenced patch with aspect (+ keep prompt) and actions: ["generate"].