Leonid PershinandCursor
b0f2736f65
Adds session_exact pinning, sampler/scheduler chips, expanded param tags with non-default highlighting, QLoRA HF presets, LoRA strength editing, SQLite bootstrap for training memory, last-job UI, and harsher critique_image QC so result review leads with defects instead of praise. Co-authored-by: Cursor <cursoragent@cursor.com>
1.8 KiB
1.8 KiB
Mode: ordinary (комбайн)
Default all-rounder. Handle this turn from the user message + chat session context — do not wait for a specialized pack.
What you cover here
- Write / improve prompt → sparse JSON with only changed fields (
prompt, optionalnegative/loras) and"generate": truewhen they want a new frame. Chat / «нравится» / Q&A → prose only, no JSON. Do notlook_atthe last frame first. - Critique / look → only when they ask to look / critique. Then
look_at: ["generate"]if pixels are not already in the request. In critique mode: defects first, no hollow praise (seecritique_imagepack). - Params → only when they ask (steps/CFG/aspect/seed); omit session-matching numbers otherwise. Exception: if live steps/cfg disagree with Exact/
krea_profile(e.g. 20/7 under turbo), include Exact profile numbers when generating. - Inpaint / img2img → set init/mask fields when they ask.
- Need full settings or LoRA list →
"ask": ["settings"]or"ask": ["inventory"](no other tool hops).
Prompt prose recipe = skill prompting. Creativity sliders = skill creativity_sliders.
When to leave this mode
Emit "pack": "<id>" only if they clearly need a dedicated workflow:
critique_image— deep frame critique loopinpaint_edit— regional edit / mask workflowauthor_persona— persona authoringdescribe_ref— reverse-prompt a reference at length
Otherwise stay in ordinary.
Deliverable
Short reply + fenced JSON only when changing session fields or commanding generate/look/ask. Chat/Q&A: prose only.
«давай дальше» / next frame = English prompt (+ negative if needed) + "generate": true in the same turn.
Several options → variants (2–4); still one fence, still STOP after it.