@vellumai/assistant 0.4.37 → 0.4.41

package/src/config/bundled-skills/agentmail/SKILL.md

@@ -10,7 +10,7 @@ metadata: {"vellum": {"emoji": "📬"}}
 `vellum` is your own CLI binary — it is already installed and available on the PATH.
 Run all commands via `bash`. Do NOT attempt to install, build, or locate the CLI — just execute it directly.
 
-Example: `bash("vellum email status --json")`
+Example: `bash("assistant email status --json")`
 
 Never use browser/computer-use unless user explicitly approves fallback.
 
@@ -20,8 +20,8 @@ This skill manages the **assistant's own** AgentMail address (`@agentmail.to`)
 
 ## Rules
 
-- Always run `vellum email` commands via `bash` and parse JSON output.
-- Always do `vellum email status --json` preflight first.
+- Always run `assistant email` commands via `bash` and parse JSON output.
+- Always do `assistant email status --json` preflight first.
 - Prefer `draft create` before any send — never bypass draft flow.
 - Require explicit user confirmation before `draft approve-send --confirm`.
 - When uncertain, draft to ops@ inbox and notify user.
@@ -29,7 +29,7 @@ This skill manages the **assistant's own** AgentMail address (`@agentmail.to`)
 
 ## API Key Setup
 
-If `vellum email status --json` returns an error about a missing API key, prompt the user for their AgentMail API key using the secure credential prompt. **Never ask the user to paste the key in chat.**
+If `assistant email status --json` returns an error about a missing API key, prompt the user for their AgentMail API key using the secure credential prompt. **Never ask the user to paste the key in chat.**
 
 Use `credential_store` with:
 - action: `prompt`
@@ -41,14 +41,14 @@ Use `credential_store` with:
 - allowed_tools: `["bash"]`
 - usage_description: `AgentMail email operations via vellum CLI`
 
-After the credential is stored, retry `vellum email status --json` to confirm it works.
+After the credential is stored, retry `assistant email status --json` to confirm it works.
 
 ## Workflow
 
-1. **Preflight:** `vellum email status --json` (if API key error, run API Key Setup above)
-2. **Quick inbox:** `vellum email inbox create --username <name>` (creates e.g. sam@agentmail.to — no custom domain needed)
+1. **Preflight:** `assistant email status --json` (if API key error, run API Key Setup above)
+2. **Quick inbox:** `assistant email inbox create --username <name>` (creates e.g. sam@agentmail.to — no custom domain needed)
 3. **Custom domain setup (optional):** domain -> dns -> verify -> inboxes -> webhook
-4. **Draft path:** `vellum email draft create ...` — always draft first
+4. **Draft path:** `assistant email draft create ...` — always draft first
 5. **Send path:** show draft -> user confirms -> `draft approve-send --draft-id <id> --confirm`
 6. **Inbound triage:** list -> get -> summarize -> propose reply draft
 7. **Guardrails:** check with `guardrails get`, use `guardrails set` to change
@@ -58,67 +58,67 @@ After the credential is stored, retry `vellum email status --json` to confirm it
 ### Provider
 
 ```
-vellum email provider get [--json]                         # Show active provider
-vellum email provider set <provider> [--json]               # Switch provider
+assistant email provider get [--json]                         # Show active provider
+assistant email provider set <provider> [--json]               # Switch provider
 ```
 
 ### Status
 
 ```
-vellum email status [--json]                               # Provider health + guardrails
+assistant email status [--json]                               # Provider health + guardrails
 ```
 
 ### Inbox Management
 
 ```
-vellum email inbox create --username <name> [--domain <d>] [--display-name <n>] [--json]   # Create a new inbox (e.g. --username sam)
-vellum email inbox list [--json]                                                            # List all inboxes
+assistant email inbox create --username <name> [--domain <d>] [--display-name <n>] [--json]   # Create a new inbox (e.g. --username sam)
+assistant email inbox list [--json]                                                            # List all inboxes
 ```
 
 ### Setup
 
 ```
-vellum email setup domain --domain <d> [--dry-run] [--json]
-vellum email setup dns --domain <d> [--json]
-vellum email setup verify --domain <d> [--json]
-vellum email setup inboxes --domain <d> [--json]                                            # Creates standard hello@/support@/ops@ inboxes
-vellum email setup webhook --url <u> [--secret <s>] [--json]
+assistant email setup domain --domain <d> [--dry-run] [--json]
+assistant email setup dns --domain <d> [--json]
+assistant email setup verify --domain <d> [--json]
+assistant email setup inboxes --domain <d> [--json]                                            # Creates standard hello@/support@/ops@ inboxes
+assistant email setup webhook --url <u> [--secret <s>] [--json]
 ```
 
 ### Drafts
 
 ```
-vellum email draft create --from <addr> --to <addr> --subject <s> --body <b> [--cc <addr>] [--in-reply-to <msg-id>] [--json]
-vellum email draft list [--status pending|approved|sent|rejected] [--json]
-vellum email draft get <draft-id> [--json]
-vellum email draft approve-send --draft-id <id> --confirm [--json]
-vellum email draft reject --draft-id <id> [--reason <text>] [--json]
-vellum email draft delete <draft-id> [--json]
+assistant email draft create --from <addr> --to <addr> --subject <s> --body <b> [--cc <addr>] [--in-reply-to <msg-id>] [--json]
+assistant email draft list [--status pending|approved|sent|rejected] [--json]
+assistant email draft get <draft-id> [--json]
+assistant email draft approve-send --draft-id <id> --confirm [--json]
+assistant email draft reject --draft-id <id> [--reason <text>] [--json]
+assistant email draft delete <draft-id> [--json]
 ```
 
 ### Inbound
 
 ```
-vellum email inbound list [--thread-id <id>] [--json]
-vellum email inbound get <message-id> [--json]
+assistant email inbound list [--thread-id <id>] [--json]
+assistant email inbound get <message-id> [--json]
 ```
 
 ### Threads
 
 ```
-vellum email thread list [--json]
-vellum email thread get <thread-id> [--json]
+assistant email thread list [--json]
+assistant email thread get <thread-id> [--json]
 ```
 
 ### Guardrails
 
 ```
-vellum email guardrails get [--json]
-vellum email guardrails set --paused <true|false> --daily-cap <n> [--json]
-vellum email guardrails block <pattern> [--json]
-vellum email guardrails allow <pattern> [--json]
-vellum email guardrails rules [--json]
-vellum email guardrails unrule <rule-id> [--json]
+assistant email guardrails get [--json]
+assistant email guardrails set --paused <true|false> --daily-cap <n> [--json]
+assistant email guardrails block <pattern> [--json]
+assistant email guardrails allow <pattern> [--json]
+assistant email guardrails rules [--json]
+assistant email guardrails unrule <rule-id> [--json]
 ```
 
 ## Output Format

package/src/config/bundled-skills/amazon/SKILL.md

@@ -5,45 +5,45 @@ user-invocable: true
 metadata: { "vellum": { "emoji": "\uD83D\uDCE6" } }
 ---
 
-You can shop on Amazon (and Amazon Fresh for groceries) for the user using the `vellum amazon` CLI.
+You can shop on Amazon (and Amazon Fresh for groceries) for the user using the `assistant amazon` CLI.
 
 ## CLI Setup
 
-**IMPORTANT: Always use `host_bash` (not `bash`) for all `vellum amazon` commands.** The Amazon CLI needs host access for session cookies and the `vellum` binary — neither of which are available inside the sandbox.
+**IMPORTANT: Always use `host_bash` (not `bash`) for all `assistant amazon` commands.** The Amazon CLI needs host access for session cookies and the `vellum` binary — neither of which are available inside the sandbox.
 
-`vellum amazon` is a built-in subcommand of the Vellum assistant CLI — it is NOT a separate tool you need to find or install. It should already be on your PATH. If `vellum` is not found, prepend `PATH="$HOME/.local/bin:$PATH"` to the command. Do NOT search for the binary, inspect wrapper scripts, or try to discover how the CLI works. Just run the commands as documented below.
+`assistant amazon` is a built-in subcommand of the Vellum assistant CLI — it is NOT a separate tool you need to find or install. It should already be on your PATH. If `vellum` is not found, prepend `PATH="$HOME/.local/bin:$PATH"` to the command. Do NOT search for the binary, inspect wrapper scripts, or try to discover how the CLI works. Just run the commands as documented below.
 
 ## Typical Flow — Regular Amazon Shopping
 
 When the user asks you to order something from Amazon:
 
-1. **Check session** — run `vellum amazon status --json`. If `loggedIn` is false or the session is expired, tell the user: "A Chrome window will open to the Amazon login page. Please sign in there — I'll detect your login automatically and minimize the window." Then run `vellum amazon refresh --json`. This starts a Ride Shotgun learn session that records your login and auto-stops once it detects you've signed in. The session is imported automatically. **This command blocks until login is complete — just wait for it.**
+1. **Check session** — run `assistant amazon status --json`. If `loggedIn` is false or the session is expired, tell the user: "A Chrome window will open to the Amazon login page. Please sign in there — I'll detect your login automatically and minimize the window." Then run `assistant amazon refresh --json`. This starts a Ride Shotgun learn session that records your login and auto-stops once it detects you've signed in. The session is imported automatically. **This command blocks until login is complete — just wait for it.**
 
-2. **Search** — run `vellum amazon search "<query>" --json` to find matching products. Present the top results with ASIN, title, price, and Prime status. If the user named a specific product, pick the best match. If ambiguous, ask.
+2. **Search** — run `assistant amazon search "<query>" --json` to find matching products. Present the top results with ASIN, title, price, and Prime status. If the user named a specific product, pick the best match. If ambiguous, ask.
 
-3. **Product details** (if needed) — run `vellum amazon product <asin> --json` to get full details including price and variations. For products with variants (size, color, etc.), see the Variations section below.
+3. **Product details** (if needed) — run `assistant amazon product <asin> --json` to get full details including price and variations. For products with variants (size, color, etc.), see the Variations section below.
 
-4. **Add to cart** — run `vellum amazon cart add --asin <asin> [--quantity <n>] --json`. The response includes the updated cart with all items.
+4. **Add to cart** — run `assistant amazon cart add --asin <asin> [--quantity <n>] --json`. The response includes the updated cart with all items.
 
-5. **Review cart** — run `vellum amazon cart view --json` and show the user what's in their cart with prices. Ask if they want to add anything else or proceed.
+5. **Review cart** — run `assistant amazon cart view --json` and show the user what's in their cart with prices. Ask if they want to add anything else or proceed.
 
-6. **Payment methods** — run `vellum amazon payment-methods --json` to see saved cards.
+6. **Payment methods** — run `assistant amazon payment-methods --json` to see saved cards.
 
-7. **Checkout summary** — run `vellum amazon checkout --json` to get order totals (subtotal, shipping, tax, total).
+7. **Checkout summary** — run `assistant amazon checkout --json` to get order totals (subtotal, shipping, tax, total).
 
-8. **Place order** — after the user explicitly confirms, run `vellum amazon order place [--payment-method-id <id>] --json`. The response contains `orderId` on success.
+8. **Place order** — after the user explicitly confirms, run `assistant amazon order place [--payment-method-id <id>] --json`. The response contains `orderId` on success.
 
 ## Typical Flow — Amazon Fresh Groceries
 
 Amazon Fresh delivers groceries. The flow is the same as regular Amazon, with these additions:
 
-1. **Search Fresh** — use the `--fresh` flag: `vellum amazon search "<query>" --fresh --json`
+1. **Search Fresh** — use the `--fresh` flag: `assistant amazon search "<query>" --fresh --json`
 
-2. **Add Fresh items** — use the `--fresh` flag: `vellum amazon cart add --asin <asin> --fresh --json`
+2. **Add Fresh items** — use the `--fresh` flag: `assistant amazon cart add --asin <asin> --fresh --json`
 
 3. **Select delivery slot** — Fresh orders require a delivery window:
-   - `vellum amazon fresh delivery-slots --json` — list available slots
-   - `vellum amazon fresh select-slot --slot-id <id> --json` — select a slot
+   - `assistant amazon fresh delivery-slots --json` — list available slots
+   - `assistant amazon fresh select-slot --slot-id <id> --json` — select a slot
    - Do this BEFORE checkout.
 
 4. **Checkout and order** — same as regular Amazon.
@@ -52,76 +52,76 @@ Amazon Fresh delivers groceries. The flow is the same as regular Amazon, with th
 
 Many Amazon products (clothing, electronics) have variations (size, color, style):
 
-1. Run `vellum amazon product <asin> --json` to get the product and its `variations[]` array
+1. Run `assistant amazon product <asin> --json` to get the product and its `variations[]` array
 2. Each variation has: `dimensionName` (e.g. "size"), `value` (e.g. "Large"), `asin` (child ASIN), `isAvailable`, `priceValue`
-3. Use the child ASIN when adding to cart: `vellum amazon cart add --asin <child-asin> --json`
+3. Use the child ASIN when adding to cart: `assistant amazon cart add --asin <child-asin> --json`
 
-Alternatively, run `vellum amazon variations <asin> --json` to list just the variations.
+Alternatively, run `assistant amazon variations <asin> --json` to list just the variations.
 
 ## Important Behavior
 
 - **Always confirm before placing order.** Never call `order place` without explicit user approval. Show the cart and total first.
 - **Be proactive.** If the user says "order AA batteries", don't ask clarifying questions upfront — search, find the product, and suggest it. Only ask when you need a choice the user hasn't specified.
-- **Handle expired sessions gracefully.** If any command returns `"error": "session_expired"`, run `vellum amazon refresh --json` to re-capture the session.
+- **Handle expired sessions gracefully.** If any command returns `"error": "session_expired"`, run `assistant amazon refresh --json` to re-capture the session.
 - **Handle extension errors.** If a command fails with a message about the browser extension not being connected, tell the user: "Please open Chrome, click the Vellum extension icon, and click Connect — then I'll retry." Do NOT try to interact with the relay directly.
 - **Show prices.** Always show prices when presenting products or the cart summary.
 - **Use `--json` flag** on all commands for reliable parsing.
 - **Do NOT use the browser skill.** All Amazon interaction goes through the CLI, not browser automation.
 - **Rate limiting.** Amazon may rate-limit rapid sequential requests. Wait 8–10 seconds between cart operations. If you get a 403 error, wait 15–20 seconds and retry.
-- **Always-allow tip.** At the start of an ordering flow, suggest the user enable "always allow" for `vellum amazon` commands: "Tip: You can type 'a' to always allow `vellum amazon` commands for this session so you won't be prompted each time."
-- **Fresh slot required.** Amazon Fresh orders require a delivery slot to be selected before checkout. If the user skips this step, remind them to run `vellum amazon fresh delivery-slots --json` and select a slot.
+- **Always-allow tip.** At the start of an ordering flow, suggest the user enable "always allow" for `assistant amazon` commands: "Tip: You can type 'a' to always allow `assistant amazon` commands for this session so you won't be prompted each time."
+- **Fresh slot required.** Amazon Fresh orders require a delivery slot to be selected before checkout. If the user skips this step, remind them to run `assistant amazon fresh delivery-slots --json` and select a slot.
 
 ## Command Reference
 
 ```
-vellum amazon status --json                     # Check if logged in
-vellum amazon refresh --json                    # Capture fresh session via Ride Shotgun
-vellum amazon login --recording <path>          # Import session from a recording file
-vellum amazon logout                            # Clear session
+assistant amazon status --json                     # Check if logged in
+assistant amazon refresh --json                    # Capture fresh session via Ride Shotgun
+assistant amazon login --recording <path>          # Import session from a recording file
+assistant amazon logout                            # Clear session
 
-vellum amazon search "<query>" [--fresh] [--limit <n>] --json
-vellum amazon product <asin> [--fresh] --json
-vellum amazon variations <asin> --json
+assistant amazon search "<query>" [--fresh] [--limit <n>] --json
+assistant amazon product <asin> [--fresh] --json
+assistant amazon variations <asin> --json
 
-vellum amazon cart view --json
-vellum amazon cart add --asin <asin> [--quantity <n>] [--fresh] --json
-vellum amazon cart remove --cart-item-id <id> --json
+assistant amazon cart view --json
+assistant amazon cart add --asin <asin> [--quantity <n>] [--fresh] --json
+assistant amazon cart remove --cart-item-id <id> --json
 
-vellum amazon fresh delivery-slots --json
-vellum amazon fresh select-slot --slot-id <id> --json
+assistant amazon fresh delivery-slots --json
+assistant amazon fresh select-slot --slot-id <id> --json
 
-vellum amazon payment-methods --json
-vellum amazon checkout --json
-vellum amazon order place [--payment-method-id <id>] --json
+assistant amazon payment-methods --json
+assistant amazon checkout --json
+assistant amazon order place [--payment-method-id <id>] --json
 ```
 
 ## Example Interactions
 
 **User**: "Order a pack of AA batteries from Amazon"
 
-1. `vellum amazon status --json` → logged in
-2. `vellum amazon search "AA batteries" --json` → finds products
+1. `assistant amazon status --json` → logged in
+2. `assistant amazon search "AA batteries" --json` → finds products
 3. Show top results: "Duracell AA 20-pack ($12.99, Prime), Amazon Basics AA 48-pack ($14.49, Prime)..."
-4. User picks Duracell → `vellum amazon cart add --asin B00000J1ER --json`
-5. `vellum amazon cart view --json` → show cart summary
-6. `vellum amazon checkout --json` → show total
+4. User picks Duracell → `assistant amazon cart add --asin B00000J1ER --json`
+5. `assistant amazon cart view --json` → show cart summary
+6. `assistant amazon checkout --json` → show total
 7. "Your cart has 1x Duracell AA Batteries 20-pack ($12.99), total $12.99 with free Prime shipping. Ready to order?"
-8. User confirms → `vellum amazon order place --json`
+8. User confirms → `assistant amazon order place --json`
 
 **User**: "Order a large blue t-shirt from Amazon"
 
-1. `vellum amazon search "blue t-shirt" --json` → finds products
-2. User picks a shirt → `vellum amazon variations <parentAsin> --json` → shows Size + Color combinations
-3. Find the child ASIN for Large + Blue → `vellum amazon cart add --asin <childAsin> --json`
+1. `assistant amazon search "blue t-shirt" --json` → finds products
+2. User picks a shirt → `assistant amazon variations <parentAsin> --json` → shows Size + Color combinations
+3. Find the child ASIN for Large + Blue → `assistant amazon cart add --asin <childAsin> --json`
 
 **User**: "Order milk and eggs from Amazon Fresh"
 
-1. `vellum amazon status --json` → logged in
-2. `vellum amazon search "whole milk" --fresh --json` → Fresh results
-3. `vellum amazon cart add --asin <milkAsin> --fresh --json`
-4. `vellum amazon search "eggs" --fresh --json` → Fresh results
-5. `vellum amazon cart add --asin <eggsAsin> --fresh --json`
-6. `vellum amazon fresh delivery-slots --json` → show available slots
-7. User picks a slot → `vellum amazon fresh select-slot --slot-id <id> --json`
-8. `vellum amazon checkout --json` → show totals
-9. User confirms → `vellum amazon order place --json`
+1. `assistant amazon status --json` → logged in
+2. `assistant amazon search "whole milk" --fresh --json` → Fresh results
+3. `assistant amazon cart add --asin <milkAsin> --fresh --json`
+4. `assistant amazon search "eggs" --fresh --json` → Fresh results
+5. `assistant amazon cart add --asin <eggsAsin> --fresh --json`
+6. `assistant amazon fresh delivery-slots --json` → show available slots
+7. User picks a slot → `assistant amazon fresh select-slot --slot-id <id> --json`
+8. `assistant amazon checkout --json` → show totals
+9. User confirms → `assistant amazon order place --json`

package/src/config/bundled-skills/app-builder/SKILL.md

@@ -25,6 +25,8 @@ You are an expert app builder and visual designer. When the user asks you to cre
 
 **Make creative decisions on behalf of the user.** They want to be delighted, not consulted. Pick the accent color. Choose between a dark moody aesthetic or a light airy one. Decide if cards should have glassmorphism or layered shadows. Add a background pattern or gradient. These are YOUR decisions as the designer.
 
+**Prefer multi-file TSX projects** for any non-trivial app. They give you component reuse, TypeScript safety, and cleaner organization. Fall back to single-file HTML only for the simplest one-off pages.
+
 **Only ask questions when the request is genuinely ambiguous** — e.g., "build me an app" with no indication of what kind. Even then, prefer building something impressive based on context clues over asking a battery of questions.
 
 **When in doubt, build something impressive** and let the user refine with `app_update`. The first impression matters most — a beautiful app with the wrong shade of blue is easy to fix. A correct but ugly app is hard to come back from.
@@ -65,11 +67,143 @@ Example schema for a project tracker:
 }
 ```
 
-### 3. Build the HTML Interface
+### 3. Build the App
+
+Apps are rendered inside a sandboxed WebView on macOS. You can build them in two formats: **multi-file TSX** (preferred) or **single-file HTML** (legacy).
+
+#### Multi-file TSX projects (preferred)
+
+Use this format for any non-trivial app. You get component reuse, TypeScript type-checking, and clean file organization. The build system uses esbuild to bundle everything automatically.
+
+**Project structure:**
+
+```
+src/
+  index.html          # Entry HTML — minimal shell, loads compiled bundle
+  main.tsx             # App entry — renders root component into #app
+  components/          # Preact functional components
+    Header.tsx
+    RecordList.tsx
+    ...
+  styles.css           # Global styles (imported from TSX)
+```
+
+**Preact usage:**
+
+```tsx
+import { render } from "preact";
+import { useState, useEffect } from "preact/hooks";
+import { App } from "./components/App";
+
+render(<App />, document.getElementById("app")!);
+```
+
+Functional components with hooks:
+
+```tsx
+import { FunctionComponent } from "preact";
+
+interface Props {
+  title: string;
+  count: number;
+}
+
+export const Header: FunctionComponent<Props> = ({ title, count }) => {
+  return (
+    <header>
+      <h1>{title}</h1>
+      <span className="badge">{count}</span>
+    </header>
+  );
+};
+```
+
+**TypeScript:** Use types for props, state, and data records. Define shared types in a `types.ts` file when multiple components need them.
+
+**CSS:** Import CSS files directly in TSX (`import './styles.css'`). You can also use inline styles via the `style` attribute on JSX elements.
+
+**Data bridge:** The same `window.vellum.data` API works in TSX components — call it from `useEffect` hooks or event handlers:
+
+```tsx
+const [records, setRecords] = useState<Record[]>([]);
+
+useEffect(() => {
+  window.vellum.data.query().then(setRecords).catch(console.error);
+}, []);
+```
+
+**File workflow:** Use `app_file_write` for each source file. The build happens automatically when you call `app_open`.
+
+**Allowed third-party packages:** `date-fns`, `chart.js`, `lodash-es`, `zod`, `clsx`, `lucide`. Import them directly — esbuild resolves them at build time. No CDN imports. Note: `lucide` is the vanilla JS icon library (not `lucide-react`). Use its `createElement` or `createIcons` API, or manually inline SVG — do not import JSX icon components.
+
+**Example — creating a multi-file project:**
+
+```
+app_file_write(app_id, "src/index.html", `<!DOCTYPE html>
+<html lang="en">
+<head><meta charset="UTF-8"><meta name="viewport" content="width=device-width, initial-scale=1.0">
+<title>Project Tracker</title></head>
+<body><div id="app"></div></body>
+</html>`)
+
+app_file_write(app_id, "src/main.tsx", `import { render } from 'preact';
+import { App } from './components/App';
+import './styles.css';
+
+render(<App />, document.getElementById('app')!);`)
+
+app_file_write(app_id, "src/components/App.tsx", `import { FunctionComponent } from 'preact';
+import { useState, useEffect } from 'preact/hooks';
+import { Header } from './Header';
+
+export const App: FunctionComponent = () => {
+  const [records, setRecords] = useState([]);
+
+  useEffect(() => {
+    window.vellum.data.query().then(setRecords);
+  }, []);
+
+  return (
+    <div className="app">
+      <Header title="Project Tracker" count={records.length} />
+      {/* ... */}
+    </div>
+  );
+};`)
+
+app_file_write(app_id, "src/components/Header.tsx", `import { FunctionComponent } from 'preact';
+
+interface HeaderProps {
+  title: string;
+  count: number;
+}
+
+export const Header: FunctionComponent<HeaderProps> = ({ title, count }) => (
+  <header className="header">
+    <h1>{title}</h1>
+    <span className="badge">{count} items</span>
+  </header>
+);`)
+
+app_file_write(app_id, "src/styles.css", `.app { padding: var(--v-spacing-lg); }
+.header { display: flex; justify-content: space-between; align-items: center; }
+.badge { background: var(--v-accent); color: white; padding: var(--v-spacing-xs) var(--v-spacing-sm); border-radius: var(--v-radius-pill); }`)
+```
+
+**Technical constraints (multi-file):**
+
+- No CDN imports — use esbuild-resolved packages from the allowlist above
+- Preact for UI (not React) — `import { render } from 'preact'`
+- TypeScript encouraged for all `.tsx`/`.ts` files
+- No external fonts, images, or resources — use system fonts and CSS/SVG for visuals
+- Design for 400-600px width with graceful resizing
+- The WebView blocks all navigation — links and form `action` attributes won't work
+
+#### Single HTML file (legacy)
 
-Write a complete, self-contained HTML document rendered inside a sandboxed WebView on macOS.
+Use this format only for the simplest one-off pages. Write a complete, self-contained HTML document.
 
-#### Technical constraints
+**Technical constraints (single-file):**
 
 - Single HTML string — no external files, CDNs, or imports
 - All CSS in `<style>` in `<head>`, all JavaScript in `<script>` before `</body>`

package/src/config/bundled-skills/app-builder/tools/app-create.ts

@@ -1,3 +1,5 @@
+import { isAssistantFeatureFlagEnabled } from "../../../../config/assistant-feature-flags.js";
+import { getConfig } from "../../../../config/loader.js";
 import * as appStore from "../../../../memory/app-store.js";
 import type { AppCreateInput } from "../../../../tools/apps/executors.js";
 import { executeAppCreate } from "../../../../tools/apps/executors.js";
@@ -10,9 +12,13 @@ export async function run(
   input: Record<string, unknown>,
   context: ToolContext,
 ): Promise<ToolExecutionResult> {
-  return executeAppCreate(
-    input as unknown as AppCreateInput,
-    appStore,
-    context.proxyToolResolver,
+  const multifileEnabled = isAssistantFeatureFlagEnabled(
+    "feature_flags.app-builder-multifile.enabled",
+    getConfig(),
   );
+  const createInput: AppCreateInput = {
+    ...(input as unknown as AppCreateInput),
+    featureFlags: { multifileEnabled },
+  };
+  return executeAppCreate(createInput, appStore, context.proxyToolResolver);
 }

package/src/config/bundled-skills/configure-settings/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: "Configure Settings"
-description: "Read, update, or reset assistant configuration values using the vellum config CLI"
+description: "Read, update, or reset assistant configuration values using the assistant config CLI"
 user-invocable: true
 metadata: { "vellum": { "emoji": "⚙️" } }
 ---
@@ -9,29 +9,29 @@ You are helping the user view or change assistant configuration through the `vel
 
 ## Domain Status Reads First
 
-When a user asks for setup/status of a specific capability, prefer domain commands before generic `vellum config get`:
+When a user asks for setup/status of a specific capability, prefer domain commands before generic `assistant config get`:
 
 ```bash
-vellum integrations voice config --json
-vellum integrations ingress config --json
-vellum integrations twilio config --json
-vellum email status --json
+assistant integrations voice config --json
+assistant integrations ingress config --json
+assistant integrations twilio config --json
+assistant email status --json
 ```
 
-Use `vellum config get` for generic keys that do not have a domain command.
+Use `assistant config get` for generic keys that do not have a domain command.
 
 ## Reading a value
 
 ```bash
-vellum config get <key>
+assistant config get <key>
 ```
 
 Examples:
 
 ```bash
-vellum config get platform.baseUrl
-vellum config get memory.qdrant.url
-vellum config get provider
+assistant config get platform.baseUrl
+assistant config get memory.qdrant.url
+assistant config get provider
 ```
 
 If the result is empty, the compiled default is in effect.
@@ -39,16 +39,16 @@ If the result is empty, the compiled default is in effect.
 ## Setting a value
 
 ```bash
-vellum config set <key> <value>
+assistant config set <key> <value>
 ```
 
 Examples:
 
 ```bash
-vellum config set platform.baseUrl "https://platform.vellum.ai"
-vellum config set provider "openai"
-vellum config set memory.enabled false
-vellum config set maxTokens 8000
+assistant config set platform.baseUrl "https://platform.vellum.ai"
+assistant config set provider "openai"
+assistant config set memory.enabled false
+assistant config set maxTokens 8000
 ```
 
 ## Resetting a value to its default
@@ -56,13 +56,13 @@ vellum config set maxTokens 8000
 Set the key to an empty string (for strings) or omit it from the config file:
 
 ```bash
-vellum config set <key> ""
+assistant config set <key> ""
 ```
 
 ## Listing all configuration
 
 ```bash
-vellum config list
+assistant config list
 ```
 
 ## Common configuration keys