create-instant-app 1.0.21 → 1.0.22

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-instant-app",
-  "version": "1.0.21",
+  "version": "1.0.22",
   "description": "Scaffold a new web/mobile app with InstantDB",
   "homepage": "https://github.com/instantdb/instant/tree/main/client/packages/create-instant-app",
   "repository": {
@@ -35,9 +35,9 @@
     "slugify": "^1.6.6",
     "sort-package-json": "^2.10.0",
     "tiged": "^2.12.7",
-    "@instantdb/platform": "1.0.21",
-    "@instantdb/version": "1.0.21",
-    "instant-cli": "1.0.21"
+    "@instantdb/platform": "1.0.22",
+    "@instantdb/version": "1.0.22",
+    "instant-cli": "1.0.22"
   },
   "devDependencies": {
     "@anthropic-ai/sdk": "^0.60.0",

package/template/rules/AGENTS.md

@@ -13,6 +13,8 @@ Instant provides client-side JS SDKs and an admin SDK:
 - `@instantdb/core` --- vanilla JS
 - `@instantdb/react` --- React
 - `@instantdb/react-native` --- React Native / Expo
+- `@instantdb/solidjs` --- SolidJS
+- `@instantdb/svelte` --- Svelte
 - `@instantdb/admin` --- backend scripts / servers
 
 When installing, always check what package manager the project uses (npm, pnpm,
@@ -256,6 +258,40 @@ const { data } = db.useQuery({ posts: { image: {} } });
 <img src={post.image.url} />
 ```
 
+# CRITICAL Rooms Guidelines
+
+CRITICAL: Hooks for presence and topics live on `db.rooms` and take the room as the first arg. The room object itself has no `usePresence` or `publishPresence` methods.
+
+Rooms host two ephemeral primitives: presence (cursor positions, who's online) and topics (live reactions). Use them only for data that should NOT persist. Persisted data via `transact` already syncs in real-time to all subscribed clients, so reach for rooms only when the data is intentionally ephemeral.
+
+## Presence
+
+Each peer publishes a presence object readable by all other peers in the room. Retained for the connection and cleaned up automatically on disconnect.
+
+```tsx
+const room = db.room('chat', 'main');
+const { user, peers, publishPresence } = db.rooms.usePresence(room, {
+  initialPresence: { x: 0, y: 0 },
+});
+// peers is keyed by peerId, not an array. Use Object.values(peers) to iterate
+publishPresence({ x: 50, y: 50 });
+```
+
+## Topics
+
+Topic payloads aren't retained. Peers only see events fired while they're listening.
+
+```tsx
+const room = db.room('chat', 'main');
+
+const publishEmoji = db.rooms.usePublishTopic(room, 'emoji');
+publishEmoji({ name: 'fire' });
+
+db.rooms.useTopicEffect(room, 'emoji', (payload) => {
+  animateEmoji(payload.name);
+});
+```
+
 # Best Practices
 
 ## Pass `schema` when initializing Instant

package/template/rules/cursor-rules.md

@@ -19,6 +19,8 @@ Instant provides client-side JS SDKs and an admin SDK:
 - `@instantdb/core` --- vanilla JS
 - `@instantdb/react` --- React
 - `@instantdb/react-native` --- React Native / Expo
+- `@instantdb/solidjs` --- SolidJS
+- `@instantdb/svelte` --- Svelte
 - `@instantdb/admin` --- backend scripts / servers
 
 When installing, always check what package manager the project uses (npm, pnpm,
@@ -262,6 +264,40 @@ const { data } = db.useQuery({ posts: { image: {} } });
 <img src={post.image.url} />
 ```
 
+# CRITICAL Rooms Guidelines
+
+CRITICAL: Hooks for presence and topics live on `db.rooms` and take the room as the first arg. The room object itself has no `usePresence` or `publishPresence` methods.
+
+Rooms host two ephemeral primitives: presence (cursor positions, who's online) and topics (live reactions). Use them only for data that should NOT persist. Persisted data via `transact` already syncs in real-time to all subscribed clients, so reach for rooms only when the data is intentionally ephemeral.
+
+## Presence
+
+Each peer publishes a presence object readable by all other peers in the room. Retained for the connection and cleaned up automatically on disconnect.
+
+```tsx
+const room = db.room('chat', 'main');
+const { user, peers, publishPresence } = db.rooms.usePresence(room, {
+  initialPresence: { x: 0, y: 0 },
+});
+// peers is keyed by peerId, not an array. Use Object.values(peers) to iterate
+publishPresence({ x: 50, y: 50 });
+```
+
+## Topics
+
+Topic payloads aren't retained. Peers only see events fired while they're listening.
+
+```tsx
+const room = db.room('chat', 'main');
+
+const publishEmoji = db.rooms.usePublishTopic(room, 'emoji');
+publishEmoji({ name: 'fire' });
+
+db.rooms.useTopicEffect(room, 'emoji', (payload) => {
+  animateEmoji(payload.name);
+});
+```
+
 # Best Practices
 
 ## Pass `schema` when initializing Instant

package/template/rules/windsurf-rules.md

@@ -19,6 +19,8 @@ Instant provides client-side JS SDKs and an admin SDK:
 - `@instantdb/core` --- vanilla JS
 - `@instantdb/react` --- React
 - `@instantdb/react-native` --- React Native / Expo
+- `@instantdb/solidjs` --- SolidJS
+- `@instantdb/svelte` --- Svelte
 - `@instantdb/admin` --- backend scripts / servers
 
 When installing, always check what package manager the project uses (npm, pnpm,
@@ -262,6 +264,40 @@ const { data } = db.useQuery({ posts: { image: {} } });
 <img src={post.image.url} />
 ```
 
+# CRITICAL Rooms Guidelines
+
+CRITICAL: Hooks for presence and topics live on `db.rooms` and take the room as the first arg. The room object itself has no `usePresence` or `publishPresence` methods.
+
+Rooms host two ephemeral primitives: presence (cursor positions, who's online) and topics (live reactions). Use them only for data that should NOT persist. Persisted data via `transact` already syncs in real-time to all subscribed clients, so reach for rooms only when the data is intentionally ephemeral.
+
+## Presence
+
+Each peer publishes a presence object readable by all other peers in the room. Retained for the connection and cleaned up automatically on disconnect.
+
+```tsx
+const room = db.room('chat', 'main');
+const { user, peers, publishPresence } = db.rooms.usePresence(room, {
+  initialPresence: { x: 0, y: 0 },
+});
+// peers is keyed by peerId, not an array. Use Object.values(peers) to iterate
+publishPresence({ x: 50, y: 50 });
+```
+
+## Topics
+
+Topic payloads aren't retained. Peers only see events fired while they're listening.
+
+```tsx
+const room = db.room('chat', 'main');
+
+const publishEmoji = db.rooms.usePublishTopic(room, 'emoji');
+publishEmoji({ name: 'fire' });
+
+db.rooms.useTopicEffect(room, 'emoji', (payload) => {
+  animateEmoji(payload.name);
+});
+```
+
 # Best Practices
 
 ## Pass `schema` when initializing Instant