@cerebriline/core 4.100.248 → 4.100.249

package/assets/prompt-templates/claude.md

@@ -410,9 +410,18 @@ It is the wrong tool for text that is not a symbol: strings, comments, config ke
 # tool: generate_image
 {{DEFAULT}}
 
+# tool: generate_icon
+{{DEFAULT}}
+
 # tool: edit_image
 {{DEFAULT}}
 
+# tool: render_image
+{{DEFAULT}}
+
+# tool: transform_image
+{{DEFAULT}}
+
 # tool: transcribe_audio
 {{DEFAULT}}
 

package/assets/prompt-templates/deepseek.md

@@ -193,9 +193,18 @@ Reach for it the moment you are about to do one of these by hand:
 # tool: generate_image
 {{DEFAULT}}
 
+# tool: generate_icon
+{{DEFAULT}}
+
 # tool: edit_image
 {{DEFAULT}}
 
+# tool: render_image
+{{DEFAULT}}
+
+# tool: transform_image
+{{DEFAULT}}
+
 # tool: transcribe_audio
 {{DEFAULT}}
 

package/assets/prompt-templates/default.md

@@ -212,7 +212,9 @@ Output: plain text, one result per line as `file:line:column` followed by that s
 An empty answer is a real answer once the symbol resolved: for `definition`, `references`, `implementations`, `type_definition`, `callers` and `hover` the server understood the symbol and nothing matched, so a text search for the same question will not find more. `workspace_symbols` is the exception, and says so when it comes back empty: it reads a project-wide index that covers the languages a server is installed for and does not index script embedded in `.html` or other template files, so nothing there is not proof of nothing anywhere. And when the file does not parse, every answer about it opens with that line — while it is there, the server is answering from a partial parse and you are reading guesses.
 
 # tool: generate_image
-Generate an image from a text description and save it into the workspace. Use it for visual work you would otherwise have to ask the user to do elsewhere: an app icon, a placeholder texture or sprite, a logo, a background, or a mockup of a layout or theme you are about to build.
+Generate an image from a text description and save it into the workspace. Use it for visual work you would otherwise have to ask the user to do elsewhere: an app icon, a placeholder texture or sprite, a logo, a background, an illustration or a photograph.
+
+It paints pixels: it cannot write legible text, and a picture of an interface or a diagram made this way has garbled labels. For a screen, a mockup, a workflow diagram, a chart or anything else with words in it, write it as HTML, SVG or Mermaid and use `render_image` when you have it.
 
 The image is written to a file and, if you can see images, returned to you as well — so you can look at what you made and generate again with a changed prompt if it is wrong.
 
@@ -223,6 +225,24 @@ Arguments:
 
 This costs real time — seconds to a minute per image — and on a hosted backend it costs money. Generate one image and look at it before generating variations.
 
+# tool: generate_icon
+Make an icon for an application, a site or a file type: several proposals for the user to choose from, then the chosen one saved in every format an icon needs. Two steps, one call each.
+
+1. Proposals. Give `prompt`: what the icon shows and the feeling it should have ("a paper plane, friendly, blue on white"). Several candidates are drawn and returned on one numbered sheet, each saved as its own file. Show the user the sheet and ask which one they want (`ask_question`, with the numbers as the options); do not choose for them. If none is right, call again with a changed prompt.
+2. Files. Give `pick`: the path of the chosen proposal (or of any square image in the workspace), and `path`: where the icon belongs, without an extension, e.g. `assets/icon`. That writes `assets/icon.ico`, `assets/icon.icns`, `assets/icon.png` and `assets/icon-<size>.png` for the usual sizes.
+
+Arguments:
+- `prompt` — step 1: the subject and the mood. The rules of an icon (one centred subject, bold shapes, no text) are added for you.
+- `count` — step 1: how many proposals, 1 to 6. Optional, default 4.
+- `style` — step 1: e.g. `flat vector`, `glossy 3D`, `line art`, `pixel art`. Optional, default flat vector.
+- `pick` — step 2: workspace path of the image to make the icon from.
+- `path` — step 2: where to save, without an extension.
+- `formats` — step 2: which of `ico`, `icns`, `png`, `webp` to write. Optional, default `ico,icns,png`.
+- `sizes` — step 2: the PNG sizes to write beside the main one. Optional, default `16,32,48,64,128,180,192,256,512`.
+- `background` — step 2: a CSS colour to put behind the icon. Optional; left as the proposal has it.
+
+Each proposal costs what an image costs: seconds to a minute, and money on a hosted backend.
+
 # tool: edit_image
 Edit an existing image in the workspace according to a text instruction and save the result as a new file. Use it to change a picture you already have rather than generate a different one: recolour or restyle an icon, change one element of a mockup, combine a subject with a background.
 
@@ -237,6 +257,34 @@ Arguments:
 
 How far an edit goes depends on the backend: some follow the instruction, others redraw over the source and only make small changes. Look at the result before relying on it. This costs real time — seconds to a minute per image — and on a hosted backend it costs money.
 
+# tool: render_image
+Render HTML, SVG or a Mermaid diagram that you write into an image file in the workspace. Use it for anything with text or structure in it: application screens and mockups, workflow and architecture diagrams, charts, annotated figures. An image model cannot write legible text or draw a real interface; this draws exactly what you write.
+
+The image is saved and, if you can see images, returned to you, so you can check the layout and render again.
+
+- `source` — what to draw: HTML with its CSS (a fragment or a whole document), an SVG document, or Mermaid notation (`flowchart LR`, `sequenceDiagram`, ...). Relative URLs resolve against the workspace root, so a screen of the application can link the project's own stylesheet and images: reuse its markup and class names with sample data and the picture is the real interface.
+- `kind` — `html`, `svg` or `mermaid`. Optional; read from the source.
+- `path` — where to save, relative to the workspace: `.png`, or `.svg` to keep an SVG or Mermaid drawing as vectors. Optional; defaults to a PNG under `.cline/rendered-images/`.
+- `width`, `height` — page size in CSS pixels. Optional. Leave both out and the image is exactly as large as what was drawn; `width` alone fixes where the layout wraps.
+- `scale` — pixel density, 1 to 4, default 2.
+- `crop` — `"x,y,width,height"` in CSS pixels, to keep one region of the page.
+- `background` — a CSS colour, or `transparent`.
+- `theme` — Mermaid only: `default`, `dark`, `neutral` or `forest`.
+
+A README on GitHub renders a ```mermaid block as it is; render a diagram to a file when it must show somewhere that does not. Remote fonts, scripts and images load only if the machine reaches them quickly: inline what matters.
+
+# tool: transform_image
+Resize, crop or convert an image file in the workspace and save the result as a new file. Use it to change an image's dimensions, cut a region out of it, change its format, or make an icon file from it. The source is never modified.
+
+- `image` — workspace path of the source: PNG, JPEG, WebP, GIF, BMP, AVIF, ICO or SVG.
+- `path` — where to save, relative to the workspace. The extension chooses the format: `.png`, `.jpg`, `.webp`, `.ico` or `.icns`. Optional; defaults to a file beside the source with the new size in its name.
+- `width`, `height` — the new size in pixels. Give one and the other follows the proportions.
+- `fit` — with both given: `inside` (default; the whole image, within the box, proportions kept), `cover` (fills the box, the overflow cut off), `pad` (the whole image, padded to exactly the box) or `stretch`.
+- `crop` — `"x,y,width,height"` in pixels of the source, taken before resizing.
+- `background` — a CSS colour for padding and for what was transparent. Optional; transparency is kept where the format has it, and JPEG gets white.
+- `quality` — 1 to 100 for `.jpg` and `.webp`, default 90.
+- `sizes` — for `.ico` and `.icns`, the sizes to hold, e.g. `"16,32,48,256"`. Optional; the usual set when left out.
+
 # tool: transcribe_audio
 Transcribe an audio file in the workspace to text. Use it to read a recording you would otherwise have to ask the user to describe: a meeting, a voice note, the audio of a demo.
 

package/assets/prompt-templates/gemma.md

@@ -198,9 +198,18 @@ Query the language servers for semantic information. Use this instead of `search
 # tool: generate_image
 {{DEFAULT}}
 
+# tool: generate_icon
+{{DEFAULT}}
+
 # tool: edit_image
 {{DEFAULT}}
 
+# tool: render_image
+{{DEFAULT}}
+
+# tool: transform_image
+{{DEFAULT}}
+
 # tool: transcribe_audio
 {{DEFAULT}}
 

package/assets/prompt-templates/glm.md

@@ -181,9 +181,18 @@ Output: plain text, one result per line as `file:line:column` followed by the so
 # tool: generate_image
 {{DEFAULT}}
 
+# tool: generate_icon
+{{DEFAULT}}
+
 # tool: edit_image
 {{DEFAULT}}
 
+# tool: render_image
+{{DEFAULT}}
+
+# tool: transform_image
+{{DEFAULT}}
+
 # tool: transcribe_audio
 {{DEFAULT}}
 

package/assets/prompt-templates/kimi-k3.md

@@ -303,9 +303,18 @@ Output: plain text, one result per line as `file:line:column` followed by that s
 # tool: generate_image
 {{DEFAULT}}
 
+# tool: generate_icon
+{{DEFAULT}}
+
 # tool: edit_image
 {{DEFAULT}}
 
+# tool: render_image
+{{DEFAULT}}
+
+# tool: transform_image
+{{DEFAULT}}
+
 # tool: transcribe_audio
 {{DEFAULT}}
 

package/assets/prompt-templates/kimi.md

@@ -247,9 +247,18 @@ Output: plain text, one result per line as `file:line:column` followed by that s
 # tool: generate_image
 {{DEFAULT}}
 
+# tool: generate_icon
+{{DEFAULT}}
+
 # tool: edit_image
 {{DEFAULT}}
 
+# tool: render_image
+{{DEFAULT}}
+
+# tool: transform_image
+{{DEFAULT}}
+
 # tool: transcribe_audio
 {{DEFAULT}}
 

package/assets/prompt-templates/minimax.md

@@ -290,7 +290,9 @@ In each case the alternative is `search_codebase`, which is the thing this tool
 # tool: generate_image
 Generate an image from a text description and save it into the workspace. Call shape: `generate_image(prompt: string, path?: string, size?: string)`.
 
-Use it for visual work you would otherwise have to ask the user to do elsewhere: an app icon, a placeholder texture or sprite, a logo, a background, or a mockup of a layout or theme you are about to build.
+Use it for visual work you would otherwise have to ask the user to do elsewhere: an app icon, a placeholder texture or sprite, a logo, a background, an illustration or a photograph.
+
+It paints pixels: it cannot write legible text, and a picture of an interface or a diagram made this way has garbled labels. For a screen, a mockup, a workflow diagram, a chart or anything else with words in it, write it as HTML, SVG or Mermaid and use `render_image` when you have it.
 
 The image is written to a file and, if you can see images, returned to you as well — so you can look at what you made and generate again with a changed prompt if it is wrong.
 
@@ -301,9 +303,18 @@ The image is written to a file and, if you can see images, returned to you as we
 
 This costs real time — seconds to a minute per image — and on a hosted backend it costs money. Generate one image and look at it before generating variations.
 
+# tool: generate_icon
+{{DEFAULT}}
+
 # tool: edit_image
 {{DEFAULT}}
 
+# tool: render_image
+{{DEFAULT}}
+
+# tool: transform_image
+{{DEFAULT}}
+
 # tool: transcribe_audio
 {{DEFAULT}}
 

package/assets/prompt-templates/nemotron.md

@@ -238,9 +238,18 @@ Output: plain text, one result per line as `file:line:column` followed by that s
 # tool: generate_image
 {{DEFAULT}}
 
+# tool: generate_icon
+{{DEFAULT}}
+
 # tool: edit_image
 {{DEFAULT}}
 
+# tool: render_image
+{{DEFAULT}}
+
+# tool: transform_image
+{{DEFAULT}}
+
 # tool: transcribe_audio
 {{DEFAULT}}
 

package/assets/prompt-templates/qwen.md

@@ -313,9 +313,18 @@ Reach for it the moment you are about to do one of these by hand:
 # tool: generate_image
 {{DEFAULT}}
 
+# tool: generate_icon
+{{DEFAULT}}
+
 # tool: edit_image
 {{DEFAULT}}
 
+# tool: render_image
+{{DEFAULT}}
+
+# tool: transform_image
+{{DEFAULT}}
+
 # tool: transcribe_audio
 {{DEFAULT}}
 

package/assets/skills/media-audio/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: media-audio
+description: >-
+  Reads and makes audio: turns a recording into text or subtitles, and turns
+  text into spoken audio. Use when the user asks to transcribe a recording, a
+  meeting, a voice note or the sound of a video, to make subtitles, to
+  translate speech, or to make a voice-over, a spoken prompt or an audio
+  version of a text.
+---
+
+# Audio
+
+You can read audio and make speech yourself. Do not ask the user to describe a
+recording you could transcribe, or to record something you could synthesize.
+
+## Which tool
+
+| The task | Use |
+|---|---|
+| What is said in an audio file | `transcribe_audio` |
+| Subtitles for a recording or a clip | `transcribe_audio` with `format: srt` or `vtt` |
+| The English of speech in another language | `transcribe_audio` with `translate: true` |
+| A voice-over, a spoken prompt, an audio version of a text | `synthesize_speech` |
+
+When you do not have the tool you need, it is not set up. Say that the user
+turns it on in **Settings > API Configuration > Audio** (the speech-to-text
+endpoint for transcription, the text-to-speech endpoint for speech), and stop
+there.
+
+## Transcribing
+
+- The file has to be in the workspace: wav, mp3, flac, ogg, m4a or webm. For
+  the sound of a video in another container, extract the audio first with the
+  project's tools (`ffmpeg -i clip.mp4 -vn audio.m4a`) if they are installed.
+- Give `output` a path for anything longer than a few minutes, and for
+  subtitles: the whole transcript is saved there and you get its beginning.
+  Read the file for the rest.
+- Give `prompt` the names and terms the recording uses. It fixes spelling.
+- Give `language` when you know it; detection can pick the wrong one on a
+  short or noisy recording.
+- A transcript is what was heard, not what was meant. When it is the basis of
+  a summary, minutes or tasks, say where a passage was unclear.
+
+## Speaking
+
+- Write the text as it should be said: spell out abbreviations, write numbers
+  and symbols the way they are read, and break long sentences.
+- Leave `voice` out to use the configured one. Name one only when the user
+  asked for it.
+- Save the file where the project keeps its audio and give it a name that
+  says what it is. Without a `path` it goes under `.cline/generated-audio/`.
+- You do not hear the result. Say what you asked for, where the file is and
+  how long it is, and let the user listen.
+- For a long text, make one file per section. A section that came out wrong
+  can then be made again alone.

package/assets/skills/media-images/SKILL.md

@@ -0,0 +1,102 @@
+---
+name: media-images
+description: >-
+  Makes and changes pictures for the project: rendered screens and mockups of
+  the application, workflow and architecture diagrams, charts, illustrations
+  and photographs, icons in every format, and resized, cropped or converted
+  copies of an image. Use when the user asks for an image, a picture of the
+  interface, a diagram, a logo, an icon or favicon, images for a README or the
+  documentation, or to change an image's size, shape or format.
+---
+
+# Images
+
+You can make images yourself. Do not tell the user to make one elsewhere, and
+do not describe an image you could produce.
+
+## Which tool
+
+| The picture is | Use | Why |
+|---|---|---|
+| A screen, a mockup, a dialog, anything showing the application's interface | `render_image` with HTML and CSS | Every label is the text you type. An image model garbles words |
+| A workflow, a sequence, a state machine, an architecture, a schema | `render_image` with Mermaid | The notation is short and the layout is done for you |
+| A chart, a badge, a banner with a title, an annotated figure | `render_image` with SVG or HTML | Exact numbers, exact text |
+| A photograph, an illustration, a texture, a background, artwork | `generate_image` | Only an image model paints |
+| An icon for an application, a site or a file type | `generate_icon` | Several proposals to choose from, then `.ico`, `.icns` and every PNG size |
+| A change to a picture that exists (restyle, recolour, replace a part) | `edit_image` | It starts from the picture |
+| The same picture at another size, cut down, or in another format | `transform_image` | Exact pixels, no redrawing |
+
+The rule behind the table: **if it has words or structure in it, write it and
+render it. If it is a picture of something, generate it.** Asked for "images
+showing the workflow of the application", the right tool is `render_image`,
+not `generate_image`.
+
+`render_image` and `transform_image` need nothing set up. `generate_image`,
+`generate_icon` and `edit_image` need an image endpoint; when you do not have
+them, say that the user turns one on in **Settings > API Configuration >
+Images**, and offer what `render_image` can do instead.
+
+## Rendering a screen of the application
+
+1. Read the component or template that draws the screen, and its stylesheet.
+2. Write the screen as one HTML document: the application's own markup and
+   class names, filled with realistic sample data. Link the project's real
+   stylesheet with a relative URL (`<link rel="stylesheet"
+   href="src/styles/app.css">`): relative URLs resolve from the workspace root.
+   Inline what a build step would have produced.
+3. Call `render_image` with `width` set to the window you want to show
+   (1280 for a desktop, 390 for a phone) and no `height`: the picture is as
+   tall as the page.
+4. Look at the result if you can see images. Fix what is off and render again.
+
+Do not invent an interface the application does not have. If you cannot read
+the real one, say that the picture is a mockup.
+
+## Diagrams
+
+Write Mermaid. Keep node labels short; put detail in the surrounding text.
+
+- A README shown on GitHub or GitLab renders a fenced `mermaid` block as it
+  is. Prefer that there: it stays editable and needs no file.
+- Render to a file with `render_image` when it must show somewhere that does
+  not (npm, a PDF, a slide, the VS Code Marketplace) or must look the same
+  everywhere. Save as `.svg` to keep it sharp at any size, `.png` otherwise.
+- `theme: dark` for a dark page; `background: transparent` to sit on any page.
+
+## Images for a README or the documentation
+
+1. Decide what each image has to show before making any. One idea per image.
+2. Save them in the repository where its other images are (`docs/images/`,
+   `assets/`, `.github/`); create `docs/images/` when there is no such place.
+   Give each a name that says what it shows.
+3. Reference them with a relative path and alt text that says what is in the
+   picture: `![The upload flow: validate, index, search](docs/images/upload-flow.png)`.
+4. Keep them a sensible size: 1200 to 1600 pixels across is plenty for a
+   README. Use `transform_image` to bring a larger one down.
+
+## Icons
+
+Call `generate_icon` with a `prompt`. It returns several numbered proposals.
+Show them to the user and ask which one they want; the choice is theirs. Then
+call it again with `pick` and `path`, and it writes the icon in every format.
+Put the files where the project expects them (`public/favicon.ico`,
+`build/icon.icns`, `assets/icon.png`) and update what refers to them: the
+manifest, the HTML head, the packaging configuration.
+
+An image the user already has becomes an icon the same way: pass it as `pick`.
+
+## Size, shape and format
+
+`transform_image` takes a `width` or a `height` (the other follows), both with
+a `fit`, a `crop`, and writes whatever the `path` ends in: `.png`, `.jpg`,
+`.webp`, `.ico`, `.icns`. Use it instead of a shell command. The source file
+is never changed.
+
+`render_image` also takes `width`, `height`, `scale` and `crop`, so a rendered
+picture can be made at the right size in the first place.
+
+## After making one
+
+Say where the file is. If you cannot see images, say what you asked for and
+let the user judge it. Generating costs time and may cost money: make one,
+look, then decide whether another is needed.

package/assets/skills/media-video/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: media-video
+description: >-
+  Makes short video clips from a description or from a starting image. Use
+  when the user asks for a video, a clip, an animation of an image, a
+  background loop, a product shot or placeholder footage.
+---
+
+# Video
+
+You can make a short clip yourself with `generate_video`. Do not send the user
+elsewhere for a few seconds of footage.
+
+When you do not have `generate_video`, it is not set up. Say that the user
+turns it on in **Settings > API Configuration > Video**, and stop there.
+
+## What it does well, and what it does not
+
+It makes one scene of a few seconds: a subject, a movement, a camera. It does
+not follow a storyboard, does not write legible text, and does not record the
+application.
+
+| Wanted | Do |
+|---|---|
+| A background loop, a product shot, an atmospheric clip | `generate_video` |
+| A still picture brought to life | `generate_video` with `image` |
+| A demo of the application in use | Not this tool. Offer screens made with `render_image`, or say the user has to record it |
+| A clip with a title or captions in it | Generate the footage without text and say the text has to be added in an editor |
+
+## Making a clip
+
+1. Write the `prompt` as one scene: what is in it, what moves and how, what
+   the camera does, the style and the light. "A paper plane glides left to
+   right over a blue desk, slow push-in, soft daylight, flat illustration."
+2. To control how it looks, make the first frame as a picture first
+   (`generate_image`, or `render_image` for anything with text or structure)
+   and pass it as `image`. Only some video models accept one; the reply says
+   so when it does not.
+3. Leave `size` and `seconds` out unless the task needs them. The backend
+   supports only a few shapes, and length costs more than proportionally.
+4. Give a `seed` when the user may want the same clip again with one change.
+
+A clip takes from most of a minute to many minutes, and on a hosted backend
+it costs money. Make one, tell the user where it is and let them judge it:
+you cannot watch it. Do not make another to "improve" one nobody has said is
+wrong.
+
+## After making one
+
+Save it where the project keeps its media, with a name that says what it
+shows; without a `path` it goes under `.cline/generated-videos/`. To show it
+in a README, link the file. Most renderers do not play an embedded video from
+the repository.