@agent-native/core 0.7.12 → 0.7.14

package/docs/content/template-calendar.md

@@ -1,26 +1,61 @@
 ---
-title: "Calendar Template"
-description: "AI-native calendar with Google Calendar sync and a Calendly-style public booking page."
+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."
 ---
 
-# Calendar Template
+# Calendar
 
-The Calendar template is a complete scheduling app: a full calendar UI on top of Google Calendar, plus Calendly-style public booking links, all driven by an agent that can schedule, search, and manage availability on your behalf. It replaces the Google Calendar + Calendly combo with something you own and can extend.
+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.
 
-## Overview {#overview}
+When you open the app, you'll see your calendar in the middle and the agent in the sidebar. The agent always knows which day, week, or event you're looking at, so you can say "schedule a 30-minute call with Alex on this day" without spelling everything out.
 
-Calendar is for anyone who currently juggles Google Calendar for their own schedule and Calendly (or similar) for letting other people book time. It gives you:
+## What you can do with it
 
-- Day, week, and month calendar views backed by the Google Calendar API.
-- Multi-account Google OAuth, so several calendars can overlay in one view.
-- External ICS calendar subscriptions (webcal feeds).
-- Configurable weekly availability with timezone support.
-- Public booking links at `/book/{slug}` or `/meet/{username}/{slug}` with custom durations, custom fields, and meeting-link options.
-- An agent that can answer schedule questions, create events, find free slots, and manage booking links through natural language.
+- **See your real Google Calendar** in day, week, or month view, with multiple accounts overlayed.
+- **Subscribe to ICS feeds** (HR time off, conference schedules, team calendars) — read-only, mixed into the same view.
+- **Set weekly availability** with timezone support — the agent uses this when finding free slots.
+- **Create public booking links** at `/book/{slug}` for things like "15-minute intro" or "30-minute demo." Configure durations, custom fields, and which conferencing tool to use.
+- **Ask the agent anything schedule-related**: "Am I free Thursday afternoon?" "Find a 1-hour slot next week and put 'Planning with Alex' on it." "Pause my demo booking link."
+- **Share booking links** with teammates so they can manage them too.
 
-Events themselves are not copied into the local database. The app reads them from Google Calendar on every request. Bookings, booking links, and settings live in SQL.
+## Getting started
 
-## Quick start {#quick-start}
+Live demo: [calendar.agent-native.com](https://calendar.agent-native.com).
+
+When you first open the app:
+
+1. Click **Settings**.
+2. Click **Connect Google Calendar** and approve.
+3. (Optional) Connect more Google accounts if you want personal + work overlayed.
+4. Open the main view — your real calendar will load.
+
+To create your first booking link:
+
+1. Click **Booking Links** in the sidebar.
+2. Click **New booking link**, set a title and duration.
+3. Share the public URL — visitors pick from your available slots.
+
+Or just ask the agent: "Create a 15-minute intro booking link with a name field."
+
+### Useful prompts
+
+- "What is on my calendar today?"
+- "Am I free Thursday afternoon for 30 minutes?"
+- "Find a 1-hour slot next week and put 'Planning with Alex' on it."
+- "Reschedule this event to Friday at 2pm." (when an event is selected)
+- "Switch to day view and jump to next Monday."
+- "Create a booking link called '15 min intro' at 15 minutes with a note field."
+- "Pause my '30 min demo' booking link."
+- "Block Friday afternoons on my availability."
+- "What meetings do I have about 'launch' this month?"
+
+The agent will query Google Calendar live for any schedule question — it never guesses.
+
+## For developers
+
+The rest of this doc is for anyone forking the Calendar template or extending it.
+
+### Quick start
 
 Create a new workspace with the Calendar template:
 
@@ -33,29 +68,17 @@ pnpm dev
 
 Open `http://localhost:8082` (the default Calendar dev port).
 
-Live demo: [https://calendar.agent-native.com](https://calendar.agent-native.com).
+To connect Google Calendar in dev, open the Settings view, paste a `GOOGLE_CLIENT_ID` and `GOOGLE_CLIENT_SECRET` from [Google Cloud Console](https://console.cloud.google.com/), and click "Connect Google Calendar". The OAuth redirect URI is `http://localhost:8082/_agent-native/google/callback` in dev. Tokens are stored in the `oauth_tokens` SQL table and refresh automatically.
 
-To connect Google Calendar, open the Settings view, paste a `GOOGLE_CLIENT_ID` and `GOOGLE_CLIENT_SECRET` from [Google Cloud Console](https://console.cloud.google.com/), and click "Connect Google Calendar". The OAuth redirect URI is `http://localhost:8082/_agent-native/google/callback` in dev. Tokens are stored in the `oauth_tokens` SQL table and refresh automatically.
+### Key features (technical)
 
-## Key features {#key-features}
+**Calendar views.** The main view at `/` (route `app/routes/_app._index.tsx`) renders the calendar in day, week, or month mode. Switch views from the toolbar, or ask the agent to switch for you. Events are fetched live from Google Calendar — no local sync step is required to see the latest state.
 
-### Calendar views
+**Multi-account Google Calendar sync.** Connect as many Google accounts as you like. Each connection appears in Settings, and events from every connected calendar overlay in the main view. Sync is pull-based, so no webhooks or background workers are required. The `sync-google-calendar` action refetches a date range on demand. Supporting actions: `list-events`, `search-events`, `get-event`, `create-event`, `sync-google-calendar`.
 
-The main view at `/` (route `app/routes/_app._index.tsx`) renders the calendar in day, week, or month mode. Switch views from the toolbar, or ask the agent to switch for you. Events are fetched live from Google Calendar — no local sync step is required to see the latest state.
+**External calendars (ICS subscriptions).** Subscribe to read-only ICS or `webcal://` feeds — useful for HR time off, conference schedules, or shared team calendars. Feeds are added in Settings and stored per user. Relevant actions: `add-external-calendar`, `list-external-calendars`, `remove-external-calendar`, `update-external-calendars`.
 
-### Multi-account Google Calendar sync
-
-Connect as many Google accounts as you like. Each connection appears in Settings, and events from every connected calendar overlay in the main view. Sync is pull-based, so no webhooks or background workers are required. The `sync-google-calendar` action refetches a date range on demand.
-
-Supporting actions: `list-events`, `search-events`, `get-event`, `create-event`, `sync-google-calendar`.
-
-### External calendars (ICS subscriptions)
-
-Subscribe to read-only ICS or `webcal://` feeds — useful for HR time off, conference schedules, or shared team calendars. Feeds are added in Settings and stored per user. Relevant actions: `add-external-calendar`, `list-external-calendars`, `remove-external-calendar`, `update-external-calendars`.
-
-### Availability rules
-
-Availability is a weekly schedule of time windows per day, plus a timezone. It is stored in the settings table under the key `calendar-availability`:
+**Availability rules.** Availability is a weekly schedule of time windows per day, plus a timezone. It is stored in the settings table under the key `calendar-availability`:
 
 ```json
 {
@@ -77,9 +100,7 @@ Availability is a weekly schedule of time windows per day, plus a timezone. It i
 
 Edit it at `/availability` (`app/routes/_app.availability.tsx`) or via the `update-availability` action. The `check-availability` action reads this schedule, subtracts your existing Google Calendar events, and returns free slots of the requested duration.
 
-### Public booking pages
-
-Booking links are the Calendly replacement. Create one in the UI at `/booking-links` (`app/routes/_app.booking-links._index.tsx`), configure it in the editor at `/booking-links/{id}`, and share the public URL.
+**Public booking pages.** Booking links are the Calendly replacement. Create one in the UI at `/booking-links` (`app/routes/_app.booking-links._index.tsx`), configure it in the editor at `/booking-links/{id}`, and share the public URL.
 
 Every link has:
 
@@ -93,9 +114,7 @@ Visitors land on the public page, pick a date and time from the available slots,
 
 There is also a per-user public URL at `/meet/{username}/{slug}` for clean personal sharing.
 
-### Sharing booking links with teammates
-
-Booking links are private by default — only the creator can edit or delete them. To let a teammate manage a link, either change the link's visibility or grant explicit access. The framework ships these actions, auto-mounted for any `booking-link` resource:
+**Sharing booking links with teammates.** Booking links are private by default — only the creator can edit or delete them. To let a teammate manage a link, either change the link's visibility or grant explicit access. The framework ships these actions, auto-mounted for any `booking-link` resource:
 
 - `share-resource` — grant a user or org `viewer`, `editor`, or `admin` access.
 - `unshare-resource` — revoke a grant.
@@ -104,29 +123,15 @@ Booking links are private by default — only the creator can edit or delete the
 
 Sharing only controls who can manage the link. The public booking URL always accepts bookings from unauthenticated visitors as long as `isActive` is true.
 
-### Inline event previews in chat
+**Inline event previews in chat.** The `/event` route (`app/routes/event.tsx`) renders a compact, chromeless event card that the agent can embed in chat when you ask about a specific event. Title, time, location, attendees, and a description snippet are shown with a button to jump into the main calendar.
 
-The `/event` route (`app/routes/event.tsx`) renders a compact, chromeless event card that the agent can embed in chat when you ask about a specific event. Title, time, location, attendees, and a description snippet are shown with a button to jump into the main calendar.
-
-## Working with the agent {#working-with-the-agent}
+### Working with the agent
 
 The agent sees what you are looking at. The current calendar view, the selected date, and the selected event are included in every message as a `current-screen` block, so you can say "this event" or "this day" and it resolves correctly.
 
-Example prompts:
-
-- "What is on my calendar today?"
-- "Am I free Thursday afternoon for 30 minutes?"
-- "Find a 1-hour slot next week and put 'Planning with Alex' on it."
-- "Reschedule this event to Friday at 2pm." (when an event is selected)
-- "Switch to day view and jump to next Monday."
-- "Create a booking link called '15 min intro' at 15 minutes with a note field."
-- "Pause my '30 min demo' booking link."
-- "Block Friday afternoons on my availability."
-- "What meetings do I have about 'launch' this month?"
-
 Under the hood the agent calls actions like `list-events`, `check-availability`, `create-event`, `navigate`, and `update-availability`. Because events live in Google Calendar, the agent always queries the API instead of guessing — it will not return empty results without running a script first.
 
-## Data model {#data-model}
+### Data model
 
 Defined in `templates/calendar/server/db/schema.ts`. Only non-event data is stored locally:
 
@@ -137,7 +142,7 @@ Defined in `templates/calendar/server/db/schema.ts`. Only non-event data is stor
 
 Availability rules and per-user configuration live in the settings table, keyed by `calendar-availability`. Google OAuth tokens live in the framework `oauth_tokens` table. Ephemeral UI state (current view, date, selected event) lives in `application_state` under the `navigation` key.
 
-## Customizing it {#customizing-it}
+### Customizing it
 
 Every part of the app is editable source. Start here:
 

package/docs/content/template-clips.md

@@ -1,36 +1,40 @@
 ---
-title: "Clips Template"
-description: "Agent-native screen recording with AI transcription, auto-titles, summaries, chapter markers, and full-text search across every clip."
+title: "Clips"
+description: "Record your screen, get an AI-generated title, summary, and chapter markers automatically, and search across every recording you've ever made."
 ---
 
 # Clips
 
-Clips is an agent-native screen-recording app. The user records a video, the app transcribes it, and the agent takes over: suggests titles, writes summaries, builds chapters, finds the exact moment someone said X, opens the right recording, shares it with the right teammate, drafts replies to comments.
+A screen-recording app where the agent does the post-production work for you. Record your screen, and Clips transcribes it, suggests a title and summary, builds chapter markers, and tags the content automatically. Ask "find the clip where we discussed the rollout plan" and the agent searches across every transcript you've ever made.
 
-Think Loom, but the agent is a first-class editor — and the recordings are yours, not a SaaS vendor's.
+Think along the lines of products that record short async videos for your team — but the agent is a first-class editor, and the recordings are yours, not a SaaS vendor's.
 
-## What it does {#what-it-does}
+## What you can do with it
 
-- **Record your screen.** Built-in recorder with webcam overlay, audio capture, and pause/trim.
-- **Auto-transcribe.** Every recording is transcribed on upload. Speaker turns, timestamps, searchable.
-- **Agent-generated metadata.** Titles, summaries, chapter markers, tags — the agent fills them in and keeps them current.
-- **Full-text search.** Query across every transcript in your library. "Find the clip where we discussed the rollout plan."
-- **Share links.** Per-clip permissions (public, team, private), link tracking, comments threaded with the agent in the loop.
-- **Smart library.** Group by project, filter by speaker, auto-tag based on content.
+- **Record your screen** with a built-in recorder, webcam overlay, audio capture, and pause/trim.
+- **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** with full-text search. "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.
+- **Smart library views.** Group by project, filter by speaker, auto-tag based on content.
+- **Edit the transcript through chat.** "Fix the mis-transcribed word at 1:42." "Pull three quotes for a blog post." The agent edits the transcript and the UI updates live.
 
-## Why it's interesting {#why}
+## Why it's interesting
 
-Three things make the Clips template a good showcase of what agent-native enables:
+Three things make Clips a good showcase of what agent-native enables:
 
 1. **The agent edits the transcript.** Fix a mis-transcribed word, generate chapter timestamps, pull quotes for a blog post — all in natural language, in the chat, with the UI updating live via polling.
 2. **Context awareness on recordings.** When you're viewing a clip, the agent knows the clip id, the current playhead, and the selected transcript range. Ask "summarize from here to the end" and it understands what "here" means.
-3. **Clips you own, not a vendor.** Unlike Loom, the recordings live in your storage, the transcripts live in your SQL, and the agent is yours. Fork the template, change how chapters get built, wire it to your own CDN — it's your code.
+3. **Clips you own, not a vendor.** The recordings live in your storage, the transcripts live in your SQL, and the agent is yours. Fork the template, change how chapters get built, wire it to your own CDN — it's your code.
 
-## Naming note {#naming-note}
+## For developers
 
-In the template, always say **"Clip"** in user-facing strings and agent messages — never "Loom." Internal table / variable names (`recordings`, `recording_transcripts`, etc.) stay as-is.
+The rest of this doc is for anyone forking the Clips template or extending it.
 
-## Scaffolding {#scaffolding}
+### Naming note
+
+In the template, always say **"Clip"** in user-facing strings and agent messages. Internal table / variable names (`recordings`, `recording_transcripts`, etc.) stay as-is.
+
+### Scaffolding
 
 ```bash
 pnpm dlx @agent-native/core create my-clips --template clips --standalone
@@ -38,7 +42,7 @@ pnpm dlx @agent-native/core create my-clips --template clips --standalone
 
 Clips is a larger template with a native recorder (it ships a desktop companion for local capture). See the template `README.md` for setup specifics around screen-capture permissions and storage configuration.
 
-## Customize it {#customize}
+### Customize it
 
 Ask the agent:
 

package/docs/content/template-content.md

@@ -1,19 +1,43 @@
 ---
-title: "Content Template"
-description: "A Notion-style document editor with an AI agent that can read, write, organize, and publish your pages."
+title: "Content"
+description: "A Notion-style document editor with an AI agent that can read, write, reorganize, and publish your pages — all in plain English."
 ---
 
-# Content Template
+# Content
 
-A hierarchical document editor in the style of Notion or Google Docs. The AI agent has full parity with the UI — it can create pages, edit selections, reorganize the tree, and sync with Notion, all while seeing exactly what you see.
+A Notion-style 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.
 
-## Overview {#overview}
+When you open the app, you'll see a sidebar tree of pages on the left, the editor in the middle, and the agent in the sidebar on the right. The agent always knows which page you're viewing and what text you have selected.
 
-The Content template is a rich-text document workspace with a sidebar tree, a Tiptap-based editor, and an agent panel. Pages live in a nested tree, content is stored as markdown in SQL, and the agent uses the same actions the UI calls for every operation.
+## What you can do with it
 
-Everything lives in one database (SQLite, Postgres, Turso — anything Drizzle supports) and the agent sees your current view, so you can say "rewrite this paragraph" or "add a sub-page for Q4 planning" and it knows what you mean without you pasting anything.
+- **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.
+- **Sync with Notion.** Link a local doc to a Notion page and pull or push content in either direction. Comments sync both ways too.
+- **Collaborate in real time.** Multiple people (and the agent) can edit the same doc at the same time.
+- **Share docs** with teammates or make them public — private by default, with viewer / editor / admin roles.
+- **Ask the agent for anything**: "Rewrite this paragraph." "Add a TL;DR at the top." "Find all my meeting notes from last week." "Make this tone more formal."
 
-## Quick start {#quick-start}
+## Getting started
+
+Live demo: [content.agent-native.com](https://content.agent-native.com).
+
+When you open the app, click **+ New page** in the sidebar, give it a title, and start writing. To use the agent, type in the sidebar:
+
+- "Create a page called Onboarding and add three sub-pages under it."
+- "Rewrite this paragraph to be more concise." (with a page open)
+- "Add a section about pricing with three bullet points."
+- "Summarize this doc into a TL;DR at the top."
+- "Pull the latest from Notion." (after linking a Notion page)
+
+Select text and hit Cmd+I to focus the agent with that selection pre-loaded — "make this punchier" then operates on exactly what you highlighted.
+
+## For developers
+
+The rest of this doc is for anyone forking the Content template or extending it.
+
+### Quick start
 
 Scaffold a new workspace with the Content template:
 
@@ -26,9 +50,7 @@ pnpm dev
 
 Open `http://localhost:8080` and create your first page. The agent panel is on the right — try asking it to "create a page called Onboarding and add three sub-pages under it".
 
-Live demo: https://content.agent-native.com
-
-## Key features {#key-features}
+### Key features (technical) {#key-features}
 
 ### Hierarchical pages
 
@@ -92,27 +114,15 @@ See the `sharing` skill.
 
 A dedicated team page at `/team` (see `app/routes/_app.team.tsx`) uses the framework's `TeamPage` component for creating orgs and managing members.
 
-## Working with the agent {#working-with-the-agent}
+### Working with the agent
 
 Because the agent sees your current screen, most prompts don't need you to reference a document explicitly. When you have a page open, "this" means that page.
 
-Example prompts:
-
-- "Rewrite this paragraph to be more concise."
-- "Add a section about pricing with three bullet points."
-- "Create a page called Q4 Planning with sub-pages for Goals, Metrics, and Risks."
-- "Summarize this doc into a TL;DR at the top."
-- "Find all my meeting notes from last week."
-- "Change the tone of this page to be more formal."
-- "Pull the latest from Notion."
-- "Share this doc with hbikna@gmail.com as an editor."
-- "Move this page under Onboarding."
-
 For small edits, the agent uses `edit-document --find ... --replace ...` so only the changed text flows through Yjs — you'll see the diff applied in place rather than the whole page re-render. For bigger rewrites it uses `update-document --content ...`.
 
 If you select text and press Cmd+I (or focus the agent panel), the selection travels with your next message as context, so "make this punchier" operates on exactly what you highlighted.
 
-## Data model {#data-model}
+### Data model
 
 Four core tables, all defined in `server/db/schema.ts`:
 
@@ -126,7 +136,7 @@ Content is stored as markdown. The editor converts to and from the Tiptap JSON m
 
 All ownable tables include `owner_email` and `org_id` via `ownableColumns()`, so a local-mode workspace (`local@localhost`) can be upgraded to a real account without losing history.
 
-## Customizing it {#customizing-it}
+### Customizing it
 
 The four places to look when changing behavior:
 

package/docs/content/template-dispatch.md

@@ -7,11 +7,11 @@ description: "Dispatch is the workspace control plane — central inbox, cross-a
 
 Dispatch is the **workspace control plane**. Where other templates are domain apps (Mail, Calendar, Analytics), 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).
 
-If you're running an [enterprise workspace](/docs/enterprise-workspace) with many apps, Dispatch is the glue.
+If you're running an [multi-app workspace](/docs/multi-app-workspace) with many apps, Dispatch is the glue.
 
 ## What it does {#what-it-does}
 
-- **Central inbox.** Slack DMs, Telegram messages, email notifications, A2A requests from other agents — all land in one place. The Dispatch agent triages and either handles them itself or delegates.
+- **Central inbox.** Slack DMs, Telegram messages, email notifications, A2A requests from other agents — all land in one place. The Dispatch agent triages and either handles them itself or delegates. See [Messaging](/docs/messaging) for how to wire Slack, email, and Telegram into your workspace.
 - **Orchestrator, not specialist.** Dispatch does _not_ try to be the email app or the analytics app. When someone asks "summarize last week's signups," Dispatch calls the analytics agent over A2A and returns the answer. When someone asks "draft a reply to Alice," Dispatch calls the mail agent.
 - **Secrets vault.** A central store for API keys, OAuth tokens, and shared credentials. Apps in the workspace resolve secrets from Dispatch instead of duplicating them in every `.env`. Requests + approvals for sensitive access.
 - **Integrations catalog.** One page showing every third-party integration — Slack, Telegram, SendGrid, Apollo, etc. — with a "configured / not configured / pending approval" status per app.
@@ -44,7 +44,7 @@ pnpm dlx @agent-native/core create my-platform
 # pick "Dispatch" in the multi-select picker, plus whichever domain apps you want
 ```
 
-Dispatch is usually scaffolded into a workspace alongside the apps it coordinates. For a workspace, Dispatch's shared auth, database, and brand are inherited from the workspace core — see [Enterprise Workspace](/docs/enterprise-workspace).
+Dispatch is usually scaffolded into a workspace alongside the apps it coordinates. For a workspace, Dispatch's shared auth, database, and brand are inherited from the workspace core — see [Multi-App Workspace](/docs/multi-app-workspace).
 
 ## Customize it {#customize}
 
@@ -52,7 +52,8 @@ Dispatch is a full cloneable SaaS like any other template — see [Cloneable Saa
 
 ## What's next
 
-- [**Enterprise Workspace**](/docs/enterprise-workspace) — running Dispatch alongside multiple apps
+- [**Messaging**](/docs/messaging) — connecting Slack, email, and Telegram so you can talk to your agent from anywhere
+- [**Multi-App Workspace**](/docs/multi-app-workspace) — running Dispatch alongside multiple apps
 - [**A2A Protocol**](/docs/a2a-protocol) — how Dispatch delegates to specialist agents
 - [**MCP Clients — Hub Mode**](/docs/mcp-clients#hub) — sharing MCP servers across the workspace
 - [**Recurring Jobs**](/docs/recurring-jobs) — scheduled tasks Dispatch runs

package/docs/content/template-forms.md

@@ -5,24 +5,26 @@ description: "Agent-native form builder — create, edit, and analyze forms thro
 
 # Forms
 
-Forms is an agent-native form builder with a simple premise: everything the GUI can do, the agent can do, and vice versa. You can drag fields around in the editor, or you can type "add a 'how did you hear about us' dropdown with five options and make it required" — same result, same underlying data.
+A form builder where the form builder _is_ the agent. Drag fields around in the editor, or just say "add a 'how did you hear about us' dropdown with five options and make it required" — same result, same underlying data. Think Typeform, but you can build, edit, and analyze forms by talking to the agent.
 
-Think Typeform, but the form builder _is_ the agent.
+When you open the app, you'll see a list of your forms on the left and the editor in the middle. Open a form and you can click any field to fine-tune it, or ask the agent to make changes for you.
 
-## What it does {#what-it-does}
+## What you can do with it
 
-- **Build forms conversationally.** "Create a contact form," "add a NPS score question," "make the email field required." The agent updates the schema; the preview updates live.
+- **Build forms conversationally.** "Create a contact form," "add an NPS score question," "make the email field required." The agent updates the schema and the preview updates live.
 - **Click-to-edit fine-tuning.** Every field in the preview is editable in place — label, placeholder, validation, conditional logic — with the usual GUI controls.
-- **Field types** out of the box: short text, long text, email, phone, URL, number, date, single-select, multi-select, rating, file upload, section header, conditional branch.
-- **Responses dashboard.** Per-response view + an aggregate dashboard the agent can pivot on request: "show me signups from the last 30 days grouped by source."
+- **Field types out of the box:** short text, long text, email, phone, URL, number, date, single-select, multi-select, rating, file upload, section header, conditional branch.
+- **Responses dashboard.** Per-response view plus an aggregate dashboard the agent can pivot on request: "show me signups from the last 30 days grouped by source."
 - **Agent-driven analysis.** Ask the agent to cluster free-text responses, extract sentiments, or draft a reply to everyone who scored the NPS below 7.
-- **Publishing.** Public share link with embed snippet, branded thank-you page, webhook on submit.
+- **Publish anywhere.** Public share link, embed snippet, branded thank-you page, webhook on submit.
 
-## Why it's interesting {#why}
+## Why it's interesting
 
-Forms is a clear example of the [ladder](/docs/what-is-agent-native#the-ladder) rung 3 payoff. The hard part of a form builder isn't the editor UI — it's everything around it: schema evolution, response analytics, conditional logic, publishing, notifications, integrations. Most of that is just prompting the agent, because every capability is an action the agent can call.
+Forms is a clear example of the [ladder](/docs/what-is-agent-native#the-ladder) rung-3 payoff. The hard part of a form builder isn't the editor UI — it's everything around it: schema evolution, response analytics, conditional logic, publishing, notifications, integrations. Most of that is just prompting the agent, because every capability is an action the agent can call.
 
-## Scaffolding {#scaffolding}
+## For developers
+
+### Scaffolding
 
 ```bash
 pnpm dlx @agent-native/core create my-forms --template forms --standalone
@@ -34,7 +36,7 @@ For a workspace with forms alongside other apps:
 pnpm dlx @agent-native/core create my-platform  # pick Forms + other templates
 ```
 
-## Customize it {#customize}
+### Customize it
 
 Ask the agent:
 

package/docs/content/template-slides.md

@@ -1,25 +1,51 @@
 ---
-title: "Slides Template"
-description: "Agent-native presentation editor — generate decks from a prompt, edit visually, and present in full-screen."
+title: "Slides"
+description: "Generate decks from a prompt, edit visually, and present full-screen. An open-source replacement for Google Slides, Pitch, and PowerPoint."
 ---
 
-# Slides Template
+# Slides
 
-An open-source, agent-native presentation editor built on `@agent-native/core`. It replaces Google Slides, Pitch, and PowerPoint with a deck you can author in three ways at once — by talking to the agent, by clicking the canvas, or by editing HTML.
+Generate full presentation decks from a prompt, edit slides visually, and present full-screen. Ask the agent for "a 10-slide pitch deck for a coffee subscription service" and watch it stream slide-by-slide into the editor in seconds. An open-source replacement for Google Slides, Pitch, and PowerPoint.
 
-## Overview {#overview}
+When you open the app, you'll see your deck list. Click into a deck and you get a slide editor in the middle, a sidebar of slides on the left, and the agent on the right.
 
-The Slides template is a full presentation studio:
+## What you can do with it
 
-- Generate complete decks from a prompt, one slide at a time.
-- Edit slides visually or drop into raw HTML for full control.
-- Generate images with Gemini, search stock photos, and look up company logos.
-- Present full-screen with keyboard navigation and speaker notes.
-- Comment, share, and collaborate in real time over Yjs.
+- **Generate decks from a prompt.** "Generate a 10-slide pitch deck for a coffee subscription service, audience is investors."
+- **Edit slides visually** — double-click text to edit, click a block for the bubble menu, use `/` for the slash menu to insert blocks.
+- **Generate images with AI.** Hero images, product mockups, illustrations — generated with Gemini, multiple variations per request.
+- **Search stock photos and company logos.** "Find the logo for stripe.com and add it to slide 2."
+- **Present full-screen** with keyboard navigation, auto-hiding controls, and speaker notes.
+- **Comment, collaborate, and share.** Multiple people can edit the same deck in real time. Generate a public read-only URL or share with specific teammates.
+- **Import from PDF.** Turn a PDF into a starter deck — the agent parses it and lays out the content.
 
-Every operation the UI does — creating a deck, adding a slide, swapping an image — is exposed as an action the agent can call too. The agent and UI always stay in sync because they read and write the same SQL database.
+## Getting started
 
-## Quick start {#quick-start}
+Live demo: [slides.agent-native.com](https://slides.agent-native.com).
+
+When you open the app:
+
+1. Click **New deck**.
+2. In the agent sidebar, ask: "Generate a 10-slide pitch deck for a coffee subscription service, audience is investors."
+3. Watch slides stream in. Click any slide to edit, or keep asking the agent to refine.
+
+### Useful prompts
+
+- "Generate a 10-slide pitch deck for a coffee subscription service, audience is investors."
+- "Add a pricing slide after slide 3."
+- "Make the title on this slide bigger and change the accent color to green."
+- "Generate a hero image for the current slide — dark, minimal, cinematic."
+- "Find the logo for stripe.com and add it to slide 2."
+- "Replace the word 'customers' with 'members' everywhere in this deck."
+- "Summarize this PDF as a 6-slide deck." (attach the PDF)
+
+Select text on a slide and hit Cmd+I to focus the agent with that selection — it'll act only on what you selected.
+
+## For developers
+
+The rest of this doc is for anyone forking the Slides template or extending it.
+
+### Quick start
 
 Create a new Slides app from the CLI:
 
@@ -29,11 +55,7 @@ cd my-slides
 pnpm dev
 ```
 
-Or try the hosted demo at [slides.agent-native.com](https://slides.agent-native.com).
-
-Once running, open the app, click "New deck", and ask the agent in the sidebar: "Generate a 10-slide pitch deck for a coffee subscription service."
-
-## Key features {#key-features}
+### Key features (technical) {#key-features}
 
 ### Prompt-to-deck generation
 
@@ -91,20 +113,10 @@ Cmd+Z and Cmd+Shift+Z work across the whole deck, with a labeled history panel (
 
 Turn a PDF into a starter deck. The `extract-pdf` action parses the file and hands the content to the agent for layout.
 
-## Working with the agent {#working-with-the-agent}
+### Working with the agent
 
 The agent chat lives in the sidebar. It can create decks, edit individual slides, generate images, search logos, and navigate the UI — all using the same actions you'd run from the CLI.
 
-### Example prompts
-
-- "Generate a 10-slide pitch deck for a coffee subscription service, audience is investors."
-- "Add a pricing slide after slide 3."
-- "Make the title on this slide bigger and change the accent color to green."
-- "Generate a hero image for the current slide — dark, minimal, cinematic."
-- "Find the logo for stripe.com and add it to slide 2."
-- "Replace the word 'customers' with 'members' everywhere in this deck."
-- "Summarize this PDF as a 6-slide deck." (attach the PDF)
-
 ### What the agent sees
 
 When a deck is open, the agent automatically sees:
@@ -123,7 +135,7 @@ Select text on a slide and hit Cmd+I to focus the agent with that selection pre-
 
 The agent can embed a live slide preview directly in a chat reply using the framework's embed fence. It renders a chromeless iframe via `app/routes/slide.tsx` so you can see the result without leaving the conversation.
 
-## Data model {#data-model}
+### Data model
 
 All deck data lives in SQL via Drizzle ORM. Schema: `templates/slides/server/db/schema.ts`.
 
@@ -169,7 +181,7 @@ Each slide inside `decks.data` is:
 
 `content` is raw HTML — the renderer (`app/components/deck/SlideRenderer.tsx`) provides the black background and fixed aspect ratio, and the HTML provides everything inside. Rich embedding is supported too: Excalidraw diagrams via `ExcalidrawSlide.tsx` and Mermaid charts via `MermaidRenderer.tsx`.
 
-## Customizing it {#customizing-it}
+### Customizing it
 
 The Slides template is fully forkable. Key places to look when extending it: