better-cmdk 0.0.22 → 0.0.23

package/dist/nextjs/AGENTS.md

@@ -344,6 +344,14 @@ const assistant = useAssistant({
   getContext: () => ({
     currentPage: window.location.pathname,
     currentDateTime: new Date().toISOString(),
+    // Pass as much app data as possible — reuse existing cached queries.
+    // The AI can only help with what it can see. Include:
+    // - User profile (name, email, timezone, role, preferences)
+    // - Core entities (projects, items, orders — whatever your app manages)
+    // - Recent activity (upcoming events, notifications, recent changes)
+    // - Connected accounts (integrations, linked services)
+    // - Settings (theme, defaults, feature flags)
+    // See modifywithai's AGENTS.md Step 5b for a full context discovery guide.
   }),
 })
 
@@ -355,6 +363,8 @@ const assistant = useAssistant({
 />
 ```
 
+**Context richness matters.** The AI can only answer questions about data it receives via `getContext`. Passing just `currentPage` means the AI can't answer "what are my projects?" or "who's on my team?" Reuse your app's existing data-fetching hooks (React Query, tRPC, SWR) — they're already cached client-side, so this adds zero extra network requests. Aim for 5-15 data categories covering user profile, core entities, recent activity, connected accounts, and settings.
+
 ---
 
 ## Step 7: Mount the component

package/dist/remix/AGENTS.md

@@ -342,6 +342,14 @@ const assistant = useAssistant({
   getContext: () => ({
     currentPage: window.location.pathname,
     currentDateTime: new Date().toISOString(),
+    // Pass as much app data as possible — reuse existing cached queries.
+    // The AI can only help with what it can see. Include:
+    // - User profile (name, email, timezone, role, preferences)
+    // - Core entities (projects, items, orders — whatever your app manages)
+    // - Recent activity (upcoming events, notifications, recent changes)
+    // - Connected accounts (integrations, linked services)
+    // - Settings (theme, defaults, feature flags)
+    // See modifywithai's AGENTS.md Step 5b for a full context discovery guide.
   }),
 })
 
@@ -353,6 +361,8 @@ const assistant = useAssistant({
 />
 ```
 
+**Context richness matters.** The AI can only answer questions about data it receives via `getContext`. Passing just `currentPage` means the AI can't answer "what are my projects?" or "who's on my team?" Reuse your app's existing data-fetching hooks (React Query, tRPC, SWR) — they're already cached client-side, so this adds zero extra network requests. Aim for 5-15 data categories covering user profile, core entities, recent activity, connected accounts, and settings.
+
 ---
 
 ## Step 7: Mount the component

package/dist/tanstack-start/AGENTS.md

@@ -344,6 +344,14 @@ const assistant = useAssistant({
   getContext: () => ({
     currentPage: window.location.pathname,
     currentDateTime: new Date().toISOString(),
+    // Pass as much app data as possible — reuse existing cached queries.
+    // The AI can only help with what it can see. Include:
+    // - User profile (name, email, timezone, role, preferences)
+    // - Core entities (projects, items, orders — whatever your app manages)
+    // - Recent activity (upcoming events, notifications, recent changes)
+    // - Connected accounts (integrations, linked services)
+    // - Settings (theme, defaults, feature flags)
+    // See modifywithai's AGENTS.md Step 5b for a full context discovery guide.
   }),
 })
 
@@ -355,6 +363,8 @@ const assistant = useAssistant({
 />
 ```
 
+**Context richness matters.** The AI can only answer questions about data it receives via `getContext`. Passing just `currentPage` means the AI can't answer "what are my projects?" or "who's on my team?" Reuse your app's existing data-fetching hooks (React Query, tRPC, SWR) — they're already cached client-side, so this adds zero extra network requests. Aim for 5-15 data categories covering user profile, core entities, recent activity, connected accounts, and settings.
+
 ---
 
 ## Step 7: Mount the component

package/dist/vite/AGENTS.md

@@ -343,6 +343,14 @@ const assistant = useAssistant({
   getContext: () => ({
     currentPage: window.location.pathname,
     currentDateTime: new Date().toISOString(),
+    // Pass as much app data as possible — reuse existing cached queries.
+    // The AI can only help with what it can see. Include:
+    // - User profile (name, email, timezone, role, preferences)
+    // - Core entities (projects, items, orders — whatever your app manages)
+    // - Recent activity (upcoming events, notifications, recent changes)
+    // - Connected accounts (integrations, linked services)
+    // - Settings (theme, defaults, feature flags)
+    // See modifywithai's AGENTS.md Step 5b for a full context discovery guide.
   }),
 })
 
@@ -354,6 +362,8 @@ const assistant = useAssistant({
 />
 ```
 
+**Context richness matters.** The AI can only answer questions about data it receives via `getContext`. Passing just `currentPage` means the AI can't answer "what are my projects?" or "who's on my team?" Reuse your app's existing data-fetching hooks (React Query, tRPC, SWR) — they're already cached client-side, so this adds zero extra network requests. Aim for 5-15 data categories covering user profile, core entities, recent activity, connected accounts, and settings.
+
 ---
 
 ## Step 7: Mount the component

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "better-cmdk",
-  "version": "0.0.22",
+  "version": "0.0.23",
   "type": "module",
   "main": "./dist/index.js",
   "module": "./dist/index.js",