@agent-native/core 0.130.2 → 0.131.3

package/corpus/templates/forms/.agents/skills/agent-native-toolkit/SKILL.md

@@ -117,6 +117,11 @@ in the moment of agent use.
   missing-secret states, OAuth grants, and provider connection health.
 - **Agent UX kit**: sidebar, composer, staged context, mentions, voice, human
   approval, generative UI, progress, and screen-state exposure.
+- **Custom block kit**: optional extension creation, viewer chrome, slots, and
+  promotion affordances. Apps must opt in; Core keeps the sandbox, SQL storage,
+  access checks, and compatibility routes, while Toolkit owns reusable adoption
+  UI. Analytics may expose this as one-off **Custom Blocks**; durable behavior
+  should be promoted to app code.
 - **Chat history kit**: presentational chat lists and recent-chat rails belong
   in Toolkit; Core keeps thread persistence, agent execution, transport, and
   page-to-sidebar handoff. Use Toolkit's `ChatHistoryRail` for the standard

package/corpus/templates/forms/app/components/layout/Sidebar.tsx

@@ -5,7 +5,7 @@ import {
 } from "@agent-native/core/client/agent-chat";
 import { appPath } from "@agent-native/core/client/api-path";
 import { DevDatabaseLink } from "@agent-native/core/client/db-admin";
-import { LanguagePicker, useT } from "@agent-native/core/client/i18n";
+import { useT } from "@agent-native/core/client/i18n";
 import { openCommandMenu } from "@agent-native/core/client/navigation";
 import { OrgSwitcher } from "@agent-native/core/client/org";
 import { FeedbackButton } from "@agent-native/core/client/ui";
@@ -114,9 +114,6 @@ export function Sidebar() {
       <TooltipContent side="right">{t("root.searchForms")}</TooltipContent>
     </Tooltip>
   );
-  const translateButton = (
-    <LanguagePicker variant="ghost-icon" label={t("settings.languageLabel")} />
-  );
   const feedbackButton = (
     <FeedbackButton
       variant={effectiveCollapsed ? "icon" : "sidebar"}
@@ -340,7 +337,6 @@ export function Sidebar() {
         <SidebarFooterActions
           collapsed
           feedback={feedbackButton}
-          translate={translateButton}
           search={searchButton}
           collapse={collapseButton}
         />
@@ -468,7 +464,6 @@ export function Sidebar() {
         </div>
         <SidebarFooterActions
           feedback={feedbackButton}
-          translate={translateButton}
           search={searchButton}
           collapse={collapseButton}
           className="px-0 py-0"

package/corpus/templates/forms/changelog/2026-07-29-sidebar-footers-now-keep-feedback-search-and-collapse-togeth.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-29
+---
+
+Sidebar footers now keep Feedback, Search, and Collapse together without a separate language shortcut.

package/corpus/templates/macros/.agents/skills/agent-native-toolkit/SKILL.md

@@ -117,6 +117,11 @@ in the moment of agent use.
   missing-secret states, OAuth grants, and provider connection health.
 - **Agent UX kit**: sidebar, composer, staged context, mentions, voice, human
   approval, generative UI, progress, and screen-state exposure.
+- **Custom block kit**: optional extension creation, viewer chrome, slots, and
+  promotion affordances. Apps must opt in; Core keeps the sandbox, SQL storage,
+  access checks, and compatibility routes, while Toolkit owns reusable adoption
+  UI. Analytics may expose this as one-off **Custom Blocks**; durable behavior
+  should be promoted to app code.
 - **Chat history kit**: presentational chat lists and recent-chat rails belong
   in Toolkit; Core keeps thread persistence, agent execution, transport, and
   page-to-sidebar handoff. Use Toolkit's `ChatHistoryRail` for the standard

package/corpus/templates/macros/app/components/layout/AppLayout.tsx

@@ -1,7 +1,7 @@
 import { AgentSidebar } from "@agent-native/core/client/agent-chat";
 import { agentNativePath, appPath } from "@agent-native/core/client/api-path";
 import { DevDatabaseLink } from "@agent-native/core/client/db-admin";
-import { LanguagePicker, useT } from "@agent-native/core/client/i18n";
+import { useT } from "@agent-native/core/client/i18n";
 import { openCommandMenu } from "@agent-native/core/client/navigation";
 import { OrgSwitcher } from "@agent-native/core/client/org";
 import { FeedbackButton } from "@agent-native/core/client/ui";
@@ -232,9 +232,6 @@ function SidebarContent({
       <TooltipContent side="right">{t("root.search")}</TooltipContent>
     </Tooltip>
   );
-  const translateButton = (
-    <LanguagePicker variant="ghost-icon" label={t("settings.languageLabel")} />
-  );
   const feedbackButton = (
     <FeedbackButton
       variant={collapsed ? "icon" : "sidebar"}
@@ -352,7 +349,6 @@ function SidebarContent({
       <SidebarFooterActions
         collapsed={collapsed}
         feedback={feedbackButton}
-        translate={translateButton}
         search={searchButton}
         collapse={collapseButton}
       />

package/corpus/templates/macros/changelog/2026-07-29-sidebar-footers-now-keep-feedback-search-and-collapse-togeth.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-29
+---
+
+Sidebar footers now keep Feedback, Search, and Collapse together without a separate language shortcut.

package/corpus/templates/mail/.agents/skills/agent-native-toolkit/SKILL.md

@@ -117,6 +117,11 @@ in the moment of agent use.
   missing-secret states, OAuth grants, and provider connection health.
 - **Agent UX kit**: sidebar, composer, staged context, mentions, voice, human
   approval, generative UI, progress, and screen-state exposure.
+- **Custom block kit**: optional extension creation, viewer chrome, slots, and
+  promotion affordances. Apps must opt in; Core keeps the sandbox, SQL storage,
+  access checks, and compatibility routes, while Toolkit owns reusable adoption
+  UI. Analytics may expose this as one-off **Custom Blocks**; durable behavior
+  should be promoted to app code.
 - **Chat history kit**: presentational chat lists and recent-chat rails belong
   in Toolkit; Core keeps thread persistence, agent execution, transport, and
   page-to-sidebar handoff. Use Toolkit's `ChatHistoryRail` for the standard

package/corpus/templates/mail/app/components/layout/AppLayout.tsx

@@ -5,7 +5,7 @@ import {
 import { agentNativePath } from "@agent-native/core/client/api-path";
 import { appApiPath } from "@agent-native/core/client/api-path";
 import { DevDatabaseLink } from "@agent-native/core/client/db-admin";
-import { LanguagePicker, useT } from "@agent-native/core/client/i18n";
+import { useT } from "@agent-native/core/client/i18n";
 import { openCommandMenu } from "@agent-native/core/client/navigation";
 import { InvitationBanner, OrgSwitcher } from "@agent-native/core/client/org";
 import { FeedbackButton } from "@agent-native/core/client/ui";
@@ -427,9 +427,6 @@ function AppLayoutInner({ children }: AppLayoutProps) {
       <TooltipContent side="right">{t("mail.search.label")}</TooltipContent>
     </Tooltip>
   );
-  const translateButton = (
-    <LanguagePicker variant="ghost-icon" label={t("settings.languageLabel")} />
-  );
   const feedbackButton = (
     <FeedbackButton
       variant={showCollapsedSidebar ? "icon" : "sidebar"}
@@ -1801,7 +1798,6 @@ function AppLayoutInner({ children }: AppLayoutProps) {
               <SidebarFooterActions
                 collapsed={showCollapsedSidebar}
                 feedback={feedbackButton}
-                translate={translateButton}
                 search={searchButton}
                 collapse={collapseButton}
                 className={showCollapsedSidebar ? undefined : "px-0 py-0"}
@@ -2030,9 +2026,6 @@ function StandardLayout({ children }: AppLayoutProps) {
       <TooltipContent side="right">{t("mail.search.label")}</TooltipContent>
     </Tooltip>
   );
-  const translateButton = (
-    <LanguagePicker variant="ghost-icon" label={t("settings.languageLabel")} />
-  );
   const feedbackButton = (
     <FeedbackButton variant="sidebar" side="right" className="min-w-0" />
   );
@@ -2198,7 +2191,6 @@ function StandardLayout({ children }: AppLayoutProps) {
             </div>
             <SidebarFooterActions
               feedback={feedbackButton}
-              translate={translateButton}
               search={searchButton}
               collapse={collapseButton}
               className="px-0 py-0"

package/corpus/templates/mail/changelog/2026-07-29-sidebar-footers-now-keep-feedback-search-and-collapse-togeth.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-29
+---
+
+Sidebar footers now keep Feedback, Search, and Collapse together without a separate language shortcut.

package/corpus/templates/plan/.agents/skills/agent-native-toolkit/SKILL.md

@@ -117,6 +117,11 @@ in the moment of agent use.
   missing-secret states, OAuth grants, and provider connection health.
 - **Agent UX kit**: sidebar, composer, staged context, mentions, voice, human
   approval, generative UI, progress, and screen-state exposure.
+- **Custom block kit**: optional extension creation, viewer chrome, slots, and
+  promotion affordances. Apps must opt in; Core keeps the sandbox, SQL storage,
+  access checks, and compatibility routes, while Toolkit owns reusable adoption
+  UI. Analytics may expose this as one-off **Custom Blocks**; durable behavior
+  should be promoted to app code.
 - **Chat history kit**: presentational chat lists and recent-chat rails belong
   in Toolkit; Core keeps thread persistence, agent execution, transport, and
   page-to-sidebar handoff. Use Toolkit's `ChatHistoryRail` for the standard

package/corpus/templates/plan/app/components/layout/Sidebar.tsx

@@ -10,7 +10,7 @@ import { appPath } from "@agent-native/core/client/api-path";
 import { PromptComposer } from "@agent-native/core/client/composer";
 import { DevDatabaseLink } from "@agent-native/core/client/db-admin";
 import { useSession } from "@agent-native/core/client/hooks";
-import { LanguagePicker, useT } from "@agent-native/core/client/i18n";
+import { useT } from "@agent-native/core/client/i18n";
 import { openCommandMenu } from "@agent-native/core/client/navigation";
 import { OrgSwitcher } from "@agent-native/core/client/org";
 import {
@@ -584,9 +584,6 @@ export function Sidebar({
       </TooltipContent>
     </Tooltip>
   );
-  const translateButton = (
-    <LanguagePicker variant="ghost-icon" label={t("settings.languageLabel")} />
-  );
   const feedbackButton = (
     <FeedbackButton
       variant={collapsed ? "icon" : "sidebar"}
@@ -669,8 +666,8 @@ export function Sidebar({
           return (
             <div key={item.href}>
               {link}
-              {item.href === "/" && isActive ? (
-                <PlanChatsSection collapsed={collapsed} open />
+              {item.href === "/" ? (
+                <PlanChatsSection collapsed={collapsed} open={isActive} />
               ) : null}
               {item.href === "/plans" && isActive ? (
                 <PlansSidebarSection collapsed={collapsed} />
@@ -746,7 +743,6 @@ export function Sidebar({
       <SidebarFooterActions
         collapsed={collapsed}
         feedback={feedbackButton}
-        translate={translateButton}
         search={searchButton}
         collapse={collapseButton}
       />

package/corpus/templates/plan/app/pages/PlansPage.tsx

@@ -1467,7 +1467,7 @@ function resolveInlineCommentPosition(input: {
   };
 }
 
-function buildPlanAgentContext(input: {
+export function buildPlanAgentContext(input: {
   bundle: PlanBundle & { html?: string };
   documentHtml: string;
   url: string;
@@ -1563,7 +1563,7 @@ function buildPlanAgentContext(input: {
         .join("\n");
     })
     .join("\n");
-  const recentReviewEvents = input.bundle.events
+  const recentReviewEvents = (input.bundle.events ?? [])
     .filter((event) => event.type === "plan.updated")
     .slice(-6)
     .map((event) => {

package/corpus/templates/plan/changelog/2026-07-29-chat-history-now-closes-smoothly-and-stays-ready-when-you-re.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-29
+---
+
+Chat history now closes smoothly and stays ready when you return to Ask.

package/corpus/templates/plan/changelog/2026-07-29-chat-history-stays-visible-when-you-return-to-ask-plan.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-29
+---
+
+Chat history stays visible when you return to Ask Plan.

package/corpus/templates/plan/changelog/2026-07-29-fixed-plan-pages-crashing-when-recent-activity-is-unavailabl.md

@@ -0,0 +1,6 @@
+---
+type: fixed
+date: 2026-07-29
+---
+
+Fixed Plan pages crashing when recent activity is unavailable.

package/corpus/templates/plan/changelog/2026-07-29-sidebar-footers-now-keep-feedback-search-and-collapse-togeth.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-29
+---
+
+Sidebar footers now keep Feedback, Search, and Collapse together without a separate language shortcut.

package/corpus/templates/slides/.agents/skills/agent-native-toolkit/SKILL.md

@@ -117,6 +117,11 @@ in the moment of agent use.
   missing-secret states, OAuth grants, and provider connection health.
 - **Agent UX kit**: sidebar, composer, staged context, mentions, voice, human
   approval, generative UI, progress, and screen-state exposure.
+- **Custom block kit**: optional extension creation, viewer chrome, slots, and
+  promotion affordances. Apps must opt in; Core keeps the sandbox, SQL storage,
+  access checks, and compatibility routes, while Toolkit owns reusable adoption
+  UI. Analytics may expose this as one-off **Custom Blocks**; durable behavior
+  should be promoted to app code.
 - **Chat history kit**: presentational chat lists and recent-chat rails belong
   in Toolkit; Core keeps thread persistence, agent execution, transport, and
   page-to-sidebar handoff. Use Toolkit's `ChatHistoryRail` for the standard

package/corpus/templates/slides/.agents/skills/analytics-data-for-decks/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: analytics-data-for-decks
+description: >-
+  Route customer, account, CRM, HubSpot, pipeline, renewal, usage, product
+  activity, Gong, and other analytics-backed deck requests through the
+  Analytics agent. Use when generating or updating Slides content that needs
+  external or first-party data.
+---
+
+# Analytics data for decks
+
+When a deck needs customer or product data, ask the Analytics agent over A2A
+before creating or changing Slides content. The user's wording can be direct,
+such as "ask the analytics agent to ...", or implicit in a request for customer,
+account, CRM, HubSpot, pipeline, renewal, usage, product-activity, Gong, or
+other analytics data.
+
+## Delegation
+
+- For a known, read-only operation, use `call-agent` with `agent: "analytics"`,
+  the exact `action`, and complete `input`. This invokes Analytics directly
+  without starting a second model loop.
+- For ambiguous, multi-source, or narrative questions, use `call-agent` with a
+  natural-language `message` and let Analytics decide which source or sources
+  to use.
+- Useful Analytics operations include `hubspot-records` for bounded CRM
+  records and `hubspot-deals` for pipeline and deal metrics,
+  `account-deep-dive` for a named account or renewal/risk review, `gong-calls`
+  for quotes/counts/transcripts and coverage, and `gong-native-insights` for
+  bounded narrative synthesis. For first-party product activity, send a
+  natural-language message and let Analytics choose its query.
+- Slides must not write SQL, choose a warehouse or provider, call HubSpot/Gong
+  directly, or interpret a provider schema itself. Analytics owns source
+  selection, data dictionary interpretation, filters, joins, and query
+  execution using its own instructions and connected-source status.
+
+## Evidence and deck behavior
+
+- Preserve the question, source, filters, date window, coverage, counts,
+  pagination, and limitations from Analytics. Never invent customer data or
+  claim a lookup succeeded when it failed.
+- If a source is unavailable, name the missing source and continue only with
+  clearly labeled data that Analytics actually returned. Do not expose
+  credentials or raw provider payloads.
+- Before generation, call `get-workspace-defaults` when no reference deck or
+  design system is named, then follow `creative-context` for approved brand
+  context and provenance. For updates, preserve the existing deck structure
+  and make focused slide edits.

package/corpus/templates/slides/.agents/skills/create-deck/SKILL.md

@@ -11,10 +11,19 @@ description: How to create a new deck with slides from scratch. Read this before
 
 1. Read the `creative-context` skill and retrieve factual evidence separately
    from presentation structure. Respect `contextMode: "off"`.
-2. Plan the slides (title, section dividers, content slides).
-3. Call `create-deck --title "..." --slides '[]'` to create an empty deck.
-4. Navigate to the new deck.
-5. Call `add-slide` once per slide in slide order, waiting for each result.
+2. Unless the user named a reference deck or design system, call
+   `get-workspace-defaults` and use what it returns. See "Workspace Defaults".
+3. Plan the slides (deck title, title slide, section dividers, content slides).
+4. Call `create-deck --title "..." --slides '[]'` with a concise, specific
+   title derived from the user's request and source material. Never use
+   `Untitled Deck` or another placeholder title for a generated deck.
+5. Navigate to the new deck.
+6. Call `add-slide` once per slide in slide order, waiting for each result.
+
+When the UI has already created the empty deck, keep its id and rename it before
+adding the first slide. Call `patch-deck` with a `patch-deck-fields` operation
+whose `fields.title` is the generated title. Do not leave the pre-created deck's
+placeholder title in place.
 
 Follow the creative-context reuse ladder before inventing a slide language:
 reuse an approved native template unchanged, compose approved pieces, lightly
@@ -37,6 +46,53 @@ sub-agents to write into the same deck at the same time. Sub-agents may research
 or draft slide copy, but one writer should call `add-slide` sequentially so the
 editor stays stable and the user can watch progress.
 
+## Reference Decks
+
+The user can pick an existing deck as a style reference when starting a new one.
+When they do, a `## Reference Deck` block is already in your context holding one
+worked HTML example per layout.
+
+Treat it as a pattern library, not an outline. The most common failure here is
+walking the reference deck slide by slide and swapping in new copy, which
+produces a deck with the wrong shape for its own content. Instead:
+
+1. Plan the new deck from the user's request alone — story, slide count, order.
+2. For each slide you decided to write, pick the pattern that fits that content.
+3. Reuse a pattern as often as the content warrants, or never.
+4. When nothing fits, compose a new slide from the same type scale, spacing,
+   color, and markup conventions rather than bending content to a near-miss.
+
+The block deliberately omits the reference deck's slide sequence. Call
+`get-deck --id <reference deck id>` if you need to see how that deck handled a
+case the patterns do not cover.
+
+A reference deck and a design system are independent: the design system wins on
+tokens (color, type, spacing), the reference deck wins on slide-level
+composition and markup idiom. Apply both when both are present.
+
+Decks the user has starred are their intended reference decks. `list-decks`
+reports `starred` so you can offer them when the user asks for something "like
+our usual deck".
+
+## Workspace Defaults
+
+A workspace admin can flag one deck and one design system as the workspace
+default, so a bare "make a deck about X" still comes out on brand. When the user
+did not name a reference deck or design system, call `get-workspace-defaults`
+before planning slides.
+
+- `referenceDeck` — call `get-deck-reference-context --id <id>` and treat the
+  result exactly like a user-picked reference deck.
+- `designSystem` — pass its id as `designSystemId` to `create-deck`, unless the
+  caller already has a personal default, which `create-deck` applies on its own.
+- Either field can come back `{ unavailable: true }`. That means the default
+  exists but this user cannot open it, which is a misconfiguration, not an
+  absent default. Generate without it and tell the user their workspace default
+  is not shared with them, rather than silently producing an off-brand deck.
+
+An explicit request always wins over the workspace default. Do not re-apply a
+workspace default to an existing deck the user is editing.
+
 If the user provides a Google Docs URL as source material, call
 `import-google-doc --url <url>` first and build from the returned text. If the
 action cannot read a private document, the user can connect Google Docs and

package/corpus/templates/slides/.agents/skills/design-systems/SKILL.md

@@ -40,6 +40,26 @@ Do not call `create-design-system` locally from `.fig` uploads. Do not call
 `import-document` for `.fig` files; it only handles metadata and will miss the
 Builder indexing flow.
 
+### Source: connected code, GitHub, or `design.md`
+
+For any other reusable source — connected code, a GitHub repo, local
+code/design files, or an optional `design.md` — use Builder-backed DSI
+indexing through `index-design-system-with-builder`. Pass readable `design.md`
+content as `designMd`, and use the returned local design system id in the rest
+of the Slides flow. Call `get-design-system` before generation so Builder docs
+and tokens are hydrated when available.
+
+Never create a duplicate local design system from raw Figma or code sources.
+Builder owns the indexed brand kit; a second local copy drifts from it and
+nothing records which one a deck was actually built from.
+
+### Source: workspace default
+
+A workspace admin can flag one design system as the workspace default, used by
+members who have not set their own. `create-deck` resolves it server-side, so
+call `get-workspace-defaults` only to name it or answer what the default is.
+See the `create-deck` skill.
+
 ## Deleting a Design System
 
 `delete-design-system` requires admin access or higher (owner or admin share

package/corpus/templates/slides/.agents/skills/slide-editing/SKILL.md

@@ -5,7 +5,11 @@ description: How to edit individual slides -- content formatting, HTML styling r
 
 # Slide Editing
 
-Slides are HTML content stored inside the deck JSON. Each slide's `content` field is a self-contained HTML string that renders at 1920x1080 resolution.
+Slides are HTML content stored inside the deck JSON. Each slide's `content`
+field is a self-contained HTML string rendered at the intrinsic dimensions for
+its aspect ratio: 16:9 is 960x540, 1:1 is 1080x1080, 9:16 is 540x960, and 4:5
+is 864x1080. These canonical dimensions come from the shared aspect-ratio
+registry; do not assume a fixed 1920x1080 canvas.
 
 ## Slide HTML Structure
 
@@ -56,6 +60,31 @@ If retrieval produces a new immutable context pack, keep its `contextPackId`
 and reuse labels with the deck provenance. Existing slide HTML is not proof of
 which source version influenced it.
 
+## Freeform Canvas Objects
+
+Manual text boxes and other freeform canvas objects are absolutely positioned
+children of `.fmd-slide`. Give each one a stable `data-slide-object-id`:
+
+```html
+<div
+  class="fmd-text-box"
+  data-slide-object-id="slide-object-unique-id"
+  style="position: absolute; left: 160px; top: 120px; width: 420px;"
+>
+  Editable text
+</div>
+```
+
+- Preserve `data-slide-object-id` when updating, moving, resizing, or styling an
+  existing object.
+- Mint a new unique object ID when duplicating an object.
+- Do not use runtime-only `data-builder-id` values in saved slide HTML.
+- Keep generated flex and grid content in normal flow. Do not silently
+  absolute-position a nested layout child just to make it draggable; create a
+  deliberate freeform object instead.
+- Build editable shapes with styled HTML elements such as `div`. Do not use
+  inline SVG, which the slide sanitizer removes.
+
 ## Image Placeholders
 
 For visual elements (diagrams, charts, photos), use placeholder divs:

package/corpus/templates/slides/.agents/skills/slide-images/SKILL.md

@@ -22,7 +22,9 @@ The standard workflow for generating slide images:
 
 1. User clicks "Image" in the editor or asks the agent
 2. Agent runs `pnpm action generate-image --prompt "..." --count 3`
-3. Agent shows variations to the user in chat
+3. Agent shows each variation as an inline rendered preview using markdown
+   image syntax (`![Variation 1](url)`), not a plain link (`[Variation 1](url)`)
+   — the chat renders `![]()` as an actual image but `[]()` as a bare link
 4. User picks a favorite
 5. Agent writes the chosen image into the slide content
 6. User can follow up: "make it darker", "try a different angle"

package/corpus/templates/slides/AGENTS.md

@@ -27,21 +27,17 @@ ladder.
   current layout is unclear.
 - Preserve deck structure and visual consistency. Prefer focused slide edits over
   regenerating whole decks unless requested.
+- Preserve freeform objects and their `data-slide-object-id` values. They are
+  absolutely positioned `.fmd-slide` children; keep generated flex/grid in
+  normal flow and mint ids only for duplicates. Use styled HTML, not inline SVG.
 - Follow linked design-system tokens and custom instructions.
-- For reusable design-system setup from Figma, connected code/GitHub, local
-  code/design files, or optional `design.md`, use Builder-backed DSI indexing
-  through `index-design-system-with-builder` or `import-file --format fig`.
-  Pass readable `design.md` content as `designMd`, use the returned local design
-  system id in Slides flows, and call `get-design-system` before generation to
-  hydrate Builder docs/tokens when available. Do not create a duplicate local
-  design system from raw Figma/code sources.
-- Treat import/export actions as shortcuts, not capability limits. When the
-  exact Google Drive endpoint, file metadata field, export format, pagination
-  mode, or API version matters, use `provider-api-catalog`,
-  `provider-api-docs`, and `provider-api-request` against the real provider
-  API. Slides resolves Google Drive auth from the user's connected Google Docs
-  OAuth account. For large scans, stage results with `stageAs` and analyze them
-  with `query-staged-dataset`.
+- Build reusable design systems from Figma, code, GitHub, or `design.md` via
+  Builder-backed DSI indexing, never a duplicate local copy. Read
+  `design-systems` for the per-source actions.
+- Import/export actions are shortcuts, not capability limits. For exact Google
+  Drive API needs, use `provider-api-catalog`, `provider-api-docs`, and
+  `provider-api-request`; auth comes from the user's Google Docs OAuth. Stage
+  large scans with `stageAs` and analyze them via `query-staged-dataset`.
 - Use image-generation and image-selection actions only when the deck genuinely
   needs imagery; keep citations/asset provenance when available.
 - Use framework sharing actions for deck visibility and grants.
@@ -49,15 +45,15 @@ ladder.
   and `input` (or `invokeAgentAction`) instead of starting the sibling agent's
   model loop. In Analytics, use `gong-native-insights` for provider-synthesized
   briefs and `gong-calls` for quotes, counts, transcripts, and coverage claims.
-- Before generation, follow the creative-context reuse ladder in
-  `.agents/skills/creative-context/SKILL.md`: explicit request and current deck
-  first, then a pinned/current pack, then narrow library search. Respect
-  `creative-context.contextMode: "off"` without silently restoring a pack.
-- To submit a deck to a governed Creative Context, use the Context tab or
-  `manage-context-membership`; it captures one immutable deck version. Reuse
-  only a returned opaque native clone reference through the Slides clone action.
-  Use `operation="submit-latest"` with a Library membership id when its native
-  update status reports `update-available`.
+- For data requests, read `.agents/skills/analytics-data-for-decks/SKILL.md` and
+  delegate via Analytics over A2A; do not write SQL or call providers directly.
+- When the user names no reference deck or design system, call
+  `get-workspace-defaults` first so a bare "make a deck about X" is still on
+  brand.
+- Before generation, follow `.agents/skills/creative-context/SKILL.md`: explicit
+  request/current deck, then pinned/current pack, then narrow library search.
+  Respect `contextMode: "off"`. Submit governed context through the Context tab
+  or `manage-context-membership`; reuse only its opaque clone reference.
 
 ## Persistence Model
 
@@ -89,6 +85,10 @@ extending the editor's save path, enqueue a granular op (`patch-slide`,
 - Browser PowerPoint export uses the rendered slide DOM to generate native,
   editable PPTX text/shapes/images. Do not replace it with full-slide images
   unless the user explicitly asks for non-editable visual snapshots.
+- The server-side `export-pptx` action cannot measure browser-rendered
+  freeform geometry. It must fail clearly for positioned objects and direct the
+  user to the editor's Export > PowerPoint path instead of silently reflowing
+  them.
 - Google Slides export is a PPTX import workflow: generate the same editable
   PPTX and have the user import it into Google Slides. Creating a native Google
   Slides file directly requires a separate Google Slides API batchUpdate path.
@@ -97,10 +97,11 @@ extending the editor's save path, enqueue a granular op (`patch-slide`,
 
 Read the relevant skill before deeper work:
 
-- `create-deck` for new decks and outline-to-slide flows.
+- `create-deck` for new decks, reference decks, workspace defaults, outlines.
 - `slide-editing` for targeted slide changes.
 - `deck-management` for organization, sharing, import/export, and metadata.
 - `slide-images` and `image-generation-via-a2a` for image work.
 - `design-systems`, `frontend-design`, `shadcn-ui`, and `actions` as needed.
 - `creative-context` for cross-app source reuse, pinned packs, provenance, and
   context opt-out.
+- `analytics-data-for-decks` for delegated data.

package/corpus/templates/slides/actions/check-image-gen.ts

@@ -1,15 +1,21 @@
 import { defineAction } from "@agent-native/core";
-import { resolveSecret } from "@agent-native/core/server";
+import {
+  resolveBuilderCredentials,
+  resolveSecret,
+} from "@agent-native/core/server";
 import { z } from "zod";
 
 export default defineAction({
   description:
-    "Check which image generation providers are configured (Gemini API key status).",
+    "Check which image generation providers are configured (Builder connection, Gemini/OpenAI API key status).",
   schema: z.object({}),
   http: { method: "GET" },
   run: async () => {
+    const builderCreds = await resolveBuilderCredentials();
     return {
+      builder: !!(builderCreds.privateKey && builderCreds.publicKey),
       gemini: !!(await resolveSecret("GEMINI_API_KEY")),
+      openai: !!(await resolveSecret("OPENAI_API_KEY")),
     };
   },
 });

package/corpus/templates/slides/actions/create-deck.ts

@@ -11,13 +11,14 @@ import {
   validateGenerationCreativeContext,
 } from "@agent-native/creative-context/server";
 import type { CreativeContextElementProvenance } from "@agent-native/creative-context/types";
-import { and, eq } from "drizzle-orm";
+import { eq } from "drizzle-orm";
 import { z } from "zod";
 
 import { normalizeSlidePadding } from "../app/lib/normalize-slide-padding.js";
 import { getDb, schema } from "../server/db/index.js";
 import { notifyClients } from "../server/handlers/decks.js";
 import { createDeckVersionSnapshot } from "../server/lib/deck-versions.js";
+import { resolveDefaultDesignSystemId } from "../server/workspace-defaults.js";
 import { ASPECT_RATIO_VALUES } from "../shared/aspect-ratios.js";
 import { getDeckUrl } from "./_app-url.js";
 
@@ -286,17 +287,8 @@ export default defineAction({
     if (resolvedDesignSystemId) {
       await assertAccess("design-system", resolvedDesignSystemId, "viewer");
     } else {
-      const defaults = await db
-        .select({ id: schema.designSystems.id })
-        .from(schema.designSystems)
-        .where(
-          and(
-            eq(schema.designSystems.ownerEmail, ownerEmail),
-            eq(schema.designSystems.isDefault, true),
-          ),
-        )
-        .limit(1);
-      resolvedDesignSystemId = defaults[0]?.id;
+      resolvedDesignSystemId =
+        (await resolveDefaultDesignSystemId(ownerEmail)) ?? undefined;
     }
 
     const id = `deck-${Date.now()}-${Math.random().toString(36).slice(2, 7)}`;