@agent-native/core 0.84.20 → 0.84.22

package/corpus/templates/design/actions/delete-file.ts

@@ -5,9 +5,72 @@ import { z } from "zod";
 
 import { getDb, schema } from "../server/db/index.js";
 
+function isRecord(value: unknown): value is Record<string, unknown> {
+  return Boolean(value && typeof value === "object" && !Array.isArray(value));
+}
+
+function parseDesignData(value: unknown): Record<string, unknown> {
+  if (typeof value !== "string" || !value.trim()) return {};
+  try {
+    const parsed = JSON.parse(value);
+    return isRecord(parsed) ? parsed : {};
+  } catch {
+    return {};
+  }
+}
+
+function pruneKeyedRecord(
+  value: unknown,
+  fileId: string,
+): Record<string, unknown> | undefined {
+  if (!isRecord(value)) return undefined;
+  const next = { ...value };
+  delete next[fileId];
+  return next;
+}
+
+function variantScreenMatchesFile(screen: unknown, fileId: string): boolean {
+  if (typeof screen === "string") return screen === fileId;
+  return isRecord(screen) && screen.id === fileId;
+}
+
+function pruneDesignVariantSets(
+  value: unknown,
+  fileId: string,
+): Record<string, unknown> | undefined {
+  if (!isRecord(value)) return undefined;
+  const next: Record<string, unknown> = {};
+  for (const [key, rawSet] of Object.entries(value)) {
+    if (!isRecord(rawSet) || !Array.isArray(rawSet.screens)) {
+      next[key] = rawSet;
+      continue;
+    }
+    const screens = rawSet.screens.filter(
+      (screen) => !variantScreenMatchesFile(screen, fileId),
+    );
+    if (screens.length <= 1) continue;
+    next[key] = { ...rawSet, screens };
+  }
+  return next;
+}
+
+function pruneDeletedFileMetadata(
+  data: Record<string, unknown>,
+  fileId: string,
+): Record<string, unknown> {
+  return {
+    ...data,
+    canvasFrames: pruneKeyedRecord(data.canvasFrames, fileId) ?? {},
+    screenMetadata: pruneKeyedRecord(data.screenMetadata, fileId) ?? {},
+    localhostScreens: pruneKeyedRecord(data.localhostScreens, fileId) ?? {},
+    designVariantSets:
+      pruneDesignVariantSets(data.designVariantSets, fileId) ?? {},
+  };
+}
+
 export default defineAction({
   description:
-    "Delete a file from a design project. Validates ownership via the parent design's access.",
+    "Delete a file from a design project. Idempotent: if the file is already gone, returns deleted=false so cleanup retries can continue. Validates ownership via the parent design's access when the file exists.",
   schema: z.object({
     id: z.string().describe("File ID to delete"),
   }),
@@ -33,21 +96,34 @@ export default defineAction({
       )
       .limit(1);
 
-    if (!file) {
-      throw new Error(`File not found: ${id}`);
-    }
+    if (!file) return { id, deleted: false, alreadyMissing: true };
 
     await assertAccess("design", file.designId, "editor");
 
     const now = new Date().toISOString();
 
-    await db.delete(schema.designFiles).where(eq(schema.designFiles.id, id));
+    await db.transaction(async (tx) => {
+      const [currentDesign] = await tx
+        .select({ data: schema.designs.data })
+        .from(schema.designs)
+        .where(eq(schema.designs.id, file.designId))
+        .limit(1);
+      const nextData = pruneDeletedFileMetadata(
+        parseDesignData(currentDesign?.data),
+        id,
+      );
+
+      await tx.delete(schema.designFiles).where(eq(schema.designFiles.id, id));
 
-    // Update the parent design's updatedAt timestamp
-    await db
-      .update(schema.designs)
-      .set({ updatedAt: now })
-      .where(eq(schema.designs.id, file.designId));
+      // Update the parent design's board metadata and updatedAt timestamp.
+      await tx
+        .update(schema.designs)
+        .set({
+          data: JSON.stringify({ ...nextData, updatedAt: now }),
+          updatedAt: now,
+        })
+        .where(eq(schema.designs.id, file.designId));
+    });
 
     return { id, deleted: true };
   },

package/corpus/templates/design/actions/get-design-snapshot.ts

@@ -87,6 +87,7 @@ export default defineAction({
       err.statusCode = 409;
       throw err;
     }
+    const boundedFile = requestedFileId || requestedFilename ? files[0] : null;
 
     return {
       designId,
@@ -108,6 +109,18 @@ export default defineAction({
       appliedTweaks: snapshot.appliedTweaks,
       resolvedCssVars: snapshot.resolvedCssVars,
       deepLink: designDeepLink(designId),
+      ...(boundedFile
+        ? {
+            editTarget: {
+              designId,
+              fileId: boundedFile.id,
+              filename: boundedFile.filename,
+            },
+            nextRequiredAction:
+              `Call edit-design exactly once with designId ${designId} and fileId ${boundedFile.id} (${boundedFile.filename}). ` +
+              "Do not call delete-file or get-design-snapshot again unless edit-design fails with a concrete missing context error.",
+          }
+        : {}),
     };
   },
   link: ({ result }) => {

package/corpus/templates/design/actions/present-design-variants.ts

@@ -40,20 +40,18 @@ const FALLBACK_INSTRUCTIONS =
   "The generated directions have been saved as normal screens on the Design " +
   "overview board. The chat shows one button per screen. Ask the user to pick " +
   "a screen by name if the inline buttons are not available; after they pick, " +
-  "delete the other variant screens, call get-design-snapshot with fileId for " +
-  "the kept screen, then call edit-design on that same fileId in a bounded pass. " +
+  "delete each other variant screen at most once, call get-design-snapshot with fileId for " +
+  "the kept screen once, then call edit-design on that same fileId in a bounded pass. " +
   'Use mode "replace-file" when expanding the representative placeholder. ' +
   "Do not call generate-design after a variant pick.";
 
 const VARIANT_PICK_SUBMIT_MESSAGE =
-  "Use this design direction. Delete the other variant screens, call " +
-  "get-design-snapshot with the selected option's fileId (or filename if " +
-  "needed) for the kept file, then call edit-design with that same fileId in " +
-  'a bounded single-file pass. Use mode "replace-file" when replacing the ' +
-  "representative placeholder with the full chosen direction, or search/replace " +
-  "for smaller refinements. Do not call generate-design after a variant pick, " +
-  "do not create index.html, and do not resend a huge payload. Stop after the " +
-  "first successful edit-design save.";
+  "Use this design direction. Keep the selected screen, clean up each other " +
+  "variant screen at most once, read only the kept screen, then update that " +
+  "same screen in one bounded pass. If a cleanup action reports a screen was " +
+  "already missing, continue. Use the exact file ids and tool instructions in " +
+  "the selected answer below. Do not repeat cleanup/read cycles, do not create " +
+  "a new index.html, and stop after the first successful screen update.";
 
 const variantSchema = z.object({
   id: z.string().min(1).describe("Stable variant id, e.g. 'minimal-focus'"),
@@ -609,8 +607,8 @@ export default defineAction({
               label: screen.label || optionName(index),
               value:
                 `Keep "${screen.label}" (${screen.filename}, file id ${screen.id}) ` +
-                `from variant set ${variantSetId}. Delete the other variant screens: ${otherScreens}. ` +
-                `Then call get-design-snapshot with designId ${designId} and fileId ${screen.id} (filename ${screen.filename}), then call edit-design with fileId ${screen.id} on that same kept file in a bounded single-file pass. Use mode "replace-file" when replacing the representative placeholder with the full chosen direction, or search/replace for smaller refinements. Do not call generate-design after this variant pick, do not create index.html, and do not resend a huge payload. Stop after the first successful edit-design save.`,
+                `from variant set ${variantSetId}. Delete each other variant screen at most once: ${otherScreens}. If delete-file says a screen is already missing, continue. ` +
+                `Then call get-design-snapshot exactly once with designId ${designId} and fileId ${screen.id} (filename ${screen.filename}), then call edit-design with fileId ${screen.id} on that same kept file in a bounded single-file pass. Use mode "replace-file" when replacing the representative placeholder with the full chosen direction, or search/replace for smaller refinements. Do not call generate-design after this variant pick, do not repeat delete/snapshot cycles, do not create index.html, and do not resend a huge payload. Stop after the first successful edit-design save.`,
             };
           }),
         },
@@ -628,7 +626,7 @@ export default defineAction({
       embed: true,
       fallbackInstructions: FALLBACK_INSTRUCTIONS,
       nextRequiredAction:
-        'Wait for the user to pick a screen in chat. Then delete the unchosen variant screens with delete-file, call get-design-snapshot with fileId for the chosen screen, and call edit-design with that same fileId in a bounded pass. Use mode "replace-file" when expanding the placeholder into the full chosen direction. Do not call generate-design after a variant pick. Stop after the first successful edit-design save.',
+        'Wait for the user to pick a screen in chat. Then delete each unchosen variant screen with delete-file at most once, call get-design-snapshot exactly once with fileId for the chosen screen, and call edit-design with that same fileId in a bounded pass. Use mode "replace-file" when expanding the placeholder into the full chosen direction. Do not repeat delete/snapshot cycles. Do not call generate-design after a variant pick. Stop after the first successful edit-design save.',
     };
   },
   link: ({ result }) => {

package/corpus/templates/design/app/hooks/use-question-flow.ts

@@ -41,7 +41,7 @@ export function useQuestionFlow(
         formattedAnswers,
         "",
         designId
-          ? 'Now continue the design. Honor any answer about variations: if the user asked to explore options, call present-design-variants with 2-5 concise directions using label, description, accentColor, and feature bullets; omit large content HTML when needed because the action can render compact representative screens - wait for their chat pick, delete the unchosen variant screens, call get-design-snapshot with fileId for the kept screen, then call edit-design on that same fileId in a bounded pass. Use mode "replace-file" when expanding the representative placeholder into the full chosen direction. Do not call generate-design after a variant pick. Stop after the first successful edit-design save. Otherwise call generate-design with one complete, renderable index.html first. Do not ask another question unless a required decision is still genuinely missing.'
+          ? 'Now continue the design. Honor any answer about variations: if the user asked to explore options, call present-design-variants with 2-5 concise directions using label, description, accentColor, and feature bullets; omit large content HTML when needed because the action can render compact representative screens - wait for their chat pick, delete each unchosen variant screen at most once, call get-design-snapshot exactly once with fileId for the kept screen, then call edit-design exactly once on that same fileId in a bounded pass. Use mode "replace-file" when expanding the representative placeholder into the full chosen direction. Do not repeat delete/snapshot cycles. Do not call generate-design after a variant pick. Stop after the first successful edit-design save. Otherwise call generate-design with one complete, renderable index.html first. Do not ask another question unless a required decision is still genuinely missing.'
           : "Now continue the design. Honor any answer about variations: use variants only if requested; otherwise generate one polished direction.",
       ]
         .filter(Boolean)
@@ -79,7 +79,7 @@ export function useQuestionFlow(
         formattedAnswers,
         "",
         designId
-          ? 'Now continue the design. Honor any answer about variations: if the user asked to explore options, call present-design-variants with 2-5 concise directions using label, description, accentColor, and feature bullets; omit large content HTML when needed because the action can render compact representative screens - wait for their chat pick, delete the unchosen variant screens, call get-design-snapshot with fileId for the kept screen, then call edit-design on that same fileId in a bounded pass. Use mode "replace-file" when expanding the representative placeholder into the full chosen direction. Do not call generate-design after a variant pick. Stop after the first successful edit-design save. Otherwise call generate-design with one complete, renderable index.html first. Do not ask another question unless a required decision is still genuinely missing.'
+          ? 'Now continue the design. Honor any answer about variations: if the user asked to explore options, call present-design-variants with 2-5 concise directions using label, description, accentColor, and feature bullets; omit large content HTML when needed because the action can render compact representative screens - wait for their chat pick, delete each unchosen variant screen at most once, call get-design-snapshot exactly once with fileId for the kept screen, then call edit-design exactly once on that same fileId in a bounded pass. Use mode "replace-file" when expanding the representative placeholder into the full chosen direction. Do not repeat delete/snapshot cycles. Do not call generate-design after a variant pick. Stop after the first successful edit-design save. Otherwise call generate-design with one complete, renderable index.html first. Do not ask another question unless a required decision is still genuinely missing.'
           : "Now continue the design. Honor any answer about variations: use variants only if requested; otherwise generate one polished direction.",
       ]
         .filter(Boolean)

package/corpus/templates/design/app/pages/DesignEditor.tsx

@@ -1573,7 +1573,7 @@ function designVariantGenerationDirectives(
     ...designSystemGenerationDirectives(designSystemId),
     "The user's prompt already asks to explore multiple directions, so DO NOT call `show-design-questions` first and DO NOT call `generate-design` first.",
     "Call `present-design-variants` with 2-5 concise directions (3 when unspecified). Prefer label, description, accentColor, and feature bullets; omit large content HTML when needed because the action can render compact representative screens.",
-    'Wait for the user\'s chat pick, delete the unchosen variant screens, call `get-design-snapshot` with `fileId` for the kept screen, then call `edit-design` on that same `fileId` in a bounded pass. Use `mode: "replace-file"` when expanding the representative placeholder into the full chosen direction. Do not call `generate-design` after a variant pick. Stop after the first successful `edit-design` save.',
+    'Wait for the user\'s chat pick, delete each unchosen variant screen at most once, call `get-design-snapshot` exactly once with `fileId` for the kept screen, then call `edit-design` exactly once on that same `fileId` in a bounded pass. Use `mode: "replace-file"` when expanding the representative placeholder into the full chosen direction. Do not repeat delete/snapshot cycles. Do not call `generate-design` after a variant pick. Stop after the first successful `edit-design` save.',
   ];
 }
 
@@ -1584,7 +1584,7 @@ function designGenerationDirectives(
   return [
     `Use the \`generate-design --designId="${designId}"\` action with exactly one complete, renderable \`index.html\` file first. The design already exists - DO NOT call create-design.`,
     ...designSystemGenerationDirectives(designSystemId),
-    'If the user asked to explore variations, call `present-design-variants` with 2-5 concise directions. Prefer label, description, accentColor, and feature bullets; omit large content HTML when needed because the action can render compact representative screens. Wait for their chat pick, delete the unchosen variant screens, call `get-design-snapshot` with `fileId` for the kept screen, then call `edit-design` on that same `fileId` in a bounded pass. Use `mode: "replace-file"` when expanding the representative placeholder into the full chosen direction. Do not call `generate-design` after a variant pick. Stop after the first successful `edit-design` save. Otherwise generate one polished first direction.',
+    'If the user asked to explore variations, call `present-design-variants` with 2-5 concise directions. Prefer label, description, accentColor, and feature bullets; omit large content HTML when needed because the action can render compact representative screens. Wait for their chat pick, delete each unchosen variant screen at most once, call `get-design-snapshot` exactly once with `fileId` for the kept screen, then call `edit-design` exactly once on that same `fileId` in a bounded pass. Use `mode: "replace-file"` when expanding the representative placeholder into the full chosen direction. Do not repeat delete/snapshot cycles. Do not call `generate-design` after a variant pick. Stop after the first successful `edit-design` save. Otherwise generate one polished first direction.',
     "Keep the first pass bounded enough to finish quickly: one self-contained Alpine.js + Tailwind CDN HTML document, polished but concise. Add 3-6 tweaks only when they naturally fit the design.",
     "After generate-design succeeds, stop and summarize what was created.",
   ];

package/corpus/templates/design/changelog/2026-07-01-design-recovers-sooner-when-an-agent-gets-stuck-preparing-a-.md

@@ -0,0 +1,6 @@
+---
+type: fixed
+date: 2026-07-01
+---
+
+Design recovers sooner when an agent gets stuck preparing a large design edit.

package/corpus/templates/dispatch/README.md

@@ -0,0 +1,34 @@
+# Dispatch
+
+The agent-native workspace control plane — a central Slack/Telegram inbox, a
+secrets vault, scheduled jobs, approvals, and an orchestrator agent that delegates
+work to the right specialist app over A2A.
+
+**Live app: [dispatch.agent-native.com](https://dispatch.agent-native.com)**
+
+Where other templates are domain apps (Mail, Calendar, Analytics, Brain),
+Dispatch is the app you run _alongside_ them to coordinate everything. It routes
+messages, holds shared credentials, runs cross-app jobs, and gates sensitive
+actions behind approvals.
+
+## Features
+
+- Central inbox for Slack DMs, Telegram, email, and A2A requests from other agents.
+- Orchestrator agent that triages and delegates domain work over A2A.
+- Secrets vault with per-app grants and an audit trail.
+- Workspace resources: shared skills, guardrails, agent profiles, and MCP servers.
+- Cross-app scheduled/recurring jobs.
+- Approval queue for destructive or external actions.
+
+## Develop locally
+
+Scaffold your own copy and run it:
+
+```bash
+npx @agent-native/core@latest create my-dispatch --standalone --template dispatch
+cd my-dispatch
+pnpm install
+pnpm dev
+```
+
+Full docs: [agent-native.com/docs/template-dispatch](https://agent-native.com/docs/template-dispatch).

package/corpus/templates/forms/README.md

@@ -0,0 +1,34 @@
+# Forms
+
+An open-source, agent-native alternative to Typeform and Google Forms. Describe
+the form you want, refine it in the visual editor, and publish a public form that
+stores submissions in your own SQL database.
+
+**Live app: [forms.agent-native.com](https://forms.agent-native.com)**
+
+Build forms conversationally or by hand — the agent updates the schema and the
+preview updates from SQL-backed state. Route new submissions wherever you need
+them.
+
+## Features
+
+- Build and edit forms conversationally, with a live preview.
+- Visual builder for labels, validation, options, and field order.
+- Shipped field types: text, email, number, long text, select, multi-select,
+  checkbox, radio, date, rating, and scale.
+- Submissions stored in SQL with a per-response detail view and dashboard.
+- Route submissions to webhooks, Slack, Discord, or Google Sheets.
+- Publish public form URLs with a thank-you message.
+
+## Develop locally
+
+Scaffold your own copy and run it:
+
+```bash
+npx @agent-native/core@latest create my-forms --standalone --template forms
+cd my-forms
+pnpm install
+pnpm dev
+```
+
+Full docs: [agent-native.com/docs/template-forms](https://agent-native.com/docs/template-forms).

package/corpus/templates/macros/README.md

@@ -0,0 +1,28 @@
+# Macros
+
+An agent-native, voice-driven calorie and macro tracker — an open-source take on
+MyFitnessPal-style logging. Speak or type what you ate and the agent logs the
+food, estimates calories and macros, and keeps your daily stats up to date.
+
+> **Internal/experimental template.** Macros is not shown in the public template
+> pickers. It exists as a reference app and demo.
+
+**Live app: [macros.agent-native.com](https://macros.agent-native.com)**
+
+## Features
+
+- Log foods and meals by voice or text through the agent.
+- Automatic calorie and macro estimation.
+- Voice corrections and quick edits.
+- Daily and historical stats.
+
+## Develop locally
+
+Scaffold your own copy and run it:
+
+```bash
+npx @agent-native/core@latest create my-macros --standalone --template macros
+cd my-macros
+pnpm install
+pnpm dev
+```

package/corpus/templates/mail/README.md

@@ -0,0 +1,35 @@
+# Mail
+
+An open-source, agent-native alternative to Superhuman. An agent-powered,
+keyboard-first email client for Gmail — the agent can read, draft, send, and
+organize email for you, and the codebase is yours to own.
+
+**Live app: [mail.agent-native.com](https://mail.agent-native.com)**
+
+Connect one or more Gmail accounts and drive a fast, keyboard-first inbox
+yourself, or ask the agent to do anything you can. The agent always knows which
+view you're in and which thread is open, so "archive this" just works.
+
+## Features
+
+- Keyboard-first triage (`J`/`K` to move, `E` to archive, `R` to reply, `C` to compose).
+- Multiple Gmail accounts in one inbox.
+- Ask the agent to summarize, draft, reply, archive, or bulk-clean your inbox.
+- Natural-language auto-triage rules (label, archive, mark read, star, trash).
+- Open and click tracking on emails you send.
+- Search across every connected inbox with one query.
+- Queue drafts for review from teammates or Slack.
+
+## Develop locally
+
+Scaffold your own copy and run it:
+
+```bash
+npx @agent-native/core@latest create my-mail --standalone --template mail
+cd my-mail
+pnpm install
+pnpm dev
+```
+
+Connecting Gmail in dev needs a Google OAuth client — see the docs for setup.
+Full docs: [agent-native.com/docs/template-mail](https://agent-native.com/docs/template-mail).

package/corpus/templates/plan/README.md

@@ -1,133 +1,45 @@
-# Agent-Native Plan
+# Plan
 
-Agent-Native Plan is structured visual plan mode for coding agents. It turns a
-normal Markdown/Codex/Claude Code plan into a visual review surface with
-editable rich blocks, diagrams, wireframes, prototype options, annotated code
-walkthroughs and file trees, code previews, annotations, share links, feedback,
-and HTML export.
+Structured visual plan mode for coding agents. Plan turns an ordinary
+Codex / Claude Code / Markdown plan into a reviewable document — diagrams,
+wireframes, prototype options, annotated code walkthroughs, file trees, comments,
+share links, and HTML export.
 
-## Install
+**Live app: [plan.agent-native.com](https://plan.agent-native.com)**
 
-Use the Agent-Native CLI. This is the recommended setup because it installs the
-Plan skill instructions, registers the hosted Plan MCP connector, and runs the
-client-specific auth/setup flow in one step:
+## Install (recommended)
+
+Most people install Plan as a skill, not a scaffolded app. One CLI command adds
+the `/visual-plan` and `/visual-recap` skills plus the hosted Plan connector to
+your coding agent:
 
 ```sh
 npx @agent-native/core@latest skills add visual-plan
 ```
 
-You do not need to wire the MCP server separately.
-
-Supported aliases include:
-
-- `npx @agent-native/core@latest skills add visual-plan`
-- `npx @agent-native/core@latest skills add visual-recap`
-
-Restart or reload the host if the tools are not visible immediately.
-
-## Use
-
-It comes down to two commands: `/visual-plan` to plan before the agent builds,
-and `/visual-recap` to review a change after it lands.
-
-Type `/visual-plan` when you want a fresh plan before the agent builds, or when
-you already have a Codex, Claude Code, Markdown, or pasted plan and want the
-agent to preserve it while adding a richer visual review surface.
-
-Type `/visual-recap` when you want a high-level visual code-review recap from a
-PR, commit, branch, or git diff. A recap is an aid for review, not a replacement
-for reading the actual diff.
-
-Command behavior:
-
-- `/visual-plan` creates a new rich visual plan with docs-level detail, diagrams,
-  detailed wireframes/mockups when UI is involved, functional prototypes when
-  the interaction feel matters, tradeoffs, open questions, annotated code
-  walkthroughs and file trees for code work, code previews, and feedback prompts.
-  When an existing plan is provided, it builds from that plan instead of starting
-  over.
-- `/visual-recap` creates a reverse plan from code that already changed:
-  file-tree, diff, data-model, API, and columns blocks that let a
-  reviewer scan the shape of a PR before reading line-by-line.
-
-## Normal Planning Flow
-
-`/visual-plan` remains the main planning command. Agents should use their normal
-planning flow first: inspect the codebase, gather context, ask clarifying
-questions through the host's native ask-user-question tools when needed, then
-create the visual plan.
-
-The document should stay close to the Markdown plan a coding agent would
-normally produce. Diagrams, wireframes, mockups, and annotations are additive
-review aids.
-
-Plans should be visual by default:
+Then use `/visual-plan` to plan before the agent builds, and `/visual-recap` to
+review a change after it lands. Reviewers you share with edit as a guest and sign
+in only to save or share.
 
-- diagrams for architecture, data flow, dependencies, and state machines
-- detailed wireframes and quick mockups for UI work, including layout regions,
-  controls, states, empty/loading/error paths, and copy placeholders
-- tabs for multiple diagrams, wireframes, mockups, and design options so rich
-  plans do not become long stacks of visuals
-- prototype options when interaction or design direction is uncertain
-- annotated code walkthroughs and file trees for code work: files,
-  symbols/components/functions, planned changes, concise code snippets, and
-  explicit editor-open affordances
-- plannotator-style comments, corrections, and annotations
-- review prompts for options, open questions, risky assumptions, and choices
-- README-like details when helpful: commands, MCP/link fallback, tool behavior,
-  data shape, scope, and what is deferred
+## Features
 
-Review recaps use the same plan surface, but their center of gravity is
-before/after review. Use `columns` as the generic side-by-side layout primitive
-for structured before/after comparisons, and use split `diff` blocks for literal
-code hunks. Use prose beside `data-model` or `api-endpoint` blocks when the
-important change is semantic API or schema compatibility.
+- Rich, editable plan blocks: diagrams, wireframes, prototypes, and annotations.
+- Annotated code walkthroughs and file trees for code work.
+- Reviewer comments, feedback, and private share links.
+- `/visual-recap` reverse-plans a PR, commit, branch, or diff for review.
+- MDX source sync so plans can be committed to a repo.
+- Optional PR Visual Recap GitHub Action.
 
-## Review Loop
+## Develop locally
 
-1. The agent creates a plan and opens the MCP app inline or as a browser link.
-2. The user reacts to visuals instead of reading a wall of Markdown.
-3. The user annotates, corrects, chooses options, or asks for a clearer visual.
-4. The agent reads structured feedback before editing and updates the plan or
-   implementation.
-5. The user can keep the plan local or sign in to share a private review link.
+Forking the template is the secondary path, for self-hosting or customizing the
+Plan app itself:
 
-Local development can use the framework's auto-created dev account. Hosted
-persistence, private sharing, reviewer links, and team feedback use account
-login, with Google sign-in available when OAuth env vars are configured.
-
-## Hosted App
-
-The hosted MCP app is expected at:
-
-- App: `https://plan.agent-native.com`
-- MCP: `https://plan.agent-native.com/_agent-native/mcp`
-
-The local template remains useful for development and self-hosting.
-
-## PR Visual Recaps
-
-When you install Plans interactively, the CLI asks whether you also want the PR
-Visual Recap GitHub Action. You can add it explicitly at any time:
-
-```sh
-npx @agent-native/core@latest skills add visual-plan --with-github-action
-```
-
-That writes `.github/workflows/pr-visual-recap.yml`. Then run the setup helper to
-configure GitHub Actions secrets/variables where possible and print any missing
-manual steps:
-
-```sh
-npx @agent-native/core@latest recap setup
-npx @agent-native/core@latest recap doctor
+```bash
+npx @agent-native/core@latest create my-plan --standalone --template plan
+cd my-plan
+pnpm install
+pnpm dev
 ```
 
-The hosted default needs `PLAN_RECAP_TOKEN` plus `ANTHROPIC_API_KEY` for the
-default Claude backend. `PLAN_RECAP_APP_URL` is only needed when self-hosting the
-Plan app, and Codex users can set `VISUAL_RECAP_AGENT=codex` with
-`OPENAI_API_KEY`.
-
-The workflow should treat recap generation as informational only: it can show a
-non-required `Visual Recap` check while it runs and update a sticky PR comment
-with the recap link, but reviewers still own the real diff review.
+Full docs: [agent-native.com/docs/template-plan](https://agent-native.com/docs/template-plan).

package/corpus/templates/plan/app/global.css

@@ -156,7 +156,7 @@
   }
 
   .plan-content-surface[data-recap-screenshot-theme] .plan-document-shell {
-    padding: 10px;
+    padding: 0;
   }
 
   .plan-content-surface[data-recap-screenshot-theme] .plan-document-body {

package/corpus/templates/slides/README.md

@@ -0,0 +1,34 @@
+# Slides
+
+An open-source, agent-native alternative to Google Slides, Pitch, and PowerPoint.
+Generate full decks from a prompt, edit slides visually, and present full-screen.
+
+**Live app: [slides.agent-native.com](https://slides.agent-native.com)**
+
+Ask the agent for "a 10-slide pitch deck for a coffee subscription service" and
+watch it stream in slide-by-slide, then refine it visually or by prompt. Anything
+you can do in the editor, the agent can do too.
+
+## Features
+
+- Generate full presentation decks from a prompt.
+- Edit slides visually with a bubble menu and slash-menu blocks.
+- AI image generation, stock photo search, and company logo lookup.
+- Present full-screen with keyboard navigation and speaker notes.
+- Real-time collaboration, comments, and public read-only share links.
+- Import from PDF, PPTX, DOCX, Google Docs, or a URL; export to PPTX, Google
+  Slides, or HTML.
+- Design systems and per-deck version history.
+
+## Develop locally
+
+Scaffold your own copy and run it:
+
+```bash
+npx @agent-native/core@latest create my-slides --standalone --template slides
+cd my-slides
+pnpm install
+pnpm dev
+```
+
+Full docs: [agent-native.com/docs/template-slides](https://agent-native.com/docs/template-slides).