@mindstudio-ai/remy 0.1.131 → 0.1.133

package/dist/headless.js

@@ -4707,9 +4707,9 @@ Use <current_deck> as your starting point and replace or update the content as n
 ### Rules
 - The deck must be a single HTML file \u2014 it will be rendered in an iframe.
 - Must look beautiful on desktop and mobile.
-- Animation between slides must be seamless, no flicker or flashing. For reveal animations: hide elements with CSS \`opacity: 0\` only (no transform in CSS). Let GSAP handle transforms via inline styles and never use \`clearProps\`.
+- Animation between slides must be seamless, no flicker or flashing. For reveal animations: hide elements with CSS \`opacity: 0\` only (no transform in CSS). Let GSAP handle transforms via inline styles and never use \`clearProps\`. Use the existing scaffold, do not write your own transition logic or slide mechanics.
 - Be bold and impactful.
-- Code must be clean, bug free, and easy to parse. Use GSAP for animations.
+- Code must be clean, bug free, and easy to parse. Use GSAP for animations. Pay close attention to layout and alignment to make sure everything is perfect.
 - Keep the progress bar and edge chevrons from the shell \u2014 they are part of the navigation UX.
 
 Respond only with the complete HTML file and absolutely no other text. Your response will be written directly to an html file.`;

package/dist/index.js

@@ -4664,9 +4664,9 @@ Use <current_deck> as your starting point and replace or update the content as n
 ### Rules
 - The deck must be a single HTML file \u2014 it will be rendered in an iframe.
 - Must look beautiful on desktop and mobile.
-- Animation between slides must be seamless, no flicker or flashing. For reveal animations: hide elements with CSS \`opacity: 0\` only (no transform in CSS). Let GSAP handle transforms via inline styles and never use \`clearProps\`.
+- Animation between slides must be seamless, no flicker or flashing. For reveal animations: hide elements with CSS \`opacity: 0\` only (no transform in CSS). Let GSAP handle transforms via inline styles and never use \`clearProps\`. Use the existing scaffold, do not write your own transition logic or slide mechanics.
 - Be bold and impactful.
-- Code must be clean, bug free, and easy to parse. Use GSAP for animations.
+- Code must be clean, bug free, and easy to parse. Use GSAP for animations. Pay close attention to layout and alignment to make sure everything is perfect.
 - Keep the progress bar and edge chevrons from the shell \u2014 they are part of the navigation UX.
 
 Respond only with the complete HTML file and absolutely no other text. Your response will be written directly to an html file.`;

package/dist/prompt/static/coding.md

@@ -49,7 +49,10 @@ For multi-step tasks with branching logic (research, enrichment, content pipelin
 - Runtime errors must render visibly on screen, not produce a blank white page. User and agent must be able to visibly debug and spot them.
 
 ### State Management
-- Calls to methods introduce latency. When building web frontends that load data from methods, front-load as much data as you can in a single API request - e.g., when possible, load a large data object into a central store and use that to render sub-screens in an app, rather than an API call on every screen. User experience and perceived speed/performance are far more valuable than normalization and good REST API design.
+- Prefer to use a library like Zustand for global state. Load a big data bundle on app start into a Zustand store, then render everything from memory. Navigation between screens should feel instant — no loading spinners for data that's already in the store.
+- Optimistic updates: mutate the store immediately, fire the API call in the background, roll back on error. The user should never wait for the server to confirm before seeing their change.
+- Not everything needs global state. Form inputs, UI toggles, modal visibility — keep those in local component state. Global state is for data that multiple screens need access to.
+- Do not use SWR for apps where you can load everything on startup. Those libraries are for server-cache patterns where data is too large or dynamic to hold in memory. For small apps with a handful of users, a Zustand store with a single initial fetch is simpler and faster.
 
 ### Secrets & Third-Party Integrations
 When a method needs credentials for a third-party service, use `process.env` and use the CLI to set it on behalf of the user (chat logs are secure and scrubbed, so it's fine for them to paste) or they can set it manually in the Dashboard.

package/dist/subagents/codeSanityCheck/prompt.md

@@ -27,7 +27,7 @@ These are things we already know about and have decided to accept:
   - `@mindstudio-ai/interface` — frontend SDK. `createClient<T>()` gives typed RPC to backend methods (no raw fetch). `auth` handles auth state (`auth.currentUser`, `auth.onAuthStateChanged(cb)`, verification flows, logout). `platform.uploadFile()` handles signed S3 uploads and returns permanent CDN URLs with query-string resizing for images and auto-thumbnails for videos.
   - `@mindstudio-ai/agent` — backend SDK. `db.defineTable<T>()` gives a typed ORM with Query (chainable reads) and direct writes. `auth` gives `auth.userId`, `auth.roles`, `auth.requireRole()`, `auth.hasRole()`. Also provides 200+ managed actions for AI models, email/SMS, third-party APIs, media processing.
 - Libraries we know are actively maintained, don't bother checking:
-  - swr
+  - zustand
   - motion (formerly framer-motion — import from `motion/react`, not `framer-motion`)
   - gsap (now fully free, including ScrollTrigger, FLIP, MorphSVG)
   - styled-components

package/dist/subagents/productVision/pitch-deck-shell.html

@@ -150,11 +150,14 @@ html, body {
 
 @media (max-width: 768px) {
   .slide { padding: 32px 24px; }
-  .nav { bottom: 24px; }
 }
 
+/* Reveal: elements with data-reveal start hidden, GSAP animates them in */
+[data-reveal] { opacity: 0; }
+
 @media (prefers-reduced-motion: reduce) {
   *, *::before, *::after { transition-duration: 0.01ms !important; animation-duration: 0.01ms !important; }
+  [data-reveal] { opacity: 1 !important; }
 }
 </style>
 </head>
@@ -165,18 +168,18 @@ html, body {
 <div class="deck" id="deck">
 
   <div class="slide slide-dark" data-index="0">
-    <h1>Slide One</h1>
-    <p>Placeholder subtitle text</p>
+    <h1 data-reveal>Slide One</h1>
+    <p data-reveal>Placeholder subtitle text</p>
   </div>
 
   <div class="slide slide-light" data-index="1">
-    <h1 style="color:var(--text-dark)">Slide Two</h1>
-    <p>Another placeholder</p>
+    <h1 data-reveal style="color:var(--text-dark)">Slide Two</h1>
+    <p data-reveal>Another placeholder</p>
   </div>
 
   <div class="slide slide-dark" data-index="2">
-    <h1>Slide Three</h1>
-    <p>Final placeholder</p>
+    <h1 data-reveal>Slide Three</h1>
+    <p data-reveal>Final placeholder</p>
   </div>
 
 </div>
@@ -204,6 +207,8 @@ html, body {
   const tapPrev = document.getElementById('tapPrev');
   const tapNext = document.getElementById('tapNext');
   const progress = document.getElementById('progress');
+  const chevronPrev = document.getElementById('chevronPrev');
+  const chevronNext = document.getElementById('chevronNext');
 
   // Build progress segments
   for (let i = 0; i < totalSlides; i++) {
@@ -226,15 +231,30 @@ html, body {
     chevronPrev.classList.toggle('hidden', current === 0);
     chevronNext.classList.toggle('hidden', current === totalSlides - 1);
 
-    // Light/dark adjustment
-    const isLight = slides[current].classList.contains('slide-light');
+    // Light/dark adjustment — checks class or data-theme attribute
+    const s = slides[current];
+    const isLight = s.classList.contains('slide-light') || s.classList.contains('s-light') || s.dataset.theme === 'light';
     progress.classList.toggle('light', isLight);
     chevronPrev.classList.toggle('light', isLight);
     chevronNext.classList.toggle('light', isLight);
   }
 
-  const chevronPrev = document.getElementById('chevronPrev');
-  const chevronNext = document.getElementById('chevronNext');
+  // Slide content reveal — called once per slide on first visit.
+  // Elements with [data-reveal] start hidden (CSS opacity:0) and
+  // animate in. Override this function to customize per-slide animations.
+  const revealed = new Set();
+  function revealSlide(index) {
+    if (revealed.has(index)) return;
+    revealed.add(index);
+    const els = slides[index].querySelectorAll('[data-reveal]');
+    els.forEach((el, i) => {
+      const delay = (parseFloat(el.dataset.reveal) || 0) + i * 0.04;
+      gsap.fromTo(el,
+        { opacity: 0, y: 16 },
+        { opacity: 1, y: 0, duration: 0.5, delay, ease: 'power2.out' }
+      );
+    });
+  }
 
   function goTo(index) {
     if (index === current || isAnimating || index < 0 || index >= totalSlides) return;
@@ -246,7 +266,10 @@ html, body {
       x: -current * window.innerWidth,
       duration: 0.4,
       ease: 'power2.inOut',
-      onComplete: () => { isAnimating = false; }
+      onComplete: () => {
+        revealSlide(current);
+        isAnimating = false;
+      }
     });
   }
 
@@ -287,9 +310,11 @@ html, body {
     resizeTimer = setTimeout(() => gsap.set(deck, { x: -current * window.innerWidth }), 100);
   });
 
-  // Init
+  // Init — first slide is visible immediately, no reveal animation
   gsap.set(deck, { x: 0 });
   updateNav();
+  revealed.add(0);
+  slides[0].querySelectorAll('[data-reveal]').forEach(el => { el.style.opacity = 1; });
 })();
 </script>
 

package/package.json

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