@agent-native/core 0.93.0 → 0.94.0

package/corpus/core/docs/content/sharing.mdx

@@ -1,13 +1,13 @@
 ---
 title: "Sharing & Privacy"
-description: "Google-Docs-style sharing, built into the framework. Every user-created resource — docs, dashboards, designs, decks, clips, recordings, forms — gets the same private-by-default model with one consistent share UI."
+description: "Familiar, consistent sharing built into the framework. Every user-created resource — docs, dashboards, designs, decks, clips, recordings, forms — gets the same private-by-default model with one consistent share UI."
 ---
 
 # Sharing & Privacy
 
 Every resource a user creates in an agent-native app — a document, a dashboard, a design, a deck, a screen recording, a meeting transcript, a form, a booking link — is **private to the creator by default**. Other people see it only when the creator explicitly shares it, or changes its visibility to `org` or `public`.
 
-It looks and works like Google Docs. The same share button, the same dialog, the same three-tier visibility model, the same per-user/per-org grants — across every template, with no per-app reinvention.
+It's one familiar sharing model everywhere: the same share button, the same dialog, the same three-tier visibility model, the same per-user/per-org grants — across every template, with no per-app reinvention.
 
 ## Why one model {#why}
 
@@ -92,7 +92,7 @@ Every template that stores user-authored work uses this model. Concretely:
 - **Content** — documents
 - **Slides** — decks
 - **Design** — designs and assets
-- **Clips** — screen recordings (Loom-style)
+- **Clips** — screen recordings
 - **Plan** — visual plans and PR recaps
 - **Forms** — form definitions
 - **Calendar** — events and booking links
@@ -115,7 +115,7 @@ Every shareable resource gets a share button in its header. Clicking it opens a
 
 - Visibility selector (`Private` / `Organization` / `Public link`).
 - "Add people or teams" autocomplete — search users in the org or paste an email.
-- A Google Docs-style `Notify people` checkbox for individual email grants.
+- A `Notify people` checkbox for individual email grants.
 - A list of current grants with role pickers and a remove control.
 - A copy-link button that respects the current visibility.
 
@@ -294,7 +294,7 @@ export const deckShares = createSharesTable("deck_shares");
 
 One registration call in `server/db/index.ts`:
 
-```ts
+```ts filename="server/db/index.ts"
 import { registerShareableResource } from "@agent-native/core/sharing";
 
 registerShareableResource({
@@ -339,9 +339,9 @@ For resources that execute code or carry elevated trust (like extensions), set `
 
 Sharing rides on the framework's broader data-scoping model — list/read/write access to ownable tables goes through `accessFilter()` / `resolveAccess()` / `assertAccess()`, and `org_id`-tagged resources are invisible across orgs. See [Security → Data Scoping](/docs/security#data-scoping) for the full pipeline, the CI guard, and the threat surface.
 
-## See also {#see-also}
+## What's next {#see-also}
 
-- [Security & Data Scoping](/docs/security) — the access-filter and ownership model that sharing rides on.
-- [Authentication](/docs/authentication) — sessions, organizations, and how identity flows into the request context.
-- [Extensions](/docs/extensions#sharing) — sharing in the sandboxed mini-app surface.
-- [Creating Templates](/docs/creating-templates) — wiring `ownableColumns` into a new template's schema.
+- [**Security — Data Scoping**](/docs/security#data-scoping) — the access-filter and ownership model that sharing rides on
+- [**Authentication**](/docs/authentication) — sessions, organizations, and how identity flows into the request context
+- [**Extensions**](/docs/extensions#sharing) — sharing in the sandboxed mini-app surface
+- [**Creating Templates**](/docs/creating-templates) — wiring `ownableColumns` into a new template's schema

package/corpus/core/docs/content/skills-guide.mdx

@@ -5,7 +5,7 @@ description: "How skills work in agent-native: framework skills, domain skills,
 
 # Skills Guide
 
-Skills are Markdown files that give the agent deep knowledge about specific patterns and workflows.
+Skills are Markdown files that give the agent deep knowledge about specific patterns and workflows. Instead of cramming every rule into one system prompt, you split knowledge into focused files the agent loads only when a task actually needs them — keeping the default context small while still letting the agent go deep on demand.
 
 ## What are skills {#what-are-skills}
 
@@ -124,7 +124,11 @@ Current app-backed skills include `visual-plan`, `visual-recap`, and
 `visualize-repo` 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).
+<Callout tone="info">
+
+**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).
+
+</Callout>
 
 ## Creating custom skills {#creating-skills}
 
@@ -179,7 +183,11 @@ The frontmatter `name` and `description` are used by the agent's tool system for
 
 Save the file at `.agents/skills/my-skill/SKILL.md`. The directory name should match the `name` in frontmatter.
 
-> **See also:** [Writing Agent Instructions](/docs/writing-agent-instructions) for how to word skill descriptions, apply progressive disclosure, and keep `AGENTS.md` lean. Both pages use the `project-imports` skill as a running example.
+<Callout tone="info">
+
+**See also:** [Writing Agent Instructions](/docs/writing-agent-instructions) for how to word skill descriptions, apply progressive disclosure, and keep `AGENTS.md` lean. Both pages use the `project-imports` skill as a running example.
+
+</Callout>
 
 ## Skill scope: runtime vs dev {#skill-scope}
 
@@ -269,33 +277,37 @@ This replaces the old hack of relying on Claude Code only reading `.claude/skill
 
 </Diagram>
 
-> **See also:** [Writing Agent Instructions](/docs/writing-agent-instructions) for how to word skill descriptions, apply progressive disclosure, and keep `AGENTS.md` lean.
-
 ## Skills vs AGENTS.md {#skills-vs-agents-md}
 
-> **AGENTS.md** — The overview. Lists all scripts, describes the data model, explains the app architecture. The agent reads this first to understand the app.
->
-> **Skills** — Deep dives. Each skill focuses on one pattern with detailed rules, code examples, and do/don't lists. The agent reads these when it needs to follow a specific pattern.
+<Callout tone="info">
+
+**AGENTS.md** — The overview. Lists all scripts, describes the data model, explains the app architecture. The agent reads this first to understand the app.
+
+**Skills** — Deep dives. Each skill focuses on one pattern with detailed rules, code examples, and do/don't lists. The agent reads these when it needs to follow a specific pattern.
+
+</Callout>
 
 `AGENTS.md` tells the agent _what_ the app does. Skills tell the agent _how_ to do specific things correctly. Both are needed — `AGENTS.md` for orientation, skills for execution.
 
 ## Skills vs memory {#skills-vs-memory}
 
-> **Skills** — Authored, reusable how-to guides. Apply to every user, invoked on demand when the task matches.
->
-> **Memory (`LEARNINGS.md` / `memory/MEMORY.md`)** — Shared project learnings and personal structured memory loaded every turn.
+<Callout tone="info">
+
+**Skills** — Authored, reusable how-to guides. Apply to every user, invoked on demand when the task matches.
+
+**Memory (`LEARNINGS.md` / `memory/MEMORY.md`)** — Shared project learnings and personal structured memory loaded every turn.
+
+</Callout>
 
 If the knowledge applies to _everyone_ working in the app ("always prefer CTEs over subqueries"), it's a skill or shared `LEARNINGS.md`. If it's about _this particular user_ ("Steve likes concise answers"), it belongs in `memory/MEMORY.md`. See [Workspace Memory](/docs/workspace#memory) for the full treatment.
 
----
+## Skills vs SQL resources {#skills-vs-resources}
 
-# Advanced
+This page frames a skill as a file at `.agents/skills/<name>/SKILL.md`. [Workspace](/docs/workspace#skills) frames the same skill as a SQL resource at path `skills/<slug>/SKILL.md`, scoped workspace/shared/personal. These are the same concept from two angles: Code mode reads and writes the file directly; App mode stores it as a resource row so it works without a filesystem. Author the content using this page's format either way.
 
 ## App-backed skills — full details {#app-backed-skills-full}
 
-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.
+The manifest format, CLI commands, marketplace adapters, and auto-update hashing behind [app-backed skills](#app-backed-skills) in full:
 
 Each app-backed skill starts with `agent-native.app-skill.json` at the app root:
 
@@ -412,3 +424,10 @@ npx @agent-native/core@latest skills update scaffold --project
 `AGENTS.md` and `.agents/skills` stay canonical. The update command also repairs
 Claude compatibility links (`CLAUDE.md` and `.claude/skills`) so Claude Code sees
 the same instructions without maintaining a second copy.
+
+## What's next {#whats-next}
+
+- [**Writing Agent Instructions**](/docs/writing-agent-instructions) — word skill descriptions and split guidance across AGENTS.md, skills, and memory
+- [**Workspace**](/docs/workspace#skills) — where skills live as SQL resources in App mode
+- [**Agent Mentions**](/docs/agent-mentions) — the `/`-command trigger that invokes a skill in chat
+- [**Plan plugin & marketplace**](/docs/plan-plugin) — a real app-backed skill's end-to-end install and auto-update flow

package/corpus/core/docs/content/template-analytics.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Analytics"
-description: "Ask analytics questions in plain English, get charts and dashboards back. An open-source replacement for Amplitude, Mixpanel, and Looker."
+description: "Ask analytics questions in plain English, get charts and dashboards back — connect your own warehouse and event sources, and own the code and the data."
 ---
 
 # Analytics
@@ -11,12 +11,12 @@ Ask analytics questions in plain English, get charts and dashboards back. The ag
   <Screen
     surface="desktop"
     html={
-      "<div style='display:flex;flex-direction:column;gap:14px;padding:18px;min-height:500px;box-sizing:border-box'><h1 style='margin:0'>Agent-Native Templates</h1><p class='wf-muted' style='margin:0'>Adoption and engagement across the last 12 weeks.</p><div style='display:grid;grid-template-columns:repeat(3,1fr);gap:12px'><div class='wf-card'><small class='wf-muted'>Weekly active users</small><br/><strong>24,318</strong><br/><span class='wf-pill accent'>+12.4%</span></div><div class='wf-card'><small class='wf-muted'>New signups</small><br/><strong>1,842</strong><br/><span class='wf-pill accent'>+8.7%</span></div><div class='wf-card'><small class='wf-muted'>Revenue MRR</small><br/><strong>$48,210</strong><br/><span class='wf-pill accent'>+21.3%</span></div></div><div style='display:grid;grid-template-columns:1fr 1fr;gap:12px;flex:1'><div class='wf-card' style='display:flex;flex-direction:column;gap:10px'><strong>Weekly active users</strong><div style='flex:1;display:flex;align-items:end;gap:8px'><div style='height:38%;flex:1;background:var(--wf-accent-soft)'></div><div style='height:44%;flex:1;background:var(--wf-accent-soft)'></div><div style='height:58%;flex:1;background:var(--wf-accent-soft)'></div><div style='height:74%;flex:1;background:var(--wf-accent-soft)'></div></div></div><div class='wf-card' style='display:flex;flex-direction:column;gap:10px'><strong>Revenue over time</strong><div style='flex:1;display:flex;align-items:end;gap:8px'><div style='height:32%;flex:1;background:var(--wf-accent-soft)'></div><div style='height:48%;flex:1;background:var(--wf-accent-soft)'></div><div style='height:63%;flex:1;background:var(--wf-accent-soft)'></div><div style='height:80%;flex:1;background:var(--wf-accent-soft)'></div></div></div></div><div class='wf-card'><strong>Signups by source</strong><br/><small class='wf-muted'>Lower chart begins below the main charts.</small></div></div>"
+      "<div style='display:flex;flex-direction:column;gap:14px;padding:18px;min-height:500px;box-sizing:border-box'><h1 style='margin:0'>Agent-Native Templates</h1><p class='wf-muted' style='margin:0'>Adoption and engagement across the last 12 weeks.</p><div style='display:grid;grid-template-columns:repeat(3,1fr);gap:12px'><div class='wf-card'><small class='wf-muted'>Weekly active users</small><br/><strong>24,318</strong><br/><span class='wf-pill accent'>+12.4%</span></div><div class='wf-card'><small class='wf-muted'>New signups</small><br/><strong>1,842</strong><br/><span class='wf-pill accent'>+8.7%</span></div><div class='wf-card'><small class='wf-muted'>Revenue MRR</small><br/><strong>$48,210</strong><br/><span class='wf-pill accent'>+21.3%</span></div></div><div style='display:grid;grid-template-columns:1fr 1fr;gap:12px;flex:1'><div class='wf-card' style='display:flex;flex-direction:column;gap:10px'><strong>Weekly active users</strong><div style='flex:1;display:flex;align-items:end;gap:8px'><div style='height:38%;flex:1;background:var(--wf-accent-soft)'></div><div style='height:44%;flex:1;background:var(--wf-accent-soft)'></div><div style='height:58%;flex:1;background:var(--wf-accent-soft)'></div><div style='height:74%;flex:1;background:var(--wf-accent-soft)'></div></div></div><div class='wf-card' style='display:flex;flex-direction:column;gap:10px'><strong>Revenue over time</strong><div style='flex:1;position:relative;background:linear-gradient(115deg,var(--wf-accent-soft) 0%,transparent 60%);border-radius:6px'><div style='position:absolute;inset:0;display:flex;align-items:end;gap:10px;padding:0 6px 6px'><span style='width:7px;height:7px;border-radius:50%;background:var(--wf-accent);margin-bottom:14%'></span><span style='width:7px;height:7px;border-radius:50%;background:var(--wf-accent);margin-bottom:30%'></span><span style='width:7px;height:7px;border-radius:50%;background:var(--wf-accent);margin-bottom:48%'></span><span style='width:7px;height:7px;border-radius:50%;background:var(--wf-accent);margin-bottom:72%'></span></div></div></div></div><div class='wf-card'><strong>Signups by source</strong><div style='display:flex;flex-direction:column;gap:6px;margin-top:10px'><div style='display:flex;align-items:center;gap:8px'><span class='wf-muted' style='width:60px;font-size:11px'>Organic</span><div class='wf-box' style='height:12px;width:70%;padding:0'></div></div><div style='display:flex;align-items:center;gap:8px'><span class='wf-muted' style='width:60px;font-size:11px'>Referral</span><div class='wf-box' style='height:12px;width:45%;padding:0'></div></div><div style='display:flex;align-items:center;gap:8px'><span class='wf-muted' style='width:60px;font-size:11px'>Paid ads</span><div class='wf-box' style='height:12px;width:28%;padding:0'></div></div></div></div></div>"
     }
   />
 </WireframeBlock>
 
-It's an open-source replacement for Amplitude, Mixpanel, and Looker — for teams that want to own the code, the queries, and the data.
+It's an open-source analytics stack for teams that want to own the code, the queries, and the data.
 
 <Diagram id="doc-block-9n9ub7" title="Question to chart" summary="The agent consults the data dictionary, writes SQL, validates it against the warehouse, then renders a chart or saves a panel.">
 
@@ -125,11 +125,6 @@ Create a new Analytics app from the CLI:
 
 ```bash
 npx @agent-native/core@latest create my-analytics --standalone --template analytics
-```
-
-Local dev:
-
-```bash
 cd my-analytics
 pnpm install
 pnpm dev
@@ -371,3 +366,11 @@ To add a new data source, drop a script in `actions/` that calls the provider an
 To add a new chart type, extend the `ChartType` union in `app/pages/adhoc/sql-dashboard/types.ts`, handle it in `SqlChartCard.tsx`, and the agent can use it in any panel.
 
 For the broader pattern on extending templates, see the [Skills guide](/docs/skills-guide) and [Actions](/docs/actions).
+
+## What's next
+
+- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
+- [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync
+- [**Actions**](/docs/actions) — the action system dashboards, analyses, and the dictionary are built on
+- [**Sharing**](/docs/sharing) — the share-grant model dashboards and analyses build on
+- [**Automations**](/docs/automations) — schedule recurring dashboard refreshes or alerts

package/corpus/core/docs/content/template-assets.mdx

@@ -88,6 +88,18 @@ When you open the app, the selected library, prompt, references, and generated c
 - **Other apps need an asset picker or generator** — Slides, Design, Content, a blog editor, or a site builder can embed the picker or call Assets over A2A.
 - **You want brand media available from your coding agent** — Codex, Claude Code, Claude, or ChatGPT can generate and pick assets without leaving the chat.
 
+## What you can do with it
+
+- **Create asset libraries.** Group reference images, videos, canonical logos, style notes, palettes, folders, and generated output by brand, campaign, product, or category.
+- **Generate through chat.** The home composer and library Generate controls send the prompt to the agent with `sendToAgentChat()`, so users can inspect variants, give feedback, and iterate.
+- **Generate images and videos.** Builder-managed image generation is available when enabled, and Gemini powers video generation plus the manual image fallback.
+- **Upload and describe references.** Add images or videos from the library UI or prompt composer attachment button, then search by title, description, alt text, prompt, model, media type, status, role, folder, or collection.
+- **Keep a generation audit log.** Every run records prompts, model, aspect ratio, references, source asset, lineage, generated assets, status, errors, and timestamps for later design review.
+- **Preserve logo accuracy.** The agent can generate a placeholder area and the server composites the uploaded canonical logo onto the final image instead of relying on the image model to redraw it.
+- **Embed as a picker.** Other apps can iframe `/picker` and listen for the `chooseAsset` event from `@agent-native/embedding`, turning Assets into an asset picker/generator for blog editors, site builders, slide decks, and custom apps. The picker also emits the legacy `chooseImage` alias for existing image-only hosts.
+- **Install as an app-backed skill.** The `agent-native.app-skill.json` manifest exports an Assets skill plus MCP connector metadata so marketplaces can install the app, its instructions, and its picker together.
+- **Serve other agents.** Slides, Design, Content, Mail, and Dispatch can call Assets through A2A to list libraries, generate batches, create videos, refine an asset, fetch exports, and render inline previews where embedding is allowed.
+
 ## Getting started
 
 Live demo: [assets.agent-native.com](https://assets.agent-native.com).
@@ -249,18 +261,6 @@ For deeper prompting guidance on the underlying models, see OpenAI's
 - "Turn this uploaded diagram into a cleaner product explainer image."
 - "Create a video storyboard and save the best frame set to this library."
 
-## What you can do with it
-
-- **Create asset libraries.** Group reference images, videos, canonical logos, style notes, palettes, folders, and generated output by brand, campaign, product, or category.
-- **Generate through chat.** The home composer and library Generate controls send the prompt to the agent with `sendToAgentChat()`, so users can inspect variants, give feedback, and iterate.
-- **Generate images and videos.** Builder-managed image generation is available when enabled, and Gemini powers video generation plus the manual image fallback.
-- **Upload and describe references.** Add images or videos from the library UI or prompt composer attachment button, then search by title, description, alt text, prompt, model, media type, status, role, folder, or collection.
-- **Keep a generation audit log.** Every run records prompts, model, aspect ratio, references, source asset, lineage, generated assets, status, errors, and timestamps for later design review.
-- **Preserve logo accuracy.** The agent can generate a placeholder area and the server composites the uploaded canonical logo onto the final image instead of relying on the image model to redraw it.
-- **Embed as a picker.** Other apps can iframe `/picker` and listen for the `chooseAsset` event from `@agent-native/embedding`, turning Assets into an asset picker/generator for blog editors, site builders, slide decks, and custom apps. The picker also emits the legacy `chooseImage` alias for existing image-only hosts.
-- **Install as an app-backed skill.** The `agent-native.app-skill.json` manifest exports an Assets skill plus MCP connector metadata so marketplaces can install the app, its instructions, and its picker together.
-- **Serve other agents.** Slides, Design, Content, Mail, and Dispatch can call Assets through A2A to list libraries, generate batches, create videos, refine an asset, fetch exports, and render inline previews where embedding is allowed.
-
 ## Using it from your coding agent
 
 Generate and pick brand media without leaving Codex, Claude Code, Claude, or ChatGPT.
@@ -303,10 +303,13 @@ Generate and pick brand media without leaving Codex, Claude Code, Claude, or Cha
 
 The rest of this doc is for anyone forking the Assets template or extending it.
 
-### Scaffolding
+### Quick start
 
 ```bash
 npx @agent-native/core@latest create my-assets --standalone --template assets
+cd my-assets
+pnpm install
+pnpm dev
 ```
 
 ### Data model

package/corpus/core/docs/content/template-brain.mdx

@@ -203,7 +203,7 @@ Postgres, Neon, D1, Turso, and similar hosts. Application state mirrors the
 current route, filters, and selected IDs so the agent always knows the current
 navigation and selection.
 
-Brain's schema lives in `templates/brain/server/db/schema.ts`. Eight tables:
+Brain's schema lives in `templates/brain/server/db/schema.ts`. Nine tables:
 
 | Table                    | What it holds                                                                                                                                  |
 | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -551,3 +551,5 @@ Ask the agent to make changes for you — it can edit its own source. See
 - [**Dispatch template**](/docs/template-dispatch) — the scaffolded coordination app
 - [**Workspace**](/docs/workspace) — shared resources across apps
 - [**A2A Protocol**](/docs/a2a-protocol) — cross-app delegation
+- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
+- [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync

package/corpus/core/docs/content/template-calendar.mdx

@@ -1,11 +1,11 @@
 ---
 title: "Calendar"
-description: "An agent-powered calendar with Google Calendar sync and Calendly-style booking links. Schedule, find slots, and manage availability through plain English."
+description: "An agent-powered calendar with Google Calendar sync and shareable booking pages. Schedule, find slots, and manage availability through plain English."
 ---
 
 # Calendar
 
-An agent-powered calendar app. Connect your Google Calendar and the agent can read your schedule, find free slots, create events, and manage Calendly-style booking links — all in plain English. It replaces the Google Calendar + Calendly combo with one app you own.
+An agent-powered calendar app. Connect your Google Calendar and the agent can read your schedule, find free slots, create events, and manage shareable booking links — all in plain English. It brings your calendar and public booking pages into one app you own.
 
 <WireframeBlock id="doc-block-6wsrao">
   <Screen
@@ -167,7 +167,7 @@ Under the hood the agent calls actions like `list-events`, `check-availability`,
 Defined in `templates/calendar/server/db/schema.ts`. Only non-event data is stored locally:
 
 - `bookings` — confirmed appointments from public booking pages. Stores name, email, start, end, slug, optional notes, custom field responses, meeting link, a `cancelToken` for the public manage URL, and a `confirmed` or `cancelled` status.
-- `booking_links` — the Calendly-style link definitions. Slug, title, description, primary `duration`, optional `durations` list, `customFields`, `conferencing`, `color`, and an `isActive` flag. Uses the framework's `ownableColumns` so the sharing system applies.
+- `booking_links` — the booking-page link definitions. Slug, title, description, primary `duration`, optional `durations` list, `customFields`, `conferencing`, `color`, and an `isActive` flag. Uses the framework's `ownableColumns` so the sharing system applies.
 - `booking_slug_redirects` — remembers old slugs when a link is renamed so existing public URLs keep working.
 - `booking_link_shares` — share grants for booking links.
 
@@ -181,7 +181,7 @@ Defined in `templates/calendar/server/db/schema.ts`. Only non-event data is stor
     {
       id: "booking_links",
       name: "booking_links",
-      note: "Calendly-style link definitions (ownable)",
+      note: "Booking-page link definitions (ownable)",
       fields: [
         {
           name: "id",
@@ -375,3 +375,11 @@ Every part of the app is editable source. Start here:
 - `templates/calendar/shared/api.ts` — the shared TypeScript types (`AvailabilityConfig`, `BookingLink`, `ExternalCalendar`, etc.) used by both the server and the client.
 
 If you add a feature, remember to update all four areas: UI, action, skill or AGENTS.md entry, and any application state the agent needs to see. That is what keeps the agent and the UI in parity.
+
+## What's next
+
+- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
+- [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync
+- [**Mail**](/docs/template-mail) — a sibling domain template covering inbox and automations
+- [**Automations**](/docs/automations) — trigger jobs off calendar and booking events
+- [**Sharing**](/docs/sharing) — the share-grant model booking links build on

package/corpus/core/docs/content/template-chat.mdx

@@ -111,7 +111,7 @@ That's the point. Chat is a thin, useful default shell for your own agent, not a
 ## Scaffolding {#scaffolding}
 
 ```bash
-npx @agent-native/core@latest create my-chat-app --template chat
+npx @agent-native/core@latest create my-chat-app --standalone --template chat
 cd my-chat-app
 pnpm install
 pnpm dev
@@ -162,8 +162,7 @@ Use it for scheduled jobs, queues, CLI loops, or external-agent workflows where
 
 The chat page is intentionally thin:
 
-```tsx
-// app/routes/_index.tsx
+```tsx filename="app/routes/_index.tsx"
 import { AgentChatSurface } from "@agent-native/core/client";
 
 export default function ChatRoute() {
@@ -196,7 +195,8 @@ The agent should add a Drizzle schema, actions, route, navigation, and instructi
 
 ## What's next
 
-- [**Getting Started**](/docs) — build the chat-first path from action to inline result to app page
+- [**Getting Started**](/docs/getting-started) — build the chat-first path from action to inline result to app page
+- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every domain template to start from instead
 - [**Agent Surfaces**](/docs/agent-surfaces) — chat, inline UI, app pages, embedded, automation, and external-agent patterns
 - [**Actions**](/docs/actions) — the action system chat and UI both call
 - [**Native Chat UI**](/docs/native-chat-ui) — chat surface primitives and runtime options

package/corpus/core/docs/content/template-clips.mdx

@@ -17,7 +17,7 @@ A capture-everything app: screen recordings, meeting notes from your calendar, a
   />
 </WireframeBlock>
 
-Think along the lines of Loom + Granola + Wispr Flow rolled into one app — but the agent is a first-class editor across every surface, and the recordings, meetings, and dictations are yours, not a SaaS vendor's. Clips also makes shared recordings agent-readable: paste a public Clips share link or a temporary **Copy for agent** link into an agent and it can "hear" the transcript as text and "see" timestamped screen frames as images — no raw video needed. Frame-viewing works in any image-capable agent (ChatGPT, Claude Code, Cursor, Codex); text-only web chats still get the full transcript and can take a frame you upload.
+Async screen recordings, calendar-synced meeting notes, and push-to-talk voice dictation rolled into one app — the agent is a first-class editor across every surface, and the recordings, meetings, and dictations are yours, not a SaaS vendor's. Clips also makes shared recordings agent-readable: paste a public Clips share link or a temporary **Copy for agent** link into an agent and it can "hear" the transcript as text and "see" timestamped screen frames as images — no raw video needed. Frame-viewing works in any image-capable agent (ChatGPT, Claude Code, Cursor, Codex); text-only web chats still get the full transcript and can take a frame you upload.
 
 <Diagram id="doc-block-pqnd4p" title="Capture, transcribe, reuse" summary={"Three capture types land in one library; the agent transcribes, titles, and summarizes, then every transcript is searchable and shareable."}>
 
@@ -85,7 +85,7 @@ Think along the lines of Loom + Granola + Wispr Flow rolled into one app — but
 - **Get an auto-generated title, summary, and chapter markers** for every recording — the agent fills them in and keeps them current.
 - **Search across every transcript** — screen recordings, meetings, and dictations all in one library. "Find the clip where we discussed the rollout plan."
 - **Share clips** with per-clip permissions (public, team, private). Link tracking and threaded comments work too.
-- **Preview public clips in Slack** with a Loom-style playable unfurl after the
+- **Preview public clips in Slack** with a playable video unfurl after the
   workspace installs your Clips Slack app.
 - **Capture browser logs with the Chrome extension.** Browser recordings can
   attach redacted console logs and fetch/XHR metadata, which is helpful for
@@ -574,7 +574,7 @@ Routes in the UI live under `templates/clips/app/routes/` — the authenticated
 
 ### Key actions
 
-Every agent-callable operation is a TypeScript file in `templates/clips/actions/`, auto-mounted at `POST /_agent-native/actions/:name` and runnable from the CLI as `pnpm action <name>`. There are ~80 actions; the useful groupings:
+Every agent-callable operation is a TypeScript file in `templates/clips/actions/`, auto-mounted at `POST /_agent-native/actions/:name` and runnable from the CLI as `pnpm action <name>`. There are about 100 actions; the useful groupings:
 
 - **Recording lifecycle** — `create-recording`, `finalize-recording`, `update-recording`, `set-thumbnail`, `archive-recording` / `restore-recording` / `trash-recording` / `delete-recording-permanent`, `move-recording`, `tag-recording`.
 - **Bug reports** — `save-bug-report-context` stores redacted host-product context for recordings launched from `/bug-report`; `get-recording-player-data` returns the sidecar to editors.

package/corpus/core/docs/content/template-content.mdx

@@ -1,15 +1,15 @@
 ---
 title: "Content"
-description: "Open-source Obsidian for MDX: edit local Markdown/MDX files, generate rich interactive custom blocks, and write with an AI agent."
+description: "A local-file-friendly document workspace: edit Markdown/MDX files, generate rich interactive custom blocks, and write together with an AI agent."
 ---
 
 # Content
 
-Content is open-source Obsidian for MDX: a local-file-friendly document
-workspace where the agent can read, write, reorganize, and publish pages for
-you. Open a doc, ask "rewrite this paragraph to be more concise" or "create a
-page called Q4 Planning with sub-pages for Goals, Metrics, and Risks" - same
-result whether you do it yourself or ask.
+Content is a local-file-friendly document workspace where the agent can read,
+write, reorganize, and publish pages for you. Open a doc, ask "rewrite this
+paragraph to be more concise" or "create a page called Q4 Planning with
+sub-pages for Goals, Metrics, and Risks" - same result whether you do it
+yourself or ask.
 
 <WireframeBlock id="doc-block-1i1ubpx">
   <Screen
@@ -90,7 +90,7 @@ When you open the app, you'll see a page tree next to the editor. The agent alwa
 - **Write rich text** with headings, lists, tables, code blocks, images, and links. Slash commands (`/`) insert blocks; selecting text pops up a formatting toolbar.
 - **Organize pages in a tree** — nest infinitely, drag to reorder, favorite pages you use often.
 - **Search across everything** with full-text search across titles and content.
-- **Edit local Markdown/MDX files like Obsidian.** Use the `/local-files` view
+- **Edit local Markdown/MDX files with your own tools.** Use the `/local-files` view
   to export your workspace to files, edit them in your own tools, preview
   changes, and import them back. In Local File Mode, Content writes straight to
   the selected `.md` or `.mdx` file.
@@ -119,11 +119,10 @@ Select text and hit Cmd+I to focus the agent with that selection pre-loaded —
 ## Local Markdown/MDX files {#local-files}
 
 Content can round-trip documents through local files without cloning or running
-the Content app locally. It feels like Obsidian for MDX: files stay inspectable
-and editable, while the app gives you a rich editor, agent actions, sharing, and
-custom blocks. Open `/local-files`, choose a folder in your browser or Agent
-Native Desktop, and export the current document tree as Markdown/MDX under
-`content/`.
+the Content app locally. Files stay inspectable and editable on disk, while the
+app gives you a rich editor, agent actions, sharing, and custom blocks. Open
+`/local-files`, choose a folder in your browser or Agent Native Desktop, and
+export the current document tree as Markdown/MDX under `content/`.
 
 Each exported file contains frontmatter for document metadata (`id`, `title`,
 `parentId`, `position`, favorite/search/visibility flags, and `updatedAt`) plus
@@ -142,9 +141,8 @@ truth instead of SQL documents. Add `agent-native.json` to a repo, set
 `content/`, and `resources/`. The standard Content editor then populates its
 left sidebar from those local `.md`/`.mdx` files and writes edits back to the
 selected file through the normal document actions. Use this for repo-first docs,
-blogs, resource libraries, or Obsidian-style personal content with MDX-powered
-components; switch back to database mode when you want hosted collaboration and
-SQL-backed sharing. See [Local File Mode](/docs/local-file-mode) for the
+blogs, resource libraries, or a personal MDX-powered notes vault; switch back to
+database mode when you want hosted collaboration and SQL-backed sharing. See [Local File Mode](/docs/local-file-mode) for the
 standalone repo layout, configuration, custom MDX components, local
 `extensions/` widgets, and production safety guide.
 
@@ -220,13 +218,12 @@ Local file workspaces can also provide repo-local React components through the
 configured `components` folder. The Content dev server imports PascalCase
 exports from those files, renders matching MDX tags such as `<ImpactCounter />`
 inside the editor, and exposes them in the slash menu under Local components.
-This is the "Obsidian for MDX" layer: custom MDX blocks stay local to the
+This is the local-first custom-block layer: custom MDX blocks stay local to the
 workspace, but the editor can render them and the agent can generate or update
 their source without cloning the Content app. A minimal workspace component can
 be:
 
-```tsx
-// components/ImpactCounter.tsx
+```tsx filename="components/ImpactCounter.tsx"
 import { useState } from "react";
 
 export function ImpactCounter({
@@ -671,3 +668,11 @@ The four places to look when changing behavior:
 - **`shared/notion-markdown.ts`** — markdown-to-Notion-blocks conversion. Extend this if you add new block types that need to round-trip through Notion.
 
 The agent can make all of these changes itself — ask it to "add a tags column to documents and expose it in the sidebar" and it will update the schema, migrate, wire the UI, and write the action.
+
+## What's next
+
+- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
+- [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync
+- [**Local File Mode**](/docs/local-file-mode) — the standalone repo layout, config, and production safety guide
+- [**Real-Time Collaboration**](/docs/real-time-collaboration) — the Yjs pipeline documents share with other collaborative surfaces
+- [**Sharing**](/docs/sharing) — the share-grant model documents build on

package/corpus/core/docs/content/template-design.mdx

@@ -11,7 +11,7 @@ Design is an agent-native HTML prototyping studio. Instead of a layered drawing
   <Screen
     surface="desktop"
     html={
-      "<div style='display:flex;flex-direction:column;gap:14px;padding:18px;min-height:520px;box-sizing:border-box'><div style='display:flex;align-items:center;gap:10px'><h1 style='margin:0'>Product launch page</h1><span class='wf-pill accent'>Desktop</span><span class='wf-pill'>Tablet</span><span class='wf-pill'>Mobile</span><div style='flex:1'></div><button>Preview</button><button class='primary'>Export code</button></div><div class='wf-card' style='flex:1;display:grid;grid-template-rows:auto 1fr auto;gap:12px'><div style='display:flex;gap:8px'><span class='wf-pill accent'>Hero</span><span class='wf-pill'>Pricing</span><span class='wf-pill'>FAQ</span></div><div class='wf-box' style='display:flex;align-items:center;justify-content:center;min-height:230px'><strong>Generated HTML prototype</strong></div><div class='wf-card' style='display:flex;align-items:center;gap:10px'><span class='wf-muted'>Make the hero denser and the CTA clearer.</span><div style='flex:1'></div><button class='primary'>Apply revision</button></div></div></div>"
+      "<div style='display:flex;flex-direction:column;gap:14px;padding:18px;min-height:520px;box-sizing:border-box'><div style='display:flex;align-items:center;gap:10px'><h1 style='margin:0'>Product launch page</h1><span class='wf-pill accent'>Desktop</span><span class='wf-pill'>Tablet</span><span class='wf-pill'>Mobile</span><div style='flex:1'></div><button>Preview</button><button class='primary'>Export code</button></div><div class='wf-card' style='flex:1;display:grid;grid-template-rows:auto 1fr auto;gap:12px'><div style='display:flex;gap:8px'><span class='wf-pill accent'>Hero</span><span class='wf-pill'>Pricing</span><span class='wf-pill'>FAQ</span></div><div class='wf-box' style='display:flex;flex-direction:column;gap:12px;min-height:230px;padding:20px'><div style='display:flex;flex-direction:column;align-items:center;gap:8px;text-align:center'><strong style='font-size:22px'>Launch faster with Agent-Native</strong><span class='wf-muted' style='max-width:70%'>Generate a working prototype from a prompt, then refine it in place.</span><button class='primary'>Get started</button></div><div style='display:grid;grid-template-columns:repeat(3,1fr);gap:10px;flex:1'><div class='wf-card' style='min-height:56px'></div><div class='wf-card' style='min-height:56px'></div><div class='wf-card' style='min-height:56px'></div></div></div><div class='wf-card' style='display:flex;align-items:center;gap:10px'><span class='wf-muted'>Make the hero denser and the CTA clearer.</span><div style='flex:1'></div><button class='primary'>Apply revision</button></div></div></div>"
     }
   />
 </WireframeBlock>
@@ -134,6 +134,8 @@ pnpm dev
 
 All data lives in SQL via Drizzle ORM. Schema: `templates/design/server/db/schema.ts`. Designs and design systems carry the standard `ownableColumns` and a matching framework shares table, so they slot into the per-user / per-org sharing model.
 
+The table below covers the core ownable resources — designs, files, templates, versions, and design systems. Seven more tables in the same schema back features described elsewhere in this doc rather than the core resource model: `design_localhost_connections` and `design_localhost_write_grants` (localhost source mode), `component_index` (component indexing), `motion_timeline` (motion), `design_state` (editor state snapshots), `design_fusion_edits` (full-app fusion mode), and `design_review_snapshot` (review snapshots).
+
 | Table                                    | What it holds                                                                                                                                    |
 | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `designs`                                | A design project — `title`, `description`, `project_type` (`prototype` / `other`), the `data` JSON blob, and an optional `design_system_id` link |

package/corpus/core/docs/content/template-dispatch.mdx

@@ -5,7 +5,11 @@ description: "Dispatch is the workspace control plane — central inbox, cross-a
 
 # Dispatch
 
-> **See also:** for the conceptual overview of what Dispatch does and when you want it, see [Dispatch](/docs/dispatch). This page is the template-specific reference.
+<Callout tone="info">
+
+**See also:** for the conceptual overview of what Dispatch does and when you want it, see [Dispatch](/docs/dispatch). This page is the template-specific reference.
+
+</Callout>
 
 Dispatch is the **workspace control plane**. Where other templates are domain apps (Mail, Calendar, Analytics, Brain), Dispatch is the app you run _alongside_ them to coordinate everything: a central inbox, a secrets vault, scheduled jobs, Slack/Telegram integration, and an orchestrator agent that delegates domain work to the right specialist app over [A2A](/docs/a2a-protocol).
 

package/corpus/core/docs/content/template-mail.mdx

@@ -5,7 +5,7 @@ description: "An agent-powered email client. Connect your Gmail and the agent ca
 
 # Mail
 
-An agent-powered email client. Connect your Gmail account and the agent can read, draft, send, and organize email for you — alongside a fast, keyboard-first inbox you can drive yourself. Think Superhuman, but the agent is a first-class citizen and the codebase is yours to own.
+An agent-powered email client. Connect your Gmail account and the agent can read, draft, send, and organize email for you — alongside a fast, keyboard-first inbox you can drive yourself, with the agent as a first-class citizen and the codebase yours to own.
 
 <WireframeBlock id="doc-block-ofadgy">
   <Screen
@@ -96,7 +96,11 @@ When you open the app, the keyboard-first inbox and thread view stay focused on
 
 Live demo: [mail.agent-native.com](https://mail.agent-native.com).
 
-> **Google may show a warning:** The hosted demo uses Agent-Native's shared Google app for Gmail access, so Google may ask you to confirm before continuing. Run locally to use your own Google OAuth client.
+<Callout tone="info">
+
+**Google may show a warning:** The hosted demo uses Agent-Native's shared Google app for Gmail access, so Google may ask you to confirm before continuing. Run locally to use your own Google OAuth client.
+
+</Callout>
 
 When you first open the app:
 
@@ -362,3 +366,11 @@ Mail is yours to change. Everything important lives in a handful of places — s
 **Changing keyboard shortcuts.** Keybind handlers live in `templates/mail/app/components/email/` — search for `useHotkeys` or `addEventListener("keydown"` to find where each key is wired.
 
 Ask the agent to make any of these changes for you. The agent can edit its own source — see [Self-Modifying Code](/docs/key-concepts#agent-modifies-code).
+
+## What's next
+
+- [**Templates**](/docs/cloneable-saas) — the clone-and-own model, and every other domain template to start from
+- [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync
+- [**Calendar**](/docs/template-calendar) — a sibling domain template covering scheduling and booking
+- [**Automations**](/docs/automations) — the event-triggered engine mail's auto-triage rules build on
+- [**Actions**](/docs/actions) — the action system chat, shortcuts, and automations all call