@vatio-ai/skills 1.16.0 → 1.17.0

package/.claude-plugin/marketplace.json

@@ -11,8 +11,8 @@
     {
       "name": "vatio",
       "source": "./",
-      "description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, put it in your web, iOS or Android app with /vatio-add-to-app, then improve it daily with /vatio-improve.",
-      "version": "1.16.0",
+      "description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, put it in your web, iOS, Android or Flutter app with /vatio-add-to-app, then improve it daily with /vatio-improve.",
+      "version": "1.17.0",
       "homepage": "https://vatio.ai/docs/integrations/claude-code",
       "category": "development",
       "keywords": [

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "vatio",
-  "description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, put it in your web, iOS or Android app with /vatio-add-to-app, then improve it daily with /vatio-improve.",
-  "version": "1.16.0",
+  "description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, put it in your web, iOS, Android or Flutter app with /vatio-add-to-app, then improve it daily with /vatio-improve.",
+  "version": "1.17.0",
   "author": {
     "name": "Vatio",
     "url": "https://vatio.ai"

package/README.md

@@ -20,7 +20,7 @@ need your app’s project on your computer and Node.js 20 or newer.
 | Skill | What it does |
 |---|---|
 | `vatio-init` | The first one in a project: looks at what is already there (a `vatio.yml` anywhere in the repository, the app's code) and recommends from it. With no agent yet, builds one: asks the owner what the code does not answer, writes `vatio.yml`, pushes it (with no account, as a trial) and hands over a link to try it and one to keep it. With one, gets a developer who joined the project up to speed |
-| `vatio-add-to-app` | Puts the agent in your app once you have tried it: the web widget, or the iOS or Android SDK with a chat screen in your app's style, a publishable token for development and one for release, and your signed-in users passed along |
+| `vatio-add-to-app` | Puts the agent in your app once you have tried it: the web widget, or the iOS, Android or Flutter SDK with a chat screen in your app's style, a publishable token for development and one for release, and your signed-in users passed along |
 | `vatio-improve` | Takes every reply your supervisors reported in the inbox in one session: reads `vatio flags`, fixes each cause, `vatio push`, proves it with `vatio test` (on Vatio's servers, in the background) and publishes with `vatio publish` after your approval |
 | `vatio-share-session` | Sends the coding session to the Vatio team when you ask it to, or offers to when the others finish (send it, not now, or don't ask again), after showing you what goes (images left out, anything that looks like a secret redacted), with your feedback if you want to add some |
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@vatio-ai/skills",
-  "version": "1.16.0",
-  "description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, put it in your web, iOS or Android app with /vatio-add-to-app, then improve it daily with /vatio-improve.",
+  "version": "1.17.0",
+  "description": "Vatio skills for Claude Code, Cursor and Codex: add an AI agent to the app you're building with /vatio-init, put it in your web, iOS, Android or Flutter app with /vatio-add-to-app, then improve it daily with /vatio-improve.",
   "keywords": [
     "vatio",
     "ai-agent",

package/skills/vatio-add-to-app/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: vatio-add-to-app
-description: Puts a Vatio agent where the app's users talk to it — the web widget in a web app, the Swift package in an iOS app, the Kotlin library in an Android app — with a publishable token per environment, the signed-in user passed along, and, on mobile, a chat screen in the app's own style. Use after vatio-init, or when asked to add the agent, the chat, the widget or the Vatio SDK to a website, a web app, an iPhone/iOS app or an Android app.
+description: Puts a Vatio agent where the app's users talk to it — the web widget in a web app, the Swift package in an iOS app, the Kotlin library in an Android app, the Dart package in a Flutter app — with a publishable token per environment, the signed-in user passed along, and, on mobile, a chat screen in the app's own style. Use after vatio-init, or when asked to add the agent, the chat, the widget or the Vatio SDK to a website, a web app, an iPhone/iOS app, an Android app or a Flutter app.
 ---
 
 # Put the agent in the app
@@ -17,14 +17,14 @@ npx @vatio-ai/cli docs
 
 Under **For coding agents**, follow **Putting the agent in the app**. It takes
 precedence over the summary below, and the pages it links (Web widget, iOS
-SDK, Android SDK, Authentication, Supabase) have the details.
+SDK, Android SDK, Flutter SDK, Authentication, Supabase) have the details.
 
 ## In short
 
-1. **Find where it goes.** Web, iOS, Android, or several, and every origin a
+1. **Find where it goes.** Web, iOS, Android, Flutter, or several, and every origin a
    build will call from: local and production web addresses,
    `ios-app://BUNDLE_ID`, `android-app://APPLICATION_ID` (debug ids count).
-   React Native, Expo and Flutter have no Vatio SDK yet: say so, and
+   A Flutter app needs both app origins. React Native and Expo have no Vatio SDK yet: say so, and
    `vatio feedback` that one was asked for.
 2. **Tell the user what you will add before changing anything**: which
    screens or layout, which tokens, how signed-in users are passed, and ask
@@ -32,12 +32,13 @@ SDK, Android SDK, Authentication, Supabase) have the details.
 3. **Tokens.** `vatio tokens create --env preview` for development builds and
    `--env live` for release builds, each with its origins. `vatpub_` tokens
    ship in the app's configuration; a `vat_` token never does.
-4. **Add it.** Web: the widget, once for the whole app. iOS and Android: the
+4. **Add it.** Web: the widget, once for the whole app. iOS, Android and Flutter: the
    SDK has no UI, so write the chat screen in the app's own style from the
    example in [vatio-ai/ios](https://github.com/vatio-ai/ios)
-   (`Example/VatioExample/Views.swift`) or
+   (`Example/VatioExample/Views.swift`),
    [vatio-ai/android](https://github.com/vatio-ai/android)
-   (`example/src/main/kotlin/ai/vatio/example/Views.kt`).
+   (`example/src/main/kotlin/ai/vatio/example/Views.kt`) or
+   [vatio-ai/flutter](https://github.com/vatio-ai/flutter) (`example/lib/views.dart`).
 5. **Signed-in users.** With `auth: supabase:` the web widget needs nothing
    and the SDKs take the session's access token; with `auth: public_key:` the
    app's backend signs the visitor token, and the private key never goes into

package/skills/vatio-init/SKILL.md

@@ -42,7 +42,8 @@ you recommend, and ask them to confirm.
      which of their systems it should read from. Do not invent business
      facts.
   2. `vatio init SLUG` in the repository the agent belongs in, then write
-     `vatio.yml` (and `tools/` for their APIs).
+     `vatio.yml` (and `tools/` for their APIs, with one that alerts their
+     team when a person should take over: **Human in the loop** in the docs).
   3. `vatio diff`, `vatio push`, then try it with `vatio chat`, including a
      conversation that should hand off.
   4. Give them what `vatio push` printed, with what you tried. With no
@@ -54,7 +55,7 @@ you recommend, and ask them to confirm.
      `Try it:` is the inbox's Test page, with web chat, WhatsApp and
      Instagram. Publish with `vatio publish` only when they ask.
   5. Once they have tried it, offer to put it in the app (the web widget,
-     or the iOS or Android SDK) with the `vatio-add-to-app` skill. A trial
+     or the iOS, Android or Flutter SDK) with the `vatio-add-to-app` skill. A trial
      has to be kept first.
 - **A `vatio.yml`: the agent exists.** Never `vatio init` here: it writes a
   starter agent, and pushing that replaces the real one. Work from the