@mindstudio-ai/remy 0.1.2 → 0.1.4

package/dist/compiled/design.md

@@ -125,6 +125,23 @@ Forms should feel like interactions, not paperwork.
 - Even data entry can be beautiful. Pay attention to alignment, padding,
   and spacing. Consistency is key.
 
+## Data Fetching and Updates
+
+The UI should feel instant. Never make the user wait for a server round-trip
+to see the result of their own action.
+
+- **Optimistic updates.** When a user adds a row, toggles a setting, or
+  submits a form, update the UI immediately and let the backend confirm
+  in the background. If the backend fails, revert and show an error.
+- **Use SWR for data fetching** (`useSWR` from the `swr` package). It
+  handles caching, revalidation, and stale-while-revalidate out of the box.
+  Prefer SWR over manual `useEffect` + `useState` fetch patterns.
+- **Mutate after actions.** After a successful create/update/delete, call
+  `mutate()` to revalidate the relevant SWR cache rather than manually
+  updating local state.
+- **Skeleton loading.** Show skeletons that mirror the layout on initial
+  load. Never show a blank page or centered spinner while data is loading.
+
 ## What Good Looks Like
 
 - A dashboard that feels like Linear — clean data, clear hierarchy, every

package/dist/compiled/tables.md

@@ -143,7 +143,9 @@ const minAmount = 10000;
 Vendors.filter(v => v.totalCents > minAmount)                         // captured variables
 ```
 
-If a predicate can't be compiled to SQL (complex closures, function calls), the SDK falls back to fetching all rows and filtering in JavaScript. A warning is logged.
+**What compiles to SQL** (efficient): equality, comparisons, `&&`/`||`, `.includes()` for arrays and strings, null checks, boolean negation, captured variables.
+
+**What falls back to JS** (fetches all rows, filters in memory): `.startsWith()`, regex, computed expressions like `o.a + o.b > 100`, complex closures. A warning is logged when this happens. Avoid these patterns on large tables.
 
 ### Time Helpers
 
@@ -160,17 +162,34 @@ db.ago(db.days(7) + db.hours(12)) // composable — 7.5 days ago
 Invoices.filter(i => i.dueDate < db.ago(db.days(30)))
 ```
 
-### Batch Queries
+### Batching
 
-Execute multiple queries in a single round-trip:
+`db.batch()` combines multiple operations into a single HTTP round-trip. Every `await` on a table operation is a network call, so batching is critical for performance. Use it whenever you have multiple reads, writes, or a mix of both:
 
 ```typescript
-const [vendors, orders] = await db.batch(
+// Reads: fetch related data in one call instead of sequential awaits
+const [vendors, orders, invoiceCount] = await db.batch(
   Vendors.filter(v => v.status === 'approved'),
   PurchaseOrders.filter(po => po.vendorId === vendorId),
+  Invoices.count(i => i.status === 'pending'),
+);
+
+// Writes: batch multiple updates instead of awaiting each one in a loop
+const mutations = items.map(item =>
+  Orders.update(item.id, { status: 'approved' })
+);
+await db.batch(...mutations);
+
+// Mixed: writes execute in order, reads observe prior writes
+const [_, newOrder, pending] = await db.batch(
+  Orders.update(id, { status: 'approved' }),
+  Orders.push({ item: 'Laptop', amount: 999, status: 'pending', requestedBy: userId }),
+  Orders.filter(o => o.status === 'pending').take(10),
 );
 ```
 
+**Always batch instead of sequential awaits.** A loop with `await Table.update()` inside makes N separate HTTP calls. Mapping to mutations and passing them to `db.batch()` makes one.
+
 ## Migrations
 
 No migration files. Migrations are automatic:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/remy",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "description": "MindStudio coding agent",
   "repository": {
     "type": "git",