Leonid PershinandCursor
3380206c6a
Server inventory and streaming chat, auto-apply/generate with Interrupt, Civitai search cards (Confirm-only download), plus Init/Mask wiring and inpaint_edit pack. Co-authored-by: Cursor <cursoragent@cursor.com>
20 lines
1005 B
Markdown
20 lines
1005 B
Markdown
# Mode: write_prompt
|
|
|
|
Goal: craft or improve a **Krea 2** prompt that will generate well on Turbo.
|
|
|
|
## How to write the prompt
|
|
|
|
- Natural language + concrete visual details (subject, lighting, lens/mood, composition).
|
|
- Put **LoRA trigger phrases** near the subject they affect; do not dump unrelated tags.
|
|
- Prefer clarity over keyword stuffing. Krea 2 understands sentences.
|
|
- If the user wants a style covered by an available LoRA, enable that LoRA and weave its triggers in.
|
|
- Keep Turbo defaults unless the user asks otherwise (steps 8, cfg 1).
|
|
- If a needed LoRA is missing from `available_loras`, use `actions: ["search_civitai"]` with a clear `search_query` (and prefer Krea base).
|
|
|
|
## Deliverable
|
|
|
|
- Explain briefly what you changed.
|
|
- Emit a JSON patch with at least `prompt`, and `loras` when relevant.
|
|
- Include `actions: ["generate"]` when the user wants to see a new image.
|
|
- Include `width`/`height` only if aspect should change for the scene (e.g. portrait → taller).
|