@agent-native/core 0.79.27 → 0.80.1

package/docs/content/locales/zh-CN/template-design.mdx

@@ -338,7 +338,7 @@ UI 中的路由位于 `templates/design/app/routes/` 下：`_index.tsx`（列表
 - **设计** - `create-design`（空壳）、`generate-design`（写入生成的 HTML/JSX 内容）、`update-design`、`get-design`、`list-designs`、`duplicate-design`、`delete-design` 和 `apply-tweaks` 用于持久保存实时调整旋钮值（强调色、密度等）。
 - **文件** - `create-file`、`update-file`、`list-files`、`delete-file` 用于设计项目内的文件。
 - **设计系统** - `create-design-system`、`update-design-system`、`get-design-system`、`list-design-systems`、`delete-design-system`、`set-default-design-system` 和 `analyze-brand-assets` 用于在分析之前收集品牌数据。
-- **导入** - `import-code`、`import-figma`、`import-github`、`import-from-url`、`import-document` (DOCX/PPTX/PDF/XLSX) 和 `import-design-project` 将设计系统从现有项目中提升出来。
+- **导入** — `index-design-system-with-builder` for Builder-backed code/GitHub design-system indexing, plus `import-figma`, `import-from-url`, `import-document` (DOCX/PPTX/PDF/XLSX), and `import-design-project` for other sources.
 - **导出和移交** - `export-html`、`export-pdf`、`export-svg`、`export-zip` 和 `export-coding-handoff` 将设计转变为编码工具移交。
 - **上下文和导航** - `view-screen`（当前设计、打开的文件、视图、待决问题或变体网格）、`get-design-snapshot`（外部代理继续的当前状态）和 `navigate`。
 
@@ -348,6 +348,55 @@ UI 中的路由位于 `templates/design/app/routes/` 下：`_index.tsx`（列表
 
 因为设计只是独立的 HTML/JSX 文件，所以代理编辑 iframe 渲染和每个导出来自的相同源 - 没有单独的“AI 模型”格式需要翻译。链接设计系统提供代币和代理在每一代通行证上兑现的 `custom_instructions`。在预览中选择文本或区域，然后按 Cmd+I 将代理集中在该部分上。
 
+### 编辑器模型
+
+Design 对多屏工作采用概览优先。生成或进行大范围更新后，编辑器会打开屏幕
+概览：一个无限画布，其中每个屏幕都是可选择、移动、调整大小、拖放或复制的
+静态框架。需要聚焦滚动或原型交互时，请使用框架的完整视图按钮。
+
+单屏模式用于滚动、与原型行为交互，以及编辑一个已渲染文件内的 DOM/代码
+层。图层面板也反映这种分工：屏幕是顶层框架，活动屏幕下嵌套 DOM/代码层。
+
+当编码代理需要在 Design 中打开正在运行的本地应用，而不是生成独立原型 HTML
+时，请安装 `/visual-edit`：
+
+```bash
+npx @agent-native/core@latest skills add visual-edit
+```
+
+目标应用的开发服务器运行后，`/visual-edit` 会结合
+`npx @agent-native/core@latest design connect` 和 `add-localhost-screens`，把每个
+请求的 path 或 URL 放置为独立的 URL-backed iframe 屏幕。像
+`localhost:1234/onboarding/1`、`/onboarding/2`、`/onboarding/3` 这样的编号流程
+会在 overview 模式中保持为分开的有序屏幕。
+
+为了获得稳定的图层名称，请在有意义的元素上添加
+`data-agent-native-layer-name`。Design 会优先使用它，然后才使用语义/文本回
+退，并且可以通过编辑该属性来持久保存图层重命名。Inline HTML 支持本地代
+码层编辑，包括文本、class、style、attribute、源顺序和小型结构调整；可视
+代码层编辑目前仅支持 HTML。Localhost source mode 可以注册并解析本地路由
+artboard，但本地文件读写仍是桥接合同，直到显式权限控制完成加固。
+
+### Design 编辑器扩展
+
+编辑器在 **Tweaks** 之后包含一个 **Extensions** 检查器标签。它像 Design
+专属的插件通道：用户可以点击 **+ Extension** 让代理创建扩展，也可以安装声
+明 `design.editor.inspector` slot 的扩展。
+
+Design 扩展通过标准扩展 sandbox 内嵌渲染在 artboard 旁边。宿主会通过
+`window.slotContext` 和 `window.onSlotContext(...)` 更新传入当前
+`designId`、活动文件、屏幕列表、已选屏幕 id、已选元素元数据、视图模式、
+缩放、活动工具和 tweak 值。这样扩展就可以显示当前选择的信息、提供样式控
+件，或围绕打开的设计构建紧凑工作流。
+
+对于确定性的工作，扩展可以通过扩展桥调用 app actions。对于 AI 驱动的变
+更，让扩展调用 `agentNative.chat.send(...)`，并附带已选元素的 selector/source
+id 和请求的更改。代理应先调用 `view-screen`，然后用 `apply-visual-edit`
+处理元素 style、class、text 或 move 更改，或用带 `canvasFrames` 的
+`update-design` / `generate-design` 处理 artboard placement 更改。有关
+sandbox、持久状态和桥接 API，请参阅
+[Extensions](/docs/extensions#what-an-extension-can-do)。
+
 ### 自定义它
 
 设计是一个完整的、可克隆的模板。一些实用的扩展想法：

package/docs/content/locales/zh-TW/skills-guide.mdx

@@ -118,6 +118,10 @@ Skills 位於 `.agents/skills/<name>/SKILL.md`，包含針對代理的詳細指
 
 ## 應用程式支援的 skills {#app-backed-skills}
 
+目前應用支援的 skills 包括 Plan 的 `visual-plan` 和 `visual-recap`、Design
+的 `visual-edit`、Assets 的 `assets`，以及用於儲存庫內 docs/blog/MDX 編輯的
+`content`。
+
 應用程式支援的 skills 將 Agent-Native 應用程式打包為技能市場工件。該捆綁包可以包含代理指令、匯出的 skills、MCP 連線器中繼資料、託管/本機啟動指令和 UI 表面（例如 MCP 應用程式）。
 
 > **完整詳細資訊如下：** [App-backed skills — full details](#app-backed-skills-full) 中介紹了應用程式支援的 skills 的機制（清單格式、CLI 指令、市場轉接器、自動更新哈希）。
@@ -328,6 +332,7 @@ Hosted 是預設安裝路徑。本機啟動是明確的定制，
 ```bash
 # 愉快的路徑：匯出的指令加上託管的 MCP 連線器。
 npx @agent-native/core@latest skills add visual-plan
+npx @agent-native/core@latest skills add visual-edit
 npx @agent-native/core@latest skills add assets
 
 # 回購優先內容 docs/blog/MDX 編輯。

package/docs/content/locales/zh-TW/template-design.mdx

@@ -338,7 +338,7 @@ UI 中的路由位於 `templates/design/app/routes/` 下：`_index.tsx`（清單
 - **設計** - `create-design`（空殼）、`generate-design`（寫入產生的 HTML/JSX 內容）、`update-design`、`get-design`、`list-designs`、`duplicate-design`、`delete-design` 和 `apply-tweaks` 用於持久儲存即時調整旋鈕值（強調色、密度等）。
 - **檔案** - `create-file`、`update-file`、`list-files`、`delete-file` 用於設計專案內的檔案。
 - **設計系統** - `create-design-system`、`update-design-system`、`get-design-system`、`list-design-systems`、`delete-design-system`、`set-default-design-system` 和 `analyze-brand-assets` 用於在分析之前收集品牌資料。
-- **匯入** - `import-code`、`import-figma`、`import-github`、`import-from-url`、`import-document` (DOCX/PPTX/PDF/XLSX) 和 `import-design-project` 將設計系統從現有專案中提升出來。
+- **匯入** — `index-design-system-with-builder` for Builder-backed code/GitHub design-system indexing, plus `import-figma`, `import-from-url`, `import-document` (DOCX/PPTX/PDF/XLSX), and `import-design-project` for other sources.
 - **匯出和移交** - `export-html`、`export-pdf`、`export-svg`、`export-zip` 和 `export-coding-handoff` 將設計轉變為編碼工具移交。
 - **脈絡和導覽** - `view-screen`（目前設計、開啟的檔案、檢視、待決問題或變體網格）、`get-design-snapshot`（外部代理繼續的目前狀態）和 `navigate`。
 
@@ -348,6 +348,57 @@ UI 中的路由位於 `templates/design/app/routes/` 下：`_index.tsx`（清單
 
 因為設計只是獨立的 HTML/JSX 檔案，所以代理編輯 iframe 渲染和每個匯出來自的相同來源 - 沒有單獨的“AI 模型”格式需要翻譯。連結設計系統提供代幣和代理在每一代通行證上兌現的 `custom_instructions`。在預覽中選取文字或區域，然後按 Cmd+I 將代理集中在該部分上。
 
+### 編輯器模型
+
+Design 對多畫面工作採用概覽優先。產生或進行大範圍更新後，編輯器會開啟
+畫面概覽：一個無限畫布，其中每個畫面都是可選取、移動、調整大小、拖放或
+複製的靜態框架。需要聚焦捲動或原型互動時，請使用框架的完整檢視按鈕。
+
+單畫面模式用於捲動、與原型行為互動，以及編輯一個已渲染檔案內的 DOM/程
+式碼圖層。圖層面板也反映這種分工：畫面是頂層框架，作用中畫面下嵌套
+DOM/程式碼圖層。
+
+當編碼代理需要在 Design 中開啟正在執行的本機應用，而不是產生獨立原型 HTML
+時，請安裝 `/visual-edit`：
+
+```bash
+npx @agent-native/core@latest skills add visual-edit
+```
+
+目標應用的開發伺服器執行後，`/visual-edit` 會結合
+`npx @agent-native/core@latest design connect` 和 `add-localhost-screens`，把每個
+要求的 path 或 URL 放置為獨立的 URL-backed iframe 畫面。像
+`localhost:1234/onboarding/1`、`/onboarding/2`、`/onboarding/3` 這樣的編號流程
+會在 overview 模式中保持為分開的有序畫面。
+
+若要取得穩定的圖層名稱，請在有意義的元素上加入
+`data-agent-native-layer-name`。Design 會優先使用它，然後才使用語意/文字
+後備，並且可以透過編輯該屬性來持久保存圖層重新命名。Inline HTML 支援本
+機程式碼圖層編輯，包括文字、class、style、attribute、來源順序和小型結構
+調整；視覺程式碼圖層編輯目前僅支援 HTML。Localhost source mode 可以註冊
+並解析本機路由 artboard，但本機檔案讀寫仍是橋接合約，直到明確權限控制
+完成加固。
+
+### Design 編輯器擴充功能
+
+編輯器在 **Tweaks** 之後包含一個 **Extensions** 檢查器標籤。它像 Design
+專屬的外掛通道：使用者可以點擊 **+ Extension** 讓代理建立擴充功能，也可
+以安裝宣告 `design.editor.inspector` slot 的擴充功能。
+
+Design 擴充功能會透過標準擴充 sandbox 內嵌渲染在 artboard 旁邊。host 會
+透過 `window.slotContext` 和 `window.onSlotContext(...)` 更新傳入目前的
+`designId`、作用中檔案、畫面清單、已選畫面 id、已選元素中繼資料、檢視模
+式、縮放、作用中工具和 tweak 值。這讓擴充功能可以顯示目前選取項目的資
+訊、提供樣式控制，或圍繞開啟的設計建立精簡工作流程。
+
+對於確定性的工作，擴充功能可以透過擴充橋接呼叫 app actions。對於 AI 驅
+動的變更，讓擴充功能呼叫 `agentNative.chat.send(...)`，並附上已選元素的
+selector/source id 和要求的變更。代理應先呼叫 `view-screen`，再用
+`apply-visual-edit` 處理元素 style、class、text 或 move 變更，或用帶有
+`canvasFrames` 的 `update-design` / `generate-design` 處理 artboard placement
+變更。關於 sandbox、持久狀態和橋接 API，請參閱
+[Extensions](/docs/extensions#what-an-extension-can-do)。
+
 ### 自訂它
 
 設計是一個完整的、可克隆的範本。一些實用的擴充功能想法：

package/docs/content/skills-guide.mdx

@@ -120,6 +120,10 @@ Domain skills follow the same format as framework skills. They encode patterns s
 
 App-backed skills package an agent-native app as a skill marketplace artifact. The bundle can include agent instructions, exported skills, MCP connector metadata, hosted/local launch instructions, and UI surfaces such as MCP Apps.
 
+Current app-backed skills include `visual-plan` and `visual-recap` from Plan,
+`visual-edit` from Design, `assets` from Assets, and `content` for repo-backed
+docs/blog/MDX editing.
+
 > **Full details below:** the mechanics of app-backed skills (manifest format, CLI commands, marketplace adapters, auto-update hashing) are covered in [App-backed skills — full details](#app-backed-skills-full).
 
 ## Creating custom skills {#creating-skills}
@@ -328,6 +332,7 @@ offline work, or privacy-sensitive use.
 ```bash
 # Happy path: exported instructions plus hosted MCP connector.
 npx @agent-native/core@latest skills add visual-plan
+npx @agent-native/core@latest skills add visual-edit
 npx @agent-native/core@latest skills add assets
 
 # Repo-first Content docs/blog/MDX editing.

package/docs/content/template-design.mdx

@@ -338,7 +338,7 @@ Every agent-callable operation is a TypeScript file in `templates/design/actions
 - **Designs** — `create-design` (empty shell), `generate-design` (write generated HTML/JSX content), `update-design`, `get-design`, `list-designs`, `duplicate-design`, `delete-design`, and `apply-tweaks` for persisting live tweak-knob values (accent color, density, etc.).
 - **Files** — `create-file`, `update-file`, `list-files`, `delete-file` for the files inside a design project.
 - **Design systems** — `create-design-system`, `update-design-system`, `get-design-system`, `list-design-systems`, `delete-design-system`, `set-default-design-system`, and `analyze-brand-assets` for gathering brand data ahead of analysis.
-- **Import** — `import-code`, `import-figma`, `import-github`, `import-from-url`, `import-document` (DOCX/PPTX/PDF/XLSX), and `import-design-project` to lift a design system out of an existing project.
+- **Import** — `index-design-system-with-builder` for Builder-backed code/GitHub design-system indexing, plus `import-figma`, `import-from-url`, `import-document` (DOCX/PPTX/PDF/XLSX), and `import-design-project` for other sources.
 - **Export & handoff** — `export-html`, `export-pdf`, `export-svg`, `export-zip`, and `export-coding-handoff` to turn a design into a coding-tool handoff.
 - **Context & navigation** — `view-screen` (current design, open file, view, pending question or variant grid), `get-design-snapshot` (current state for an external agent to continue from), and `navigate`.
 
@@ -348,6 +348,64 @@ The agent always knows what you have open. The current design, the open file, th
 
 Because a design is just standalone HTML/JSX files, the agent edits the same source the iframe renders and every export comes from — there is no separate "AI mockup" format to translate. A linked design system supplies tokens and `custom_instructions` the agent honors on every generation pass. Select text or a region in the preview and hit Cmd+I to focus the agent on exactly that part.
 
+### Editor model
+
+Design is overview-first for multi-screen work. After generation or broad
+updates, the editor opens the screen overview: an infinite canvas where each
+screen is a static frame you can select, move, resize, drop, or duplicate.
+Use a frame's full-view button when one screen needs focused scrolling or
+prototype interaction.
+
+Single-screen mode is for scrolling, interacting with prototype behavior, and
+editing the DOM/code layers inside one rendered file. The layers panel reflects
+that split: screens are top-level frames, with nested DOM/code layers for the
+active screen.
+
+Install `/visual-edit` when a coding agent should open a running local app in
+Design instead of generating standalone prototype HTML:
+
+```bash
+npx @agent-native/core@latest skills add visual-edit
+```
+
+After the target app dev server is running, `/visual-edit` uses
+`npx @agent-native/core@latest design connect` plus `add-localhost-screens` to
+place each requested path or URL as its own URL-backed iframe screen. Numbered
+flows such as `localhost:1234/onboarding/1`, `/onboarding/2`, and
+`/onboarding/3` stay as separate ordered screens in overview mode.
+
+For stable layer names, add `data-agent-native-layer-name` to meaningful
+elements. Design uses it before semantic/text fallbacks and can persist layer
+renames by editing that attribute. Inline HTML supports local code-layer edits
+for text, classes, styles, attributes, source order, and small structural
+changes; visual code-layer edits are HTML-only today. Localhost source mode can
+register and resolve local route artboards, but local file reads/writes remain a
+bridge contract until explicit permission controls are hardened.
+
+### Design editor extensions
+
+The editor includes an **Extensions** inspector tab after **Tweaks**. It works
+like a Design-specific plugin lane: users can click **+ Extension** to ask the
+agent to build an extension, or install an extension that declares the
+`design.editor.inspector` slot.
+
+Design extensions render inline beside the artboard through the standard
+extension sandbox. The host passes `window.slotContext` and
+`window.onSlotContext(...)` updates with the current `designId`, active file,
+screen list, selected screen ids, selected element metadata, view mode, zoom,
+active tool, and tweak values. That lets an extension show information about
+the current selection, offer style controls, or build compact workflows around
+the open design.
+
+For deterministic work, extensions can call app actions through the extension
+bridge. For AI-driven changes, have the extension call
+`agentNative.chat.send(...)` with the selected element selector/source id and
+requested change. The agent should call `view-screen` first, then use
+`apply-visual-edit` for element style, class, text, or move changes, or
+`update-design` / `generate-design` with `canvasFrames` for artboard placement
+changes. See [Extensions](/docs/extensions#what-an-extension-can-do) for the
+sandbox, persistent state, and bridge APIs.
+
 ### Customizing it
 
 Design is a complete, cloneable template. Some practical extension ideas:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.79.27",
+  "version": "0.80.1",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -89,6 +89,7 @@
     "./embedding/react": "./dist/embedding/react.js",
     "./onboarding": "./dist/onboarding/index.js",
     "./shared": "./dist/shared/index.js",
+    "./voice": "./dist/voice/index.js",
     "./scripts": "./dist/scripts/index.js",
     "./application-state": "./dist/application-state/index.js",
     "./settings": "./dist/settings/index.js",

package/src/templates/workspace-core/.agents/skills/voice-transcription/SKILL.md

@@ -86,6 +86,7 @@ Default behavior:
 | `packages/core/src/client/transcription/use-live-transcription.ts`    | Web Speech live-transcription hook for recordings   |
 | `packages/core/src/server/transcribe-voice.ts`                        | Route handler (routes to Builder/Gemini/Groq/Whisper) |
 | `packages/core/src/transcription/builder-transcription.ts`            | Builder proxy transcription client                  |
+| `packages/core/src/voice/`                                            | Shared voice context pack, prompt, and replacement helpers |
 | `packages/core/src/secrets/register-framework-secrets.ts`             | Framework-level provider key registration           |
 
 ## Key resolution (server)
@@ -114,6 +115,15 @@ provider. Gemini uses them in the transcription prompt, Builder receives them
 as transcription/cleanup instructions, and Whisper-compatible providers receive
 them as provider prompt/context.
 
+Requests may also include a multipart `voiceContext` JSON field. Parse it with
+`parseVoiceContextPack()` from `@agent-native/core/voice` and pass the resulting
+context through `buildVoiceGuidanceBlock()`; do not hand-roll separate prompt
+formats. The context pack is for bounded snippets, active references, route/page
+metadata, and preferred vocabulary/replacements only. Browser-native and Google
+realtime final text can POST `{ text, provider, instructions, voiceContext }` to
+`/_agent-native/transcribe-voice` when AI cleanup is enabled; batch audio can
+send the same `voiceContext` field with its audio upload.
+
 Never hardcode a shared key. Never log the value. Never echo it back to the
 client.
 

package/corpus/templates/design/actions/import-figma-file.ts

@@ -1,166 +0,0 @@
-import { defineAction } from "@agent-native/core";
-import {
-  buildImageMap,
-  decodeFig,
-  extractDesignSystemFromFig,
-  renderHtmlTemplates,
-} from "@agent-native/core/brand-kit/fig";
-import { z } from "zod";
-
-/** Per-frame HTML is capped so the tool result stays a manageable size. The
- * agent can re-run with a smaller selection or fetch the full design via the
- * editor if it needs the complete markup. */
-const MAX_FRAMES = 24;
-const MAX_HTML_BYTES = 120 * 1024; // ~120 KB per frame
-const MAX_FIG_BYTES = 80 * 1024 * 1024; // 80 MB upload guard
-
-/** Accepts either a bare base64 string or a `data:...;base64,<payload>` URL
- * and returns the decoded bytes. */
-function decodeBase64Input(input: string): Buffer {
-  const trimmed = input.trim();
-  const comma = trimmed.indexOf(",");
-  const payload =
-    trimmed.startsWith("data:") && comma >= 0
-      ? trimmed.slice(comma + 1)
-      : trimmed;
-  return Buffer.from(payload, "base64");
-}
-
-export default defineAction({
-  description:
-    "Deeply parse an uploaded Figma `.fig` binary (modern fig-kiwi or legacy " +
-    "zip format) entirely in-process — no Figma account or MCP needed. " +
-    "Decodes the document node tree, renders each top-level frame to " +
-    "standalone HTML, and extracts a design-system token set (colors, " +
-    "typography, spacing, border radius, shadows). " +
-    "Provide the file as a base64 string or data URL in `fileBase64` (or " +
-    "`fileDataUrl`). This is read-only and writes nothing. " +
-    "WORKFLOW: (1) call this action with the .fig contents; (2) review the " +
-    "returned `designSystem` tokens and call `create-design-system` with them " +
-    "(optionally set as default); (3) review the returned `frames` and call " +
-    "`create-design` + `generate-design` with the frame HTML to import screens. " +
-    "Convert nothing yourself — the colors are already hex, effects already " +
-    "CSS, and spacing already snapped to a 4/8px scale.",
-  schema: z
-    .object({
-      fileBase64: z
-        .string()
-        .optional()
-        .describe(
-          "The .fig file contents as a base64 string (or a data: URL). " +
-            "Either fileBase64 or fileDataUrl is required.",
-        ),
-      fileDataUrl: z
-        .string()
-        .optional()
-        .describe(
-          "The .fig file as a data URL (data:application/octet-stream;base64,...). " +
-            "Alias for fileBase64.",
-        ),
-      title: z
-        .string()
-        .optional()
-        .describe("Optional title for the design being imported."),
-    })
-    .refine((v) => !!(v.fileBase64 || v.fileDataUrl), {
-      message: "Provide the .fig file in fileBase64 or fileDataUrl",
-    }),
-  readOnly: true,
-  run: async ({ fileBase64, fileDataUrl, title }) => {
-    const raw = (fileBase64 ?? fileDataUrl) as string;
-    let buffer: Buffer;
-    try {
-      buffer = decodeBase64Input(raw);
-    } catch {
-      throw new Error("Could not decode the provided base64 .fig payload.");
-    }
-    if (buffer.length === 0) {
-      throw new Error("The provided .fig payload was empty.");
-    }
-    if (buffer.length > MAX_FIG_BYTES) {
-      throw new Error(
-        `The .fig file is too large to parse in-process (${buffer.length} bytes > ${MAX_FIG_BYTES}).`,
-      );
-    }
-
-    let decoded;
-    try {
-      decoded = decodeFig(buffer);
-    } catch (err) {
-      throw new Error(
-        `Failed to decode .fig file: ${err instanceof Error ? err.message : String(err)}`,
-      );
-    }
-
-    if (!decoded.document) {
-      throw new Error(
-        "The .fig file decoded, but its document payload was empty or " +
-          "malformed (no node tree). It may be an unsupported format version.",
-      );
-    }
-
-    // Render frames. Image URLs line up with the hash-based filenames the
-    // decoder emits, so a downstream importer can attach the images under an
-    // `images/` directory if desired.
-    const imageMap = buildImageMap(decoded.images);
-    const rendered = renderHtmlTemplates(decoded.document, {
-      imageMap,
-      imageRefBase: "images",
-    });
-
-    const allFrames = rendered.frames;
-    const truncatedFrames = allFrames.slice(0, MAX_FRAMES).map((frame) => {
-      const safeName = frame.relativePath.replace(/\//g, ".");
-      let html = frame.html;
-      let truncated = false;
-      if (Buffer.byteLength(html, "utf8") > MAX_HTML_BYTES) {
-        html = html.slice(0, MAX_HTML_BYTES);
-        truncated = true;
-      }
-      return {
-        filename: safeName,
-        pageName: frame.pageName,
-        frameName: frame.frameName,
-        html,
-        ...(truncated ? { truncated: true } : {}),
-      };
-    });
-
-    const designSystem = extractDesignSystemFromFig(decoded.document);
-
-    const thumbnailDataUrl = decoded.thumbnail
-      ? `data:image/png;base64,${decoded.thumbnail.toString("base64")}`
-      : undefined;
-
-    return {
-      source: "fig-file",
-      title: title ?? null,
-      format: decoded.format,
-      version: decoded.version ?? null,
-      frames: truncatedFrames,
-      frameCount: rendered.frameCount,
-      pageCount: rendered.pageCount,
-      framesTruncated: allFrames.length > MAX_FRAMES,
-      designSystem,
-      imageCount: decoded.images.length,
-      images: decoded.images.map((img) => ({
-        filename: `${img.hash}.${img.ext}`,
-        ext: img.ext,
-        sizeBytes: img.bytes.length,
-      })),
-      thumbnailDataUrl,
-      instructions: [
-        "Parsed the .fig file in-process. Next steps:",
-        "1. Build the design system: call create-design-system using the " +
-          "`designSystem` tokens above (colors are hex, effects are CSS, " +
-          "spacing is snapped to a 4/8px scale). Set it as default if the " +
-          "user wants it applied to new designs.",
-        "2. Import screens: call create-design, then generate-design with the " +
-          "`frames` HTML (one file per frame, or the most relevant frames). " +
-          "Each frame is complete standalone HTML.",
-        "3. Image fills reference `images/<hash>.<ext>` — upload those bytes " +
-          "as design assets if you need the images to render.",
-      ].join("\n"),
-    };
-  },
-});