@kombai/cli 0.2.0-beta.6 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/kombai.mjs CHANGED
@@ -62,9 +62,9 @@ var init_env = __esm({
62
62
  preprod: { api: "https://api.assistant.preprod.kombai.com", web: "https://agent.preprod.kombai.com" },
63
63
  prod: { api: "https://api.assistant.app.kombai.com", web: "https://agent.kombai.com" }
64
64
  });
65
- DEFAULT_ENV = Object.hasOwn(ENVIRONMENTS, "preprod") ? (
65
+ DEFAULT_ENV = Object.hasOwn(ENVIRONMENTS, "prod") ? (
66
66
  /** @type {EnvName} */
67
- "preprod"
67
+ "prod"
68
68
  ) : "prod";
69
69
  }
70
70
  });
@@ -1040,13 +1040,13 @@ var init_version = __esm({
1040
1040
  init_define_KOMBAI_TELEMETRY();
1041
1041
  init_codexKombaiEntry();
1042
1042
  init_place();
1043
- CLI_VERSION = true ? "0.2.0-beta.6" : (
1043
+ CLI_VERSION = true ? "0.2.0" : (
1044
1044
  /** @type {{ version: string }} */
1045
1045
  JSON.parse(readFileSync(new URL("../../package.json", import.meta.url), "utf8")).version
1046
1046
  );
1047
- CLI_NPX_RUN = true ? "npx -y @kombai/cli@0.2.0-beta.6" : `npx -y ${KOMBAI_CLI_PACKAGE}`;
1047
+ CLI_NPX_RUN = true ? "npx -y @kombai/cli@0.2.0" : `npx -y ${KOMBAI_CLI_PACKAGE}`;
1048
1048
  CLI_RUN = runLineOf(fileURLToPath(import.meta.url), CLI_VERSION, CLI_NPX_RUN);
1049
- CLI_PACKAGE = true ? "@kombai/cli@0.2.0-beta.6" : KOMBAI_CLI_PACKAGE;
1049
+ CLI_PACKAGE = true ? "@kombai/cli@0.2.0" : KOMBAI_CLI_PACKAGE;
1050
1050
  CLI_OUTDATED_NEXT = "A newer Kombai CLI is out; update the Kombai plugin.";
1051
1051
  }
1052
1052
  });
@@ -36487,7 +36487,7 @@ var init_actions = __esm({
36487
36487
  var assets_default;
36488
36488
  var init_assets = __esm({
36489
36489
  "src/skill/assets.md"() {
36490
- assets_default = '# AI images and video\n\n`kombai asset generate` makes an image or a video with an AI model, for the user\'s credits. Make one\nonly when the user asks Kombai for it (names Kombai or picks this skill), or, when the user asked for AI\nvideo, for each prompt in a taste run\'s <deferred-video-generation> block. Never make one on your own,\nnot even where a design would look better with art: use the taste run\'s images, stock links, repo images\nor SVG (`kombai skill html`).\n\n{{RUN}}\n\nA guest can\'t generate (CLI_SIGNIN_REQUIRED): follow `kombai skill sign-in`, with the assets sign-in card where\n`sign_in_card` is among your tools.\n\n## Choose the model\n\n`kombai asset models --type <type>` lists the models, each with the options it takes.\n\n- An image: leave out --model unless the user named one, and Kombai picks its own. That one takes\n --aspect only.\n- A video: --model is required. Its --duration must be one the model lists.\n- Pick --aspect from the box the design shows it in (16:9 for a wide hero, 1:1 for a square tile,\n 9:16 for a phone-height panel), from the ratios the model lists.\n- Any other option goes in as `--param <key=value>`, from the model\'s params. What you leave out runs at the\n default `asset models` lists for it; check a video model\'s `audio` default there before saying it is silent.\n\n## Ask before a video\n\nA video can cost hundreds of credits, and nothing here lists prices, so never guess one. Get its cost\nfirst: run the same generate with `--max-credits 1`, then `kombai asset wait` its run. That run ends in\nASSET_OVER_LIMIT, whose message names the estimate in credits, uses no credits and makes no video. Then tell\nthe user the model, the length and that estimate, and wait for a yes; for several, ask once, naming each. Run the generate again with the number\nthey agreed to as --max-credits: a run that would cost more fails with ASSET_OVER_LIMIT. Their balance is\nin `kombai credits`. An image needs no yes.\n\n## Run it\n\n kombai asset generate --type image --prompt "<text>" --aspect <ratio>\n kombai asset generate --type video --model "<name>" --prompt "<text>" --aspect <ratio> --duration <duration> --max-credits <n>\n\n- A video from an image: add `--from-image <file-or-url>`, a png, jpeg or webp file of at most 10 MB or an https link,\n such as the url of an image made here.\n- A long prompt: `--prompt-file <file>` in place of --prompt (at most 4,000 characters).\n\ngenerate prints the run at once and never waits for it. Then run `kombai asset wait <run>` in the\nforeground, one wait at a time: it returns within about two minutes, so while its status is running, tell\nthe user the asset is still being made, as expected, and wait again. A video takes minutes. For several\nassets, run each generate in turn, then wait for each.\n\n## Use it\n\nWhen it is done, wait prints `url` (an https link), `posterUrl` (a video\'s still), `path` (a copy saved on\nthis machine) and `creditsUsed`. Put `url` in the design as it is:\n\n- An image: `<img src="\u2026" alt="\u2026">` or CSS `url()`.\n- A video: `<video src="\u2026" poster="\u2026" autoplay muted loop playsinline preload="metadata">`, the poster\n from `posterUrl`. Without one, use a still image the design already has.\n\nThe link needs no `kombai asset push`. Never invent or edit an asset link. In your reply, give the user\neach asset\'s `url` (and a video\'s `posterUrl`) as its link, and what it used (`creditsUsed`); `path` is\nonly a local copy, so mention it, if at all, after the link, never in its place. When wait also warns\nCLI_ASSET_NOT_SAVED, the link still works: use it.\n\n## When it fails\n\n- A refused flag names the values the model takes: fix it and run generate again.\n- ASSET_NO_CREDITS: call plans_card if among your tools, else show next\'s plan link; stop.\n- ASSET_OVER_LIMIT: the run would cost more than --max-credits. Ask the user before a higher one.\n- ASSET_NOT_STARTED, or a lost answer: run the same generate again; it picks up the same run.\n- Any other failure: tell the user its message. Try an image once more; ask before trying a video again.\n';
36490
+ assets_default = '# AI images and video\n\n`kombai asset generate` makes an image or a video with an AI model, for the user\'s credits. Make one\nonly when the user asks for an AI image or video itself and asks Kombai for it (names Kombai or picks this\nskill), or, when the user asked for AI video, for each prompt in a taste run\'s <deferred-video-generation>\nblock. A request to design a page, a section or a canvas is not that ask, even when it names Kombai or\nmentions illustrations. Never make one on your own, not even a hero or where a design would look better\nwith art: use the taste run\'s images, stock links, repo images or SVG (`kombai skill html`).\n\n{{RUN}}\n\nA guest can\'t generate (CLI_SIGNIN_REQUIRED): follow `kombai skill sign-in`, with the assets sign-in card where\n`sign_in_card` is among your tools.\n\n## Choose the model\n\n`kombai asset models --type <type>` lists the models, each with the options it takes.\n\n- An image: leave out --model unless the user named one, and Kombai picks its own. That one takes\n --aspect only.\n- A video: --model is required. Its --duration must be one the model lists.\n- Pick --aspect from the box the design shows it in (16:9 for a wide hero, 1:1 for a square tile,\n 9:16 for a phone-height panel), from the ratios the model lists.\n- Any other option goes in as `--param <key=value>`, from the model\'s params. What you leave out runs at the\n default `asset models` lists for it; check a video model\'s `audio` default there before saying it is silent.\n\n## Ask before a video\n\nA video can cost hundreds of credits, and nothing here lists prices, so never guess one. Get its cost\nfirst: run the same generate with `--max-credits 1`, then `kombai asset wait` its run. That run ends in\nASSET_OVER_LIMIT, whose message names the estimate in credits, uses no credits and makes no video. Then tell\nthe user the model, the length and that estimate, and wait for a yes; for several, ask once, naming each. Run the generate again with the number\nthey agreed to as --max-credits: a run that would cost more fails with ASSET_OVER_LIMIT. Their balance is\nin `kombai credits`. An image needs no yes.\n\n## Run it\n\n kombai asset generate --type image --prompt "<text>" --aspect <ratio>\n kombai asset generate --type video --model "<name>" --prompt "<text>" --aspect <ratio> --duration <duration> --max-credits <n>\n\n- A video from an image: add `--from-image <file-or-url>`, a png, jpeg or webp file of at most 10 MB or an https link,\n such as the url of an image made here.\n- A long prompt: `--prompt-file <file>` in place of --prompt (at most 4,000 characters).\n\ngenerate prints the run at once and never waits for it. Then run `kombai asset wait <run>` in the\nforeground, one wait at a time: it returns within about two minutes, so while its status is running, tell\nthe user the asset is still being made, as expected, and wait again. A video takes minutes. For several\nassets, run each generate in turn, then wait for each.\n\n## Use it\n\nWhen it is done, wait prints `url` (an https link), `posterUrl` (a video\'s still), `path` (a copy saved on\nthis machine) and `creditsUsed`. Put `url` in the design as it is:\n\n- An image: `<img src="\u2026" alt="\u2026">` or CSS `url()`.\n- A video: `<video src="\u2026" poster="\u2026" autoplay muted loop playsinline preload="metadata">`, the poster\n from `posterUrl`. Without one, use a still image the design already has.\n\nThe link needs no `kombai asset push`. Never invent or edit an asset link. In your reply, give the user\neach asset\'s `url` (and a video\'s `posterUrl`) as its link, and what it used (`creditsUsed`); `path` is\nonly a local copy, so mention it, if at all, after the link, never in its place. When wait also warns\nCLI_ASSET_NOT_SAVED, the link still works: use it.\n\n## When it fails\n\n- A refused flag names the values the model takes: fix it and run generate again.\n- ASSET_NO_CREDITS: call plans_card if among your tools, else show next\'s plan link; stop.\n- ASSET_OVER_LIMIT: the run would cost more than --max-credits. Ask the user before a higher one.\n- ASSET_NOT_STARTED, or a lost answer: run the same generate again; it picks up the same run.\n- Any other failure: tell the user its message. Try an image once more; ask before trying a video again.\n';
36491
36491
  }
36492
36492
  });
36493
36493
 
@@ -36543,7 +36543,7 @@ var init_faq = __esm({
36543
36543
  var html_default;
36544
36544
  var init_html = __esm({
36545
36545
  "src/skill/html.md"() {
36546
- html_default = '# Writing a design\'s HTML\n\nThe file `kombai node start` prints holds one design. The canvas shows it live in a frame, and\n`kombai screenshot fill` renders the thumbnail most viewers see. Write it so both look the same.\n\n## Build in passes\n\nnode start creates the file, empty. Read it right after node start, before your first write, even though\nit is empty: an editor that writes only files it has read refuses the write otherwise, and the page you\nwrote is lost. Push the first pass within 30 minutes of node start, or the placeholder expires.\n\n1. First pass: every section in order, with its layout, headings and real copy.\n2. Each later pass: one or two sections\' art, motion and interactions.\n\nPush after each pass, and only once its write has succeeded: never in the same batch of tool calls as\nthe write. The canvas shows each push live, so the user watches the page fill in. Check the design once,\nafter its last pass ("Check a finished design" in the overview).\n\n## The file\n\n- Body content only: no `<!DOCTYPE>`, `<html>`, `<head>` or `<body>`. The canvas and the thumbnail\n both wrap it in their own page, inside a `<div id="root">`, so `body > \u2026` selectors match nothing.\n- So the file is a fragment, not a web page: opened on its own it looks broken. Never open, preview or\n serve it, and never link or name its path to the user. To point the user at a design, give the `url`\n node start, node pull and node push print for it: the canvas, with that design in focus. Where\n `canvas_app` shows the canvas beside the chat, and anywhere in the Codex app (whose commands print no link),\n name the design instead, with no link unless the user asks for one. A guest\'s `url` is null: point them at the\n canvas you showed them.\n- Style with Tailwind v4 classes or with your own CSS in a `<style>`. Put every `<style>`, `<link>` and\n library `<script>` at the top of the body. Load Google Fonts with `@import url(\u2026)` as the first line of a\n `<style>`. Set the font, text color and background on your outermost element.\n- Tailwind: add no Tailwind script; Kombai loads Tailwind v4 when the design uses its classes. The canvas\n builds CSS only from classes written in `class="\u2026"`: no config, `@apply`, `@theme` or\n `<style type="text/tailwindcss">`, and a class only a script adds gets no CSS there; write that styling as\n plain CSS in a `<style>`. Use v4 utilities (`bg-black/50`, not `bg-opacity-50`), and CSS variables as\n `bg-(--brand)` or `bg-[var(--brand)]`, never `bg-[--brand]`. On a page with Tailwind classes, style\n no `*` or bare tags in a `<style>`: CSS there beats every Tailwind class.\n- Your own CSS, with no Tailwind classes: the page owns its defaults. Start its `<style>` with a reset\n (margin, padding and box-sizing on `*`) and style headings, lists, links, buttons and images yourself,\n so the page looks the same whether or not Tailwind is loaded. Don\'t name classes like Tailwind\n utilities (`flex`, `hidden`, `text-center`, `p-4`): the canvas may take the page for Tailwind.\n- Define every `@keyframes` you use.\n- `kombai node push` writes a `data-kid="\u2026"` id onto each element of a changed file before it sends it: the id\n the canvas and the user\'s requests name an element by. Read the file again before your next pass to get them.\n Keep the ids when you edit; give a new element none, the next push numbers it.\n\n## Size and position\n\n- A design is 1280 px wide. `--viewport mobile`, `--viewport tablet` or `--viewport desktop` on\n `kombai node start` makes it 390, 768 or 1280. Design for that width: one design per device, not one\n with breakpoints.\n- A design is content height unless you give it a height: its frame is as tall as its page and never\n scrolls. So:\n - Give heights in px (`h-[720px]`, `min-height: 640px`). `h-screen`, `min-h-screen` and `100vh` come out\n 1000 px tall, on the canvas and in the thumbnail.\n - Do not size anything from `window.innerHeight`: on the canvas it is the whole page\'s height.\n- What needs the page to scroll needs a design with a height of its own: scroll-driven effects (scroll\n listeners, parallax, pinned or scrubbed sections, GSAP ScrollTrigger), `sticky` and `fixed` elements, and\n smooth scrolling (Lenis, Locomotive). At content height nothing scrolls, so none of them run: a pinned\n section\'s runway shows as empty space, a sticky element never sticks, and a fixed bottom bar lands 1000 px\n down, mid-page; selected, the canvas shows a page that pins in a device-height window it cannot scroll.\n So after the first push, set the design\'s `rect.h` in canvas.json to its device height (desktop 800,\n tablet 1024, mobile 812) and run `kombai canvas push --canvas <id>`. Selected, it then scrolls inside that\n window and all of these run as on a real page. A reveal that only waits to come into view\n (IntersectionObserver) needs no height: it runs as the viewer pans to it.\n- The thumbnail scrolls the page through once and settles its animations, so it shows the page as a\n visitor who scrolled to the bottom left it: every reveal shown, pinned sections and parallax layers at\n their end, no runway. It takes scrubbed animations at their end too, so an element that fades or slides\n out as the page scrolls is missing from it: animate things in, not out. A design with a height gets the\n whole page as its thumbnail, seen through its window: a sticky element shows where it starts, and a fixed\n one where it sits on the first screen, so a bar fixed to the bottom shows at that screen\'s foot, mid-page.\n- The thumbnail stops at 16,000 px.\n\n## Scripts\n\n- Load each library from a CDN with its own `<script src>` and a pinned version: Chart.js for charts,\n GSAP or Motion for animation. Only public https hosts load.\n- The thumbnail renders with reduced motion. It scrolls the page through, runs GSAP, ScrollTrigger, anime\n and Web Animations to their end, pauses CSS animations and video, and is taken once fonts and images\n are in. The page must look finished by then:\n - Chart.js: `options: { animation: false }`.\n - CSS entrance animations: behind `motion-safe:` or `@media (prefers-reduced-motion: no-preference)`.\n - A page that fills in late (JS entrance animations, content a script draws) sets\n `window.KOMBAI_READY = false` at the top, and `true` when done (or dispatches a `kombai:ready`\n event on window). The thumbnail waits up to 20 s, then takes the page as it is. A page whose text\n names either is waited for, so name them only if you signal.\n\n## Images and video\n\n- Repo files: `/api/local/images/<path from the repo root>`, in src, srcset, poster or CSS `url()`.\n `kombai node push` uploads each one: png, jpg, jpeg, webp, gif, svg, mp4 or webm, up to 20 MB, at\n most 100 per design. Write each path in full, with spaces as `%20`; a path a script builds is not\n uploaded.\n- A file outside the repo, such as an image you generated: `kombai asset push <file> --canvas <id>`\n prints its url. Use that url.\n- AI-generated images or video, only when the user asks Kombai for one (names Kombai or picks its assets\n skill), or for a taste run\'s deferred videos once the user asked for AI video: read `kombai skill assets`.\n Use the url it prints as is.\n- Stock photos: use the links directions.md gives, with size params added. images.unsplash.com:\n `?auto=format&w=<px>&q=80&fit=crop`. images.pexels.com: `?auto=compress&cs=tinysrgb&w=<px>&q=80`.\n The bare link is the full-size original.\n- Icons: inline SVG from the library directions.md names.\n- `<img decoding="async" alt="\u2026">`. `loading="lazy"` is fine: the thumbnail loads every image first.\n- Video: `<video src="\u2026" poster="\u2026" autoplay muted loop playsinline preload="metadata">`. Always set a\n poster: it shows until the video plays. Drop autoplay and loop only for click-to-play, such as a\n walkthrough.\n- Every other URL is absolute and public https: relative paths do not resolve, and the thumbnail\n refuses localhost and private addresses.\n- Never invent an image URL.\n\n## Content\n\n- Real copy from the brief and the repo: real names, numbers and dates. No lorem ipsum. No text for the\n reviewer: no design notes, captions explaining the layout, or "click to see".\n- Plain section headings, as a product\'s UI would have them: "Plans", "Details", "Team", not "What it\n costs", "How it works" or "Who is on site this week".\n- One page or screen per design; a modal or drawer is its own design. For a component, design only\n it, on a plain background.\n- Give each meaningful element a `data-name` saying what it is ("pricing card", "hero headline"): the\n canvas editor shows it.\n- No `dark:` classes or `prefers-color-scheme` queries: they follow the viewer\'s theme, so the canvas and\n the thumbnail can differ. A dark version is its own design.\n\n## Patterns to avoid, unless asked\n\n- Drop shadows on cards; gradient-filled headline text.\n- The stock hero: headline, image, two buttons, badges.\n- Three icon-topped cards in a row; plain pricing, testimonial or two-row stat cards.\n- A footer of only links and a logo; a form or call-out as one big card.\n- Fade-in on appear and lift on hover as the only motion; buttons with the usual radius and hover.\n';
36546
+ html_default = '# Writing a design\'s HTML\n\nThe file `kombai node start` prints holds one design. The canvas shows it live in a frame, and\n`kombai screenshot fill` renders the thumbnail most viewers see. Write it so both look the same.\n\n## Build in passes\n\nnode start creates the file, empty. Read it right after node start, before your first write, even though\nit is empty: an editor that writes only files it has read refuses the write otherwise, and the page you\nwrote is lost. Push the first pass within 30 minutes of node start, or the placeholder expires.\n\n1. First pass: every section in order, with its layout, headings and real copy.\n2. Each later pass: one or two sections\' art, motion and interactions.\n\nPush after each pass, and only once its write has succeeded: never in the same batch of tool calls as\nthe write. The canvas shows each push live, so the user watches the page fill in. Check the design once,\nafter its last pass ("Check a finished design" in the overview).\n\n## The file\n\n- Body content only: no `<!DOCTYPE>`, `<html>`, `<head>` or `<body>`. The canvas and the thumbnail\n both wrap it in their own page, inside a `<div id="root">`, so `body > \u2026` selectors match nothing.\n- So the file is a fragment, not a web page: opened on its own it looks broken. Never open, preview or\n serve it, and never link or name its path to the user. To point the user at a design, give the `url`\n node start, node pull and node push print for it: the canvas, with that design in focus. Where\n `canvas_app` shows the canvas beside the chat, and anywhere in the Codex app (whose commands print no link),\n name the design instead, with no link unless the user asks for one. A guest\'s `url` is null: point them at the\n canvas you showed them.\n- Style with Tailwind v4 classes or with your own CSS in a `<style>`. Put every `<style>`, `<link>` and\n library `<script>` at the top of the body. Load Google Fonts with `@import url(\u2026)` as the first line of a\n `<style>`. Set the font, text color and background on your outermost element.\n- Tailwind: add no Tailwind script; Kombai loads Tailwind v4 when the design uses its classes. The canvas\n builds CSS only from classes written in `class="\u2026"`: no config, `@apply`, `@theme` or\n `<style type="text/tailwindcss">`, and a class only a script adds gets no CSS there; write that styling as\n plain CSS in a `<style>`. Use v4 utilities (`bg-black/50`, not `bg-opacity-50`), and CSS variables as\n `bg-(--brand)` or `bg-[var(--brand)]`, never `bg-[--brand]`. On a page with Tailwind classes, style\n no `*` or bare tags in a `<style>`: CSS there beats every Tailwind class.\n- Your own CSS, with no Tailwind classes: the page owns its defaults. Start its `<style>` with a reset\n (margin, padding and box-sizing on `*`) and style headings, lists, links, buttons and images yourself,\n so the page looks the same whether or not Tailwind is loaded. Don\'t name classes like Tailwind\n utilities (`flex`, `hidden`, `text-center`, `p-4`): the canvas may take the page for Tailwind.\n- Define every `@keyframes` you use.\n- `kombai node push` writes a `data-kid="\u2026"` id onto each element of a changed file before it sends it: the id\n the canvas and the user\'s requests name an element by. Read the file again before your next pass to get them.\n Keep the ids when you edit; give a new element none, the next push numbers it.\n\n## Size and position\n\n- A design is 1280 px wide. `--viewport mobile`, `--viewport tablet` or `--viewport desktop` on\n `kombai node start` makes it 390, 768 or 1280. Design for that width: one design per device, not one\n with breakpoints.\n- A design is content height unless you give it a height: its frame is as tall as its page and never\n scrolls. So:\n - Give heights in px (`h-[720px]`, `min-height: 640px`). `h-screen`, `min-h-screen` and `100vh` come out\n 1000 px tall, on the canvas and in the thumbnail.\n - Do not size anything from `window.innerHeight`: on the canvas it is the whole page\'s height.\n- What needs the page to scroll needs a design with a height of its own: scroll-driven effects (scroll\n listeners, parallax, pinned or scrubbed sections, GSAP ScrollTrigger), `sticky` and `fixed` elements, and\n smooth scrolling (Lenis, Locomotive). At content height nothing scrolls, so none of them run: a pinned\n section\'s runway shows as empty space, a sticky element never sticks, and a fixed bottom bar lands 1000 px\n down, mid-page; selected, the canvas shows a page that pins in a device-height window it cannot scroll.\n So after the first push, set the design\'s `rect.h` in canvas.json to its device height (desktop 800,\n tablet 1024, mobile 812) and run `kombai canvas push --canvas <id>`. Selected, it then scrolls inside that\n window and all of these run as on a real page. A reveal that only waits to come into view\n (IntersectionObserver) needs no height: it runs as the viewer pans to it.\n- The thumbnail scrolls the page through once and settles its animations, so it shows the page as a\n visitor who scrolled to the bottom left it: every reveal shown, pinned sections and parallax layers at\n their end, no runway. It takes scrubbed animations at their end too, so an element that fades or slides\n out as the page scrolls is missing from it: animate things in, not out. A design with a height gets the\n whole page as its thumbnail, seen through its window: a sticky element shows where it starts, and a fixed\n one where it sits on the first screen, so a bar fixed to the bottom shows at that screen\'s foot, mid-page.\n- The thumbnail stops at 16,000 px.\n\n## Scripts\n\n- Load each library from a CDN with its own `<script src>` and a pinned version: Chart.js for charts,\n GSAP or Motion for animation. Only public https hosts load.\n- The thumbnail renders with reduced motion. It scrolls the page through, runs GSAP, ScrollTrigger, anime\n and Web Animations to their end, pauses CSS animations and video, and is taken once fonts and images\n are in. The page must look finished by then:\n - Chart.js: `options: { animation: false }`.\n - CSS entrance animations: behind `motion-safe:` or `@media (prefers-reduced-motion: no-preference)`.\n - A page that fills in late (JS entrance animations, content a script draws) sets\n `window.KOMBAI_READY = false` at the top, and `true` when done (or dispatches a `kombai:ready`\n event on window). The thumbnail waits up to 20 s, then takes the page as it is. A page whose text\n names either is waited for, so name them only if you signal.\n\n## Images and video\n\n- Repo files: `/api/local/images/<path from the repo root>`, in src, srcset, poster or CSS `url()`.\n `kombai node push` uploads each one: png, jpg, jpeg, webp, gif, svg, mp4 or webm, up to 20 MB, at\n most 100 per design. Write each path in full, with spaces as `%20`; a path a script builds is not\n uploaded.\n- A file outside the repo, such as an image you generated: `kombai asset push <file> --canvas <id>`\n prints its url. Use that url.\n- AI-generated images or video, only when the user asks for one itself and asks Kombai for it (names\n Kombai or picks its assets skill; asking Kombai for a design is not asking for one), or for a taste run\'s\n deferred videos once the user asked for AI video: read `kombai skill assets`.\n Use the url it prints as is.\n- Stock photos: use the links directions.md gives, with size params added. images.unsplash.com:\n `?auto=format&w=<px>&q=80&fit=crop`. images.pexels.com: `?auto=compress&cs=tinysrgb&w=<px>&q=80`.\n The bare link is the full-size original.\n- Icons: inline SVG from the library directions.md names.\n- `<img decoding="async" alt="\u2026">`. `loading="lazy"` is fine: the thumbnail loads every image first.\n- Video: `<video src="\u2026" poster="\u2026" autoplay muted loop playsinline preload="metadata">`. Always set a\n poster: it shows until the video plays. Drop autoplay and loop only for click-to-play, such as a\n walkthrough.\n- Every other URL is absolute and public https: relative paths do not resolve, and the thumbnail\n refuses localhost and private addresses.\n- Never invent an image URL.\n\n## Content\n\n- Real copy from the brief and the repo: real names, numbers and dates. No lorem ipsum. No text for the\n reviewer: no design notes, captions explaining the layout, or "click to see".\n- Plain section headings, as a product\'s UI would have them: "Plans", "Details", "Team", not "What it\n costs", "How it works" or "Who is on site this week".\n- One page or screen per design; a modal or drawer is its own design. For a component, design only\n it, on a plain background.\n- Give each meaningful element a `data-name` saying what it is ("pricing card", "hero headline"): the\n canvas editor shows it.\n- No `dark:` classes or `prefers-color-scheme` queries: they follow the viewer\'s theme, so the canvas and\n the thumbnail can differ. A dark version is its own design.\n\n## Patterns to avoid, unless asked\n\n- Drop shadows on cards; gradient-filled headline text.\n- The stock hero: headline, image, two buttons, badges.\n- Three icon-topped cards in a row; plain pricing, testimonial or two-row stat cards.\n- A footer of only links and a logo; a form or call-out as one big card.\n- Fade-in on appear and lift on hover as the only motion; buttons with the usual radius and hover.\n';
36547
36547
  }
36548
36548
  });
36549
36549
 
package/dist/launch.mjs CHANGED
@@ -7,7 +7,7 @@ import { dirname, join } from 'node:path';
7
7
  import { fileURLToPath, pathToFileURL } from 'node:url';
8
8
 
9
9
  // The version that wrote this file: a published one, so its npx line always works. Filled in by the build.
10
- const WRITTEN_BY = '0.2.0-beta.6';
10
+ const WRITTEN_BY = '0.2.0';
11
11
  const root = dirname(fileURLToPath(import.meta.url));
12
12
 
13
13
  // On stderr, as the CLI's own start-up errors are: under `kombai mcp` stdout carries MCP frames only.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kombai/cli",
3
- "version": "0.2.0-beta.6",
3
+ "version": "0.2.0",
4
4
  "description": "Design UI with Kombai from your coding agent: design directions grounded in your repo, built as designs on a Kombai canvas.",
5
5
  "keywords": [
6
6
  "kombai",