@kolbo/kolbo-code-linux-x64-baseline-musl 2.3.0 → 2.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kolbo/kolbo-code-linux-x64-baseline-musl",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "os": [
     "linux"
   ],

package/skills/kolbo/SKILL.md

@@ -1,32 +1,22 @@
 ---
-version: 0.4.0
+version: 0.5.0
 name: kolbo
 description: |
-  Generate, edit, or analyze creative media via the Kolbo AI MCP server.
-  Covers images (GPT Image 2, Nano Banana, Flux, ...), video (Seedance 2,
-  Veo 3.1, Kling, Hailuo, ...), music (Suno), TTS (ElevenLabs), 3D,
-  transcription, Visual DNA (character consistency), Marketing Studio
-  (UGC + DTC ads + product photoshoot + marketplace cards),
-  Creative Director (multi-scene batches), HTML artifact publishing
-  (presentations, landing pages, dashboards), and the App Builder.
-
-  Use when: "generate", "create", "make me a", "edit", "animate",
-  "transcribe", "Visual DNA", "the same character", "UGC ad",
-  "TikTok / Reels / Shorts", "unboxing", "product review", "TV spot",
-  "Pinterest pin", "product photo", "lifestyle shot", "hero banner",
-  "ad pack", "social carousel", "virtual try-on", "Amazon listing",
-  "marketplace cards", "A+ content", "build a presentation/slide deck",
-  "landing page", "dashboard / widget / game", "music / song / jingle",
-  "TTS / voice", "sound effect", "3D model", "build me an app".
-
-  Chain: train Visual DNA → use vdna_id in any DNA-aware tool;
-  research-first → persist brand kit (.kolbo/brand-kits/) → DTC ads /
-  product photoshoot / marketplace cards; generate frames (Creative
-  Director) → animate each frame (generate_video_from_image).
-
-  NOT for: video editing / FFmpeg work (use video-production skill),
-  motion graphics (use remotion-best-practices skill), code editing,
-  general chat outside media generation.
+  Generate, edit, or analyze creative media via the Kolbo AI MCP server:
+  images (GPT Image, Nano Banana, Flux), video (Seedance, Veo, Kling, Hailuo),
+  music (Suno), TTS (ElevenLabs), 3D, transcription, Visual DNA (character
+  consistency), Marketing Studio (UGC + DTC ads + product photoshoot +
+  marketplace cards), Creative Director (multi-scene batches), HTML artifact
+  publishing (presentations, landing pages, dashboards), and the App Builder.
+
+  Use when the user wants to generate, create, make, edit, animate, or
+  transcribe media: images, video, music, voice/TTS, sound effects, 3D models,
+  UGC or TV-spot ads, product / lifestyle / hero shots, Amazon or marketplace
+  listings, presentations, landing pages, dashboards, or 'build me an app';
+  or to reuse a character or brand (Visual DNA, brand kits).
+
+  NOT for: video editing / FFmpeg (use video-production), motion graphics
+  (use remotion-best-practices), code editing, or general chat.
 argument-hint: "[prompt-or-command] [--model <name>] [--image <path>] [--video <path>]"
 allowed-tools: Bash, Read, Write, Edit
 ---
@@ -49,6 +39,25 @@ Once per conversation, before any other Kolbo tool call:
 
 If the user is on a whitelabel build (`sapir`, etc.), they must use their branded command — not `kolbo`. See `references/workflows/troubleshooting.md`.
 
+## 🎬 Confirm the Creative Brief BEFORE Generating (CRITICAL — read first)
+
+Never fire a paid generation the moment the user says "make X". First **present the brief back as a confirmation the user can change** — this is the single most important interaction. It gives the user control over what gets created and what it costs, instead of silently spending credits on defaults.
+
+**Before ANY paid image / video / music / speech / 3D generation**, unless the user has *explicitly* dictated every key parameter in this message, ask ONE labeled question (the UI renders it as an options card) confirming:
+
+- **Model** — your recommended pick as the default option, plus 1–2 alternatives (with their credit cost).
+- **Aspect ratio** — e.g. `1:1 / 9:16 / 16:9` (offer the sensible default first).
+- **Count** — how many (1 / 4 / …).
+- **Resolution / quality / duration** — where the model supports it.
+- **Creative direction** — style / mood / scene, when the user was vague ("4 cats" → offer style options: photoreal / illustrated / cinematic / surprise-me).
+- **Credit cost** — state the total (`✦ N credits`) right in the question so cost is never a surprise.
+
+Then generate **only** with the confirmed parameters. If the user changes an option, use the change. This mirrors the approval-card flow: propose → let them adjust → confirm → generate.
+
+**Only skip the brief confirmation when** the user's message already pins model + aspect + count + creative direction (e.g. "generate 4 photoreal tabby cats, 1:1, z-image/turbo") — then just state the cost one-liner and fire. A low credit cost is **not** a reason to skip: cheap ≠ no-confirmation. What matters is whether the user actually chose the parameters.
+
+For multi-scene / batch work this pairs with `generate_creative_director` (see below) — still confirm the brief first.
+
 ## Routing Index — Read These Files on Demand
 
 | If the user wants to… | Read first |
@@ -153,8 +162,8 @@ Model types for `list_models`: `text_to_img`, `image_editing`, `text_to_video`,
 
 Full tables + formulas in `references/workflows/cost-and-validation.md`. Quick rules:
 
-- **Skip cost confirmation** when the user already specified model + count + duration, OR when a single generation costs < 5 credits.
-- **Required cost confirmation** otherwise: one-line summary, suggest cheaper alternative if available, wait for confirm.
+- **Skip the brief/cost confirmation ONLY** when the user's message already pins model + count + aspect + creative direction (see "Confirm the Creative Brief" above). Low cost alone is **not** a reason to skip — cheap generations still get the one labeled confirmation unless the user chose the parameters.
+- **Otherwise confirm** via the labeled-question card: the parameters + the credit cost, suggest a cheaper alternative if one fits, wait for the user's pick. Never fire on defaults the user didn't choose.
 - **Batch totalling 100+ credits**: run `check_credits` first.
 - **Quote real cost**: after firing, log `credits_used` (from the tool result) to `.kolbo/production.md` — never `base × count`.
 

package/skills/kolbo/VERSION

@@ -1 +1 @@
-0.4.0
+0.5.0

package/skills/kolbo/references/models/seedance.md

@@ -13,18 +13,18 @@ Load this file when the user wants a **Seedance 2 / Seedance 2.0** (ByteDance) v
 
 - **First line ALWAYS declares shot structure**: total duration, shot count, aspect ratio. Example: `Total: 15s / 6 shots / 16:9`. Put it at the BOTTOM of the prompt too.
 - **Order inside each shot**: Subject → Action → Camera → Style → Constraints → (Audio/SFX if relevant).
-- **Prompt length**: aim for ~120–280 words TOTAL across all shots combined (not per shot). Shorter than ~120 words = random output. Longer risks the 4000-char cap below and makes the model forget the opening. For 6-shot prompts, keep each shot 1–2 tight sentences.
+- **Prompt length**: aim for ~120–280 words TOTAL across all shots combined (not per shot). Shorter than ~120 words = random output. Longer risks the 8000-char cap below and makes the model forget the opening. For 6-shot prompts, keep each shot 1–2 tight sentences.
 - **Character lock**: if a character recurs, open with `same character throughout all shots` to stop identity drift.
 - **Max 3 shots per single-shot prompt; max 6 shots in a multi-shot montage.** More causes drift.
 - **Always describe at least one camera movement per shot.**
 - **Tell Seedance what the camera is NOT doing** (e.g. `no cuts, no zoom, natural head movement`) — this is what locks POV.
 - **Final prompt is always English**, wrapped in a copy-ready code block. Detect intent in any language and reply in the user's language, but the prompt itself is English.
-- **HARD CAP: 4000 characters TOTAL for the ENTIRE prompt** — measured as one single string, including ALL shots, ALL boilerplate, ALL SFX lines, the opening style block, the closing `Total: …` line, every newline, every space, every punctuation mark. This is non-negotiable.
-  - Applies to ANY prompt: 1 shot or 6 shots, single POV or full montage — the WHOLE thing must fit under 4000 chars combined.
-  - It is NOT 4000 chars per shot. It is 4000 chars per prompt.
-  - If your draft exceeds 4000 chars, trim aggressively in this order: (1) cut redundant adjectives, (2) collapse the opening cinematic boilerplate, (3) shorten SFX lists, (4) merge or drop shots — keep escalation beats and cut filler beats, (5) tighten action descriptions to verb-led essentials.
+- **HARD CAP: 8000 characters TOTAL for the ENTIRE prompt** — measured as one single string, including ALL shots, ALL boilerplate, ALL SFX lines, the opening style block, the closing `Total: …` line, every newline, every space, every punctuation mark. This is non-negotiable.
+  - Applies to ANY prompt: 1 shot or 6 shots, single POV or full montage — the WHOLE thing must fit under 8000 chars combined.
+  - It is NOT 8000 chars per shot. It is 8000 chars per prompt.
+  - If your draft exceeds 8000 chars, trim aggressively in this order: (1) cut redundant adjectives, (2) collapse the opening cinematic boilerplate, (3) shorten SFX lists, (4) merge or drop shots — keep escalation beats and cut filler beats, (5) tighten action descriptions to verb-led essentials.
   - **Never** split into multiple prompts, multiple code blocks, or "part 1 / part 2" to evade the cap.
-  - Before outputting, internally count the characters of the final prompt as a single string. If > 4000, rewrite tighter and re-count. Repeat until ≤ 4000. Only then show the user.
+  - Before outputting, internally count the characters of the final prompt as a single string. If > 8000, rewrite tighter and re-count. Repeat until ≤ 8000. Only then show the user.
 
 ## The 5 Formats
 
@@ -83,7 +83,7 @@ When the user uploads a 3×3 grid image and asks for Seedance prompts, switch to
 - Final prompt(s) ALWAYS in a fenced code block ready to paste into the Seedance `prompt` field (or pass as `prompt` on `generate_video` / `generate_elements`).
 - After the code block, give a 1-line "why this works" note (camera/escalation/physics choice).
 - If user asked in any language other than English, write your explanation in their language but keep the prompt itself English.
-- **Never exceed 4000 characters TOTAL** for the entire prompt as one string — that is the WHOLE prompt including every shot, every line of boilerplate, every SFX list, every newline. NOT 4000 per shot — 4000 for the prompt as one combined unit. Count before output. If over, rewrite tighter (cut adjectives, collapse boilerplate, merge or drop shots). NEVER split into multiple prompts / multiple code blocks / "part 1 / part 2" to work around the limit.
+- **Never exceed 8000 characters TOTAL** for the entire prompt as one string — that is the WHOLE prompt including every shot, every line of boilerplate, every SFX list, every newline. NOT 8000 per shot — 8000 for the prompt as one combined unit. Count before output. If over, rewrite tighter (cut adjectives, collapse boilerplate, merge or drop shots). NEVER split into multiple prompts / multiple code blocks / "part 1 / part 2" to work around the limit.
 
 ## Seedance + Visual DNA / References
 

package/skills/kolbo/references/workflows/marketing-studio.md

@@ -119,6 +119,68 @@ For ads that feature a specific product:
 
 If the user gives a **product URL** instead of a photo, see `workflows/research-first.md` — scrape, extract images, re-host via `upload_media`, persist as a brand kit at `.kolbo/brand-kits/<slug>.md`.
 
+<!-- SKILL-ONLY: no server parity — UGC output routes through the creative-director / veo / seedance enhancers, so any server-side rule lives in those parity files, not here. -->
+
+## Multi-Slot Board Method (structured shot specs + character consistency)
+
+For any multi-shot UGC / review / how-to where the SAME presenter must stay identical across shots, compose the prompt as explicit **slots** and lock identity with a **board-first** pass. This is a prompt-only convention — no special MCP mode; it uses `generate_image` (board) + `generate_elements` / `generate_video_from_image` (per-slot animate) that already exist.
+
+### 1. Structured input slots
+
+Define each shot as one row. Fill every column before generating — blanks are where identity/quality drift creeps in.
+
+| Slot | Arc role | POV / framing | Presenter action | Product visibility | Aspect | Audio |
+|---|---|---|---|:-:|:-:|:-:|
+| 1 | hook | selfie arm, chest-up, eye contact | states the problem / grabs attention | held up to camera | 9:16 | monologue seg 1 |
+| 2 | demo | slightly wider, hands in frame | uses / demonstrates the product | in active use | 9:16 | monologue seg 2 |
+| 3 | payoff | back to selfie framing | reaction + soft CTA | resting in hand / on surface | 9:16 | monologue seg 3 |
+
+Scale to 2–6 slots. Keep `hook → demo → payoff` as the minimum arc; add `tension` / `proof` slots between demo and payoff for longer reviews.
+
+### 2. Rendering rules (hard invariants — apply to EVERY slot)
+
+- One aspect ratio across all slots (UGC = `9:16`). Never mix.
+- **No on-image text**, captions, subtitles, watermarks, or lower-thirds (users add captions in post).
+- **Identity lock**: same presenter, same wardrobe, same lighting environment across all slots — open the prompt with `same character throughout all shots`.
+- Hands and product must read cleanly — no deformed hands, no floating / clipping product, product logo legible when held.
+- Phone-shot aesthetic (handheld sway, window/screen key) unless the mode is polished (`tv_spot`, `product_showcase`).
+
+### 3. Board-first consistency (the grid technique)
+
+Before animating, generate ONE composite board image that locks the presenter's identity, then animate each panel:
+
+1. `generate_image` a labeled N-panel grid (2×2 or 1×N) of the presenter across the slot poses — front hook pose, hands-on-product demo pose, reaction pose — locked to `visual_dna_ids` (the presenter's Visual DNA). Aspect `16:9` for the board sheet.
+2. Treat that board image's CDN URL as the **`board_media_id`** — the single source of truth for identity.
+3. Animate each slot with `generate_video_from_image` / `generate_elements`, passing the board panel (and product) as `reference_images` and tagging `@image1`, so every clip inherits the same face/wardrobe.
+
+This mirrors how the best UGC pipelines keep a character consistent: lock once as a board, then move each shot — not N independent generations that drift.
+
+### 4. Structured parameters (what to carry per generation)
+
+Track these so each slot's call is reproducible and the arc stays coherent:
+
+| Param | Meaning | Maps to |
+|---|---|---|
+| `arc_role` | hook / tension / demo / proof / payoff | prompt framing + shot order |
+| `board_media_id` | the locked board image URL | `reference_images` (`@image1`) |
+| `character_media_id` / `visual_dna_id` | presenter identity | `visual_dna_ids` (`@<dna-name>`) |
+| `product_media_id` | product photo URL | `reference_images` (`@image2`) |
+| `input_tier` | `draft` (fast preview) vs `hero` (final) | model + resolution choice |
+| `monologue_segment` | the spoken line for this slot | prompt audio/dialogue line |
+| `aspect_ratio` / `duration` / `sound_enabled` | per UGC Family Defaults above | MCP call args |
+
+### 5. Worked example (brief → slots → board → clips)
+
+Brief: *"15s UGC review of a skincare serum, tech-savvy woman creator."*
+
+1. Ensure/create presenter Visual DNA (tech-savvy woman) → `visual_dna_id`.
+2. Board: `generate_image` a 3-panel `16:9` sheet — (a) chest-up hook holding the serum, (b) hands applying it, (c) thumbs-up reaction — `same character throughout all shots`, locked to the DNA. → `board_media_id`.
+3. Slots (each `9:16`, ~5s, sound OFF, animate from the matching board panel + product `@image2`):
+   - Slot 1 (hook): "Before this serum my routine was five products…" holding it to camera.
+   - Slot 2 (demo): hands applying, product in active use.
+   - Slot 3 (payoff): reaction + "…now it's just one step." soft CTA.
+4. Deliver as a structured message (setup + monologue + media), humanized refs (names/thumbnails, not raw IDs).
+
 ## UX Rules
 
 1. **Always pick a mode explicitly.** Don't auto-pick from one ambiguous word. If the user said "make me an ad" with no other signal, offer labeled options: `[UGC / TV Spot / Product Showcase / Surprise me]`.