npm - @agent-native/core - Versions diffs - 0.175.4-nightly-20260826190205 → 0.175.4 - Mend

@agent-native/core 0.175.4-nightly-20260826190205 → 0.175.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (508) hide show

package/corpus/templates/factory/.agents/skills/agent-native-toolkit/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: agent-native-toolkit
 description: >-
-  Inventory and ownership rules for shared Agent Native workspace UI. Use
+  Inventory and ownership rules for shared Agent-Native workspace UI. Use
   before building app chrome, settings, navigation, sharing, collaboration,
   setup, history, comments, chat rails, agent UX, or repeated workspace behavior.
 scope: dev

package/corpus/templates/factory/.agents/skills/customizing-agent-native/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: customizing-agent-native
 description: >-
-  How to configure, compose, or eject Agent Native features into app-owned
+  How to configure, compose, or eject Agent-Native features into app-owned
   code. Use when overriding shared components or integrations, customizing a
   template, adding UI to chat or headless apps, or inspecting package source.
 scope: dev
@@ -9,7 +9,7 @@ metadata:
   internal: true
 ---
-# Customizing Agent Native
+# Customizing Agent-Native
 ## Rule
@@ -205,7 +205,7 @@ UI ownership may change; product contracts should not:
 ## Don't
 - Don't edit or import from `node_modules/@agent-native/*/src` at runtime.
-- Don't add `pnpm.overrides`, patches, or resolutions for Agent Native packages.
+- Don't add `pnpm.overrides`, patches, or resolutions for Agent-Native packages.
 - Don't copy Core auth, DB, action, agent-loop, or transport internals.
 - Don't manually copy a first-party unit with a missing recipe; fix its manifest.
 - Don't eject a full package when a prop, slot, wrapper, or smaller unit works.

package/corpus/templates/factory/.agents/skills/frontend-design/SKILL.md CHANGED Viewed

@@ -137,7 +137,7 @@ yours to apply.
 ## Agent-Native UI Rules
-- Agent-native apps use React and Vite. The default adapter uses Tailwind CSS,
+- Agent-Native apps use React and Vite. The default adapter uses Tailwind CSS,
   shadcn/ui, and `@tabler/icons-react`, but an app may register a different
   company design system in `app/design-system.ts`.
 - **Use the app's design-system seam for standard UI.** Inspect

package/corpus/templates/factory/.agents/skills/shadcn-ui/SKILL.md CHANGED Viewed

@@ -21,7 +21,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 ## First Steps
 1. Work from the app root that owns `components.json`.
-2. In an Agent Native app, inspect `app/design-system.ts` and
+2. In an Agent-Native app, inspect `app/design-system.ts` and
    `ToolkitProvider` before choosing a primitive. A registered company design
    system takes precedence over the default shadcn adapter.
 3. Run `pnpm dlx shadcn@latest info --json` when you need current project context: framework, Tailwind version, aliases, icon library, installed components, and resolved paths.
@@ -29,7 +29,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 5. Check `app/components/ui/` or the resolved `ui` path before importing a component.
 6. For unfamiliar components, run `pnpm dlx shadcn@latest docs <component>` and read the returned docs or examples before coding.
-## Agent Native Adapter Rule
+## Agent-Native Adapter Rule
 Pages, routes, and domain components import controls through the app's local UI
 adapter layer. Never import `@agent-native/toolkit/ui/*` directly in app product
@@ -102,7 +102,7 @@ shadcn's built-in component animations are the right level of polish — keep th
 ## Icons
-- Agent-native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
+- Agent-Native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
 - If registry code imports a different icon package, replace those imports with Tabler equivalents before finishing.
 - Let shadcn components size icons through their CSS. Avoid manual icon sizing inside buttons, menus, alerts, and sidebars unless the local component API requires it.

package/corpus/templates/factory/.agents/skills/storing-data/SKILL.md CHANGED Viewed

@@ -23,7 +23,7 @@ When you add a data model, a list, or a read path, also follow the `performance`
 ## How It Works
-Agent-native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
+Agent-Native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
 For app code, use Drizzle's schema/query DSL by default. Raw SQL is an escape hatch for additive migrations, health checks, or one-off maintenance, not the normal way to build features.

package/corpus/templates/factory/.agents/skills/workspace-conventions/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: workspace-conventions
 description: >-
-  Shared conventions for a multi-app Agent Native workspace: finding
+  Shared conventions for a multi-app Agent-Native workspace: finding
   version-matched framework docs and source, shared vs app-owned code, file and
   blob storage, env and secrets, agent scratch files, and Dispatch Resources.
   Use when working across workspace apps, storing files or credentials, or

package/corpus/templates/factory/CHANGELOG.md CHANGED Viewed

@@ -51,7 +51,7 @@ time from the command menu (Cmd+K → "What's new").
 ### Improved
-- Clicking the Agent Native logo now toggles the app sidebar.
+- Clicking the Agent-Native logo now toggles the app sidebar.
 ## 2026-07-29

package/corpus/templates/factory/changelog/2026-07-31-clicking-the-agent-native-logo-now-toggles-the-app-sidebar.md CHANGED Viewed

@@ -3,4 +3,4 @@ type: improved
 date: 2026-07-31
 ---
-Clicking the Agent Native logo now toggles the app sidebar.
+Clicking the Agent-Native logo now toggles the app sidebar.

package/corpus/templates/factory/changelog/2026-08-24-slack-polling-accepts-the-agentnative-bot-handle.md CHANGED Viewed

@@ -3,4 +3,4 @@ type: fixed
 date: 2026-08-24
 ---
-Slack polling now recognizes the Agent Native bot when Slack reports its handle as @agentnative.
+Slack polling now recognizes the Agent-Native bot when Slack reports its handle as @agentnative.

package/corpus/templates/forms/.agents/skills/adding-a-feature/SKILL.md CHANGED Viewed

@@ -18,7 +18,7 @@ Scope check first: this is the checklist for a feature that adds app data or a n
 ## Why
-Agent-native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
+Agent-Native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
 ## The Checklist

package/corpus/templates/forms/.agents/skills/agent-native-docs/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: agent-native-docs
 description: >-
-  How to find version-matched Agent Native framework docs and source bundled in
+  How to find version-matched Agent-Native framework docs and source bundled in
   node_modules. Use before implementing or answering questions about
   @agent-native/core APIs, generated apps, workspaces, templates, or advanced
   features.
@@ -10,11 +10,11 @@ metadata:
   internal: true
 ---
-# Agent Native Docs Lookup
+# Agent-Native Docs Lookup
 ## Rule
-Before implementing or explaining non-trivial Agent Native behavior, read the
+Before implementing or explaining non-trivial Agent-Native behavior, read the
 version-matched docs installed with `@agent-native/core`. When examples,
 imports, or implementation details matter, inspect the packaged source corpus
 too.

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

@@ -1,7 +1,7 @@
 ---
 name: agent-native-toolkit
 description: >-
-  Inventory and ownership rules for shared Agent Native workspace UI. Use
+  Inventory and ownership rules for shared Agent-Native workspace UI. Use
   before building app chrome, settings, navigation, sharing, collaboration,
   setup, history, comments, chat rails, agent UX, or repeated workspace behavior.
 scope: dev

package/corpus/templates/forms/.agents/skills/customizing-agent-native/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: customizing-agent-native
 description: >-
-  How to configure, compose, or eject Agent Native features into app-owned
+  How to configure, compose, or eject Agent-Native features into app-owned
   code. Use when overriding shared components or integrations, customizing a
   template, adding UI to chat or headless apps, or inspecting package source.
 scope: dev
@@ -9,7 +9,7 @@ metadata:
   internal: true
 ---
-# Customizing Agent Native
+# Customizing Agent-Native
 ## Rule
@@ -205,7 +205,7 @@ UI ownership may change; product contracts should not:
 ## Don't
 - Don't edit or import from `node_modules/@agent-native/*/src` at runtime.
-- Don't add `pnpm.overrides`, patches, or resolutions for Agent Native packages.
+- Don't add `pnpm.overrides`, patches, or resolutions for Agent-Native packages.
 - Don't copy Core auth, DB, action, agent-loop, or transport internals.
 - Don't manually copy a first-party unit with a missing recipe; fix its manifest.
 - Don't eject a full package when a prop, slot, wrapper, or smaller unit works.

package/corpus/templates/forms/.agents/skills/form-publishing/SKILL.md CHANGED Viewed

@@ -51,7 +51,7 @@ Public form submissions can be protected with Cloudflare Turnstile (opt-in). Thi
 ## Branding
-Public forms display a "Built with Agent Native" badge by default. This can be configured in the form settings.
+Public forms display a "Built with Agent-Native" badge by default. This can be configured in the form settings.
 ## Form Settings

package/corpus/templates/forms/.agents/skills/frontend-design/SKILL.md CHANGED Viewed

@@ -137,7 +137,7 @@ yours to apply.
 ## Agent-Native UI Rules
-- Agent-native apps use React and Vite. The default adapter uses Tailwind CSS,
+- Agent-Native apps use React and Vite. The default adapter uses Tailwind CSS,
   shadcn/ui, and `@tabler/icons-react`, but an app may register a different
   company design system in `app/design-system.ts`.
 - **Use the app's design-system seam for standard UI.** Inspect

package/corpus/templates/forms/.agents/skills/shadcn-ui/SKILL.md CHANGED Viewed

@@ -21,7 +21,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 ## First Steps
 1. Work from the app root that owns `components.json`.
-2. In an Agent Native app, inspect `app/design-system.ts` and
+2. In an Agent-Native app, inspect `app/design-system.ts` and
    `ToolkitProvider` before choosing a primitive. A registered company design
    system takes precedence over the default shadcn adapter.
 3. Run `pnpm dlx shadcn@latest info --json` when you need current project context: framework, Tailwind version, aliases, icon library, installed components, and resolved paths.
@@ -29,7 +29,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 5. Check `app/components/ui/` or the resolved `ui` path before importing a component.
 6. For unfamiliar components, run `pnpm dlx shadcn@latest docs <component>` and read the returned docs or examples before coding.
-## Agent Native Adapter Rule
+## Agent-Native Adapter Rule
 Pages, routes, and domain components import controls through the app's local UI
 adapter layer. Never import `@agent-native/toolkit/ui/*` directly in app product
@@ -102,7 +102,7 @@ shadcn's built-in component animations are the right level of polish — keep th
 ## Icons
-- Agent-native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
+- Agent-Native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
 - If registry code imports a different icon package, replace those imports with Tabler equivalents before finishing.
 - Let shadcn components size icons through their CSS. Avoid manual icon sizing inside buttons, menus, alerts, and sidebars unless the local component API requires it.

package/corpus/templates/forms/.agents/skills/storing-data/SKILL.md CHANGED Viewed

@@ -23,7 +23,7 @@ When you add a data model, a list, or a read path, also follow the `performance`
 ## How It Works
-Agent-native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
+Agent-Native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
 For app code, use Drizzle's schema/query DSL by default. Raw SQL is an escape hatch for additive migrations, health checks, or one-off maintenance, not the normal way to build features.

package/corpus/templates/forms/.agents/skills/workspace-conventions/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: workspace-conventions
 description: >-
-  Shared conventions for a multi-app Agent Native workspace: finding
+  Shared conventions for a multi-app Agent-Native workspace: finding
   version-matched framework docs and source, shared vs app-owned code, file and
   blob storage, env and secrets, agent scratch files, and Dispatch Resources.
   Use when working across workspace apps, storing files or credentials, or

package/corpus/templates/forms/CHANGELOG.md CHANGED Viewed

@@ -41,7 +41,7 @@ time from the command menu (Cmd+K → "What's new").
 ### Improved
-- The Agent Native logo stays visible when the sidebar is collapsed and toggles the sidebar when clicked.
+- The Agent-Native logo stays visible when the sidebar is collapsed and toggles the sidebar when clicked.
 ## 2026-07-29
@@ -177,7 +177,7 @@ time from the command menu (Cmd+K → "What's new").
 ### Fixed
-- Anonymous feedback no longer shows internal Agent Native anonymous-owner emails as submitter addresses.
+- Anonymous feedback no longer shows internal Agent-Native anonymous-owner emails as submitter addresses.
 - Traditional Chinese copy now uses Taiwan terminology and clearer technical wording.
 ## 2026-06-26

package/corpus/templates/forms/changelog/2026-06-27-anonymous-feedback-no-longer-shows-internal-agent-native-ano.md CHANGED Viewed

@@ -3,4 +3,4 @@ type: fixed
 date: 2026-06-27
 ---
-Anonymous feedback no longer shows internal Agent Native anonymous-owner emails as submitter addresses.
+Anonymous feedback no longer shows internal Agent-Native anonymous-owner emails as submitter addresses.

package/corpus/templates/forms/changelog/2026-07-31-the-agent-native-logo-stays-visible-when-the-sidebar-is-coll.md CHANGED Viewed

@@ -3,4 +3,4 @@ type: improved
 date: 2026-07-31
 ---
-The Agent Native logo stays visible when the sidebar is collapsed and toggles the sidebar when clicked.
+The Agent-Native logo stays visible when the sidebar is collapsed and toggles the sidebar when clicked.

package/corpus/templates/forms/server/lib/public-form-ssr.ts CHANGED Viewed

@@ -429,7 +429,7 @@ function renderFormPage(
   <a href="https://agent-native.com" target="_blank" rel="noopener noreferrer" class="powered-badge">
     <svg width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 2L2 7l10 5 10-5-10-5z"/><path d="M2 17l10 5 10-5"/><path d="M2 12l10 5 10-5"/></svg>
-    Built with Agent Native
+    Built with Agent-Native
   </a>
 </div>

package/corpus/templates/macros/.agents/skills/adding-a-feature/SKILL.md CHANGED Viewed

@@ -18,7 +18,7 @@ Scope check first: this is the checklist for a feature that adds app data or a n
 ## Why
-Agent-native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
+Agent-Native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
 ## The Checklist

package/corpus/templates/macros/.agents/skills/agent-native-docs/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: agent-native-docs
 description: >-
-  How to find version-matched Agent Native framework docs and source bundled in
+  How to find version-matched Agent-Native framework docs and source bundled in
   node_modules. Use before implementing or answering questions about
   @agent-native/core APIs, generated apps, workspaces, templates, or advanced
   features.
@@ -10,11 +10,11 @@ metadata:
   internal: true
 ---
-# Agent Native Docs Lookup
+# Agent-Native Docs Lookup
 ## Rule
-Before implementing or explaining non-trivial Agent Native behavior, read the
+Before implementing or explaining non-trivial Agent-Native behavior, read the
 version-matched docs installed with `@agent-native/core`. When examples,
 imports, or implementation details matter, inspect the packaged source corpus
 too.

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

@@ -1,7 +1,7 @@
 ---
 name: agent-native-toolkit
 description: >-
-  Inventory and ownership rules for shared Agent Native workspace UI. Use
+  Inventory and ownership rules for shared Agent-Native workspace UI. Use
   before building app chrome, settings, navigation, sharing, collaboration,
   setup, history, comments, chat rails, agent UX, or repeated workspace behavior.
 scope: dev

package/corpus/templates/macros/.agents/skills/customizing-agent-native/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: customizing-agent-native
 description: >-
-  How to configure, compose, or eject Agent Native features into app-owned
+  How to configure, compose, or eject Agent-Native features into app-owned
   code. Use when overriding shared components or integrations, customizing a
   template, adding UI to chat or headless apps, or inspecting package source.
 scope: dev
@@ -9,7 +9,7 @@ metadata:
   internal: true
 ---
-# Customizing Agent Native
+# Customizing Agent-Native
 ## Rule
@@ -205,7 +205,7 @@ UI ownership may change; product contracts should not:
 ## Don't
 - Don't edit or import from `node_modules/@agent-native/*/src` at runtime.
-- Don't add `pnpm.overrides`, patches, or resolutions for Agent Native packages.
+- Don't add `pnpm.overrides`, patches, or resolutions for Agent-Native packages.
 - Don't copy Core auth, DB, action, agent-loop, or transport internals.
 - Don't manually copy a first-party unit with a missing recipe; fix its manifest.
 - Don't eject a full package when a prop, slot, wrapper, or smaller unit works.

package/corpus/templates/macros/.agents/skills/frontend-design/SKILL.md CHANGED Viewed

@@ -137,7 +137,7 @@ yours to apply.
 ## Agent-Native UI Rules
-- Agent-native apps use React and Vite. The default adapter uses Tailwind CSS,
+- Agent-Native apps use React and Vite. The default adapter uses Tailwind CSS,
   shadcn/ui, and `@tabler/icons-react`, but an app may register a different
   company design system in `app/design-system.ts`.
 - **Use the app's design-system seam for standard UI.** Inspect

package/corpus/templates/macros/.agents/skills/shadcn-ui/SKILL.md CHANGED Viewed

@@ -21,7 +21,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 ## First Steps
 1. Work from the app root that owns `components.json`.
-2. In an Agent Native app, inspect `app/design-system.ts` and
+2. In an Agent-Native app, inspect `app/design-system.ts` and
    `ToolkitProvider` before choosing a primitive. A registered company design
    system takes precedence over the default shadcn adapter.
 3. Run `pnpm dlx shadcn@latest info --json` when you need current project context: framework, Tailwind version, aliases, icon library, installed components, and resolved paths.
@@ -29,7 +29,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 5. Check `app/components/ui/` or the resolved `ui` path before importing a component.
 6. For unfamiliar components, run `pnpm dlx shadcn@latest docs <component>` and read the returned docs or examples before coding.
-## Agent Native Adapter Rule
+## Agent-Native Adapter Rule
 Pages, routes, and domain components import controls through the app's local UI
 adapter layer. Never import `@agent-native/toolkit/ui/*` directly in app product
@@ -102,7 +102,7 @@ shadcn's built-in component animations are the right level of polish — keep th
 ## Icons
-- Agent-native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
+- Agent-Native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
 - If registry code imports a different icon package, replace those imports with Tabler equivalents before finishing.
 - Let shadcn components size icons through their CSS. Avoid manual icon sizing inside buttons, menus, alerts, and sidebars unless the local component API requires it.

package/corpus/templates/macros/.agents/skills/storing-data/SKILL.md CHANGED Viewed

@@ -23,7 +23,7 @@ When you add a data model, a list, or a read path, also follow the `performance`
 ## How It Works
-Agent-native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
+Agent-Native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
 For app code, use Drizzle's schema/query DSL by default. Raw SQL is an escape hatch for additive migrations, health checks, or one-off maintenance, not the normal way to build features.

package/corpus/templates/macros/.agents/skills/workspace-conventions/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: workspace-conventions
 description: >-
-  Shared conventions for a multi-app Agent Native workspace: finding
+  Shared conventions for a multi-app Agent-Native workspace: finding
   version-matched framework docs and source, shared vs app-owned code, file and
   blob storage, env and secrets, agent scratch files, and Dispatch Resources.
   Use when working across workspace apps, storing files or credentials, or

package/corpus/templates/mail/.agents/skills/adding-a-feature/SKILL.md CHANGED Viewed

@@ -18,7 +18,7 @@ Scope check first: this is the checklist for a feature that adds app data or a n
 ## Why
-Agent-native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
+Agent-Native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
 ## The Checklist

package/corpus/templates/mail/.agents/skills/agent-native-docs/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: agent-native-docs
 description: >-
-  How to find version-matched Agent Native framework docs and source bundled in
+  How to find version-matched Agent-Native framework docs and source bundled in
   node_modules. Use before implementing or answering questions about
   @agent-native/core APIs, generated apps, workspaces, templates, or advanced
   features.
@@ -10,11 +10,11 @@ metadata:
   internal: true
 ---
-# Agent Native Docs Lookup
+# Agent-Native Docs Lookup
 ## Rule
-Before implementing or explaining non-trivial Agent Native behavior, read the
+Before implementing or explaining non-trivial Agent-Native behavior, read the
 version-matched docs installed with `@agent-native/core`. When examples,
 imports, or implementation details matter, inspect the packaged source corpus
 too.

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

@@ -1,7 +1,7 @@
 ---
 name: agent-native-toolkit
 description: >-
-  Inventory and ownership rules for shared Agent Native workspace UI. Use
+  Inventory and ownership rules for shared Agent-Native workspace UI. Use
   before building app chrome, settings, navigation, sharing, collaboration,
   setup, history, comments, chat rails, agent UX, or repeated workspace behavior.
 scope: dev

package/corpus/templates/mail/.agents/skills/customizing-agent-native/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: customizing-agent-native
 description: >-
-  How to configure, compose, or eject Agent Native features into app-owned
+  How to configure, compose, or eject Agent-Native features into app-owned
   code. Use when overriding shared components or integrations, customizing a
   template, adding UI to chat or headless apps, or inspecting package source.
 scope: dev
@@ -9,7 +9,7 @@ metadata:
   internal: true
 ---
-# Customizing Agent Native
+# Customizing Agent-Native
 ## Rule
@@ -205,7 +205,7 @@ UI ownership may change; product contracts should not:
 ## Don't
 - Don't edit or import from `node_modules/@agent-native/*/src` at runtime.
-- Don't add `pnpm.overrides`, patches, or resolutions for Agent Native packages.
+- Don't add `pnpm.overrides`, patches, or resolutions for Agent-Native packages.
 - Don't copy Core auth, DB, action, agent-loop, or transport internals.
 - Don't manually copy a first-party unit with a missing recipe; fix its manifest.
 - Don't eject a full package when a prop, slot, wrapper, or smaller unit works.

package/corpus/templates/mail/.agents/skills/frontend-design/SKILL.md CHANGED Viewed

@@ -137,7 +137,7 @@ yours to apply.
 ## Agent-Native UI Rules
-- Agent-native apps use React and Vite. The default adapter uses Tailwind CSS,
+- Agent-Native apps use React and Vite. The default adapter uses Tailwind CSS,
   shadcn/ui, and `@tabler/icons-react`, but an app may register a different
   company design system in `app/design-system.ts`.
 - **Use the app's design-system seam for standard UI.** Inspect

package/corpus/templates/mail/.agents/skills/shadcn-ui/SKILL.md CHANGED Viewed

@@ -21,7 +21,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 ## First Steps
 1. Work from the app root that owns `components.json`.
-2. In an Agent Native app, inspect `app/design-system.ts` and
+2. In an Agent-Native app, inspect `app/design-system.ts` and
    `ToolkitProvider` before choosing a primitive. A registered company design
    system takes precedence over the default shadcn adapter.
 3. Run `pnpm dlx shadcn@latest info --json` when you need current project context: framework, Tailwind version, aliases, icon library, installed components, and resolved paths.
@@ -29,7 +29,7 @@ This skill keeps shadcn/ui work project-aware. Components are source files in th
 5. Check `app/components/ui/` or the resolved `ui` path before importing a component.
 6. For unfamiliar components, run `pnpm dlx shadcn@latest docs <component>` and read the returned docs or examples before coding.
-## Agent Native Adapter Rule
+## Agent-Native Adapter Rule
 Pages, routes, and domain components import controls through the app's local UI
 adapter layer. Never import `@agent-native/toolkit/ui/*` directly in app product
@@ -102,7 +102,7 @@ shadcn's built-in component animations are the right level of polish — keep th
 ## Icons
-- Agent-native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
+- Agent-Native apps use `@tabler/icons-react`. Do not add `lucide-react` because a registry example used it.
 - If registry code imports a different icon package, replace those imports with Tabler equivalents before finishing.
 - Let shadcn components size icons through their CSS. Avoid manual icon sizing inside buttons, menus, alerts, and sidebars unless the local component API requires it.

package/corpus/templates/mail/.agents/skills/storing-data/SKILL.md CHANGED Viewed

@@ -23,7 +23,7 @@ When you add a data model, a list, or a read path, also follow the `performance`
 ## How It Works
-Agent-native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
+Agent-Native apps use Drizzle ORM over the configured SQL backend. Local development works out of the box with a SQLite file at `data/app.db`; production and shared preview deploys need a persistent `DATABASE_URL` because container/serverless filesystems can reset. The code should behave the same across backends, but the local SQLite file is not durable once deployed.
 For app code, use Drizzle's schema/query DSL by default. Raw SQL is an escape hatch for additive migrations, health checks, or one-off maintenance, not the normal way to build features.

package/corpus/templates/mail/.agents/skills/workspace-conventions/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: workspace-conventions
 description: >-
-  Shared conventions for a multi-app Agent Native workspace: finding
+  Shared conventions for a multi-app Agent-Native workspace: finding
   version-matched framework docs and source, shared vs app-owned code, file and
   blob storage, env and secrets, agent scratch files, and Dispatch Resources.
   Use when working across workspace apps, storing files or credentials, or

package/corpus/templates/plan/.agents/skills/adding-a-feature/SKILL.md CHANGED Viewed

@@ -18,7 +18,7 @@ Scope check first: this is the checklist for a feature that adds app data or a n
 ## Why
-Agent-native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
+Agent-Native apps are defined by parity: everything the UI can do, the agent can do, and vice versa. A feature that only has UI is invisible to the agent. A feature that only has scripts is invisible to the user. A feature without app-state sync means the agent is blind to what the user is doing.
 ## The Checklist

package/corpus/templates/plan/.agents/skills/agent-native-docs/SKILL.md CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 name: agent-native-docs
 description: >-
-  How to find version-matched Agent Native framework docs and source bundled in
+  How to find version-matched Agent-Native framework docs and source bundled in
   node_modules. Use before implementing or answering questions about
   @agent-native/core APIs, generated apps, workspaces, templates, or advanced
   features.
@@ -10,11 +10,11 @@ metadata:
   internal: true
 ---
-# Agent Native Docs Lookup
+# Agent-Native Docs Lookup
 ## Rule
-Before implementing or explaining non-trivial Agent Native behavior, read the
+Before implementing or explaining non-trivial Agent-Native behavior, read the
 version-matched docs installed with `@agent-native/core`. When examples,
 imports, or implementation details matter, inspect the packaged source corpus
 too.

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

@@ -1,7 +1,7 @@
 ---
 name: agent-native-toolkit
 description: >-
-  Inventory and ownership rules for shared Agent Native workspace UI. Use
+  Inventory and ownership rules for shared Agent-Native workspace UI. Use
   before building app chrome, settings, navigation, sharing, collaboration,
   setup, history, comments, chat rails, agent UX, or repeated workspace behavior.
 scope: dev