@mindstudio-ai/remy 0.1.19 → 0.1.21

package/dist/actions/buildFromInitialSpec.md

@@ -1,7 +1,15 @@
 This is an automated action triggered by the user pressing "Build" in the editor after reviewing the spec.
 
-The user has reviewed the spec and is ready to build. Build everything in one turn: methods, tables, interfaces, manifest updates, and scenarios, using the spec as the master plan.
+The user has reviewed the spec and is ready to build. 
 
-When code generation is complete, verify your work: use `runScenario` to seed test data, then use `runMethod` to confirm a method works, then use `runAutomatedBrowserTest` to smoke-test the main UI flow. The dev database is a disposable snapshot, so don't worry about being destructive. Fix any errors before finishing.
+Think about your approach and then get a quick sanity check from `codeSanityCheck` to make sure you aren't missing anything.
 
-When everything is working, update `src/roadmap/mvp.md` to `status: done`, then call `setProjectOnboardingState({ state: "onboardingFinished" })`.
+Then, build everything in one turn: methods, tables, interfaces, manifest updates, and scenarios, using the spec as the master plan.
+
+When code generation is complete, verify your work: 
+- First, run use `runScenario` to seed test data, then use `runMethod` to confirm a method works 
+- If the app has a web frontend, check the browser logs to make sure there are no errors rendering it.
+- Ask the `visualDesignExpert` to take a screenshot and verity that the visual design looks correct. Fix any issues it flags - we want the user's first time seeing the finished product to truly wow them.
+- Finally, use `runAutomatedBrowserTest` to smoke-test the main UI flow. The dev database is a disposable snapshot, so don't worry about being destructive. Fix any errors before finishing.
+
+When everything is working, use `productVision` to mark the MVP roadmap item as done, then call `setProjectOnboardingState({ state: "onboardingFinished" })`.

package/dist/compiled/design.md

@@ -43,7 +43,7 @@ Derive additional implementation colors (borders, focus states, hover states, di
 
 ### Typography block format
 
-A `` ```typography `` fenced block in a `type: design/typography` spec file declares fonts (with source URLs) and one or two anchor styles (typically Display and Body). Derive additional styles (labels, buttons, captions, overlines) from these anchors:
+A `` ```typography `` fenced block in a `type: design/typography` spec file declares fonts (with source URLs) and one or two anchor styles (typically Display and Body). Styles can include an optional `case` field (`uppercase`, `lowercase`, `capitalize`) for text-transform. Derive additional styles (labels, buttons, captions, overlines) from these anchors:
 
 ```typography
 fonts:
@@ -59,6 +59,7 @@ styles:
     weight: 600
     letterSpacing: -0.03em
     lineHeight: 1.1
+    case: uppercase
     description: Page titles and hero text
   Body:
     font: Satoshi

package/dist/compiled/msfm.md

@@ -181,6 +181,7 @@ styles:
     weight: 600
     letterSpacing: -0.03em
     lineHeight: 1.1
+    case: uppercase
     description: Page titles and hero text
   Body:
     font: Satoshi

package/dist/compiled/sdk-actions.md

@@ -2,9 +2,7 @@
 
 `@mindstudio-ai/agent` provides access to 200+ AI models and 1,000+ actions through a single API key. No separate provider keys needed. MindStudio routes to the correct provider (OpenAI, Anthropic, Google, etc.) server-side.
 
-There is a huge amount of capability here: hundreds of text generation models (OpenAI, Anthropic, Google, Meta, Mistral, and more), dozens of image generation models (FLUX, DALL-E, Stable Diffusion, Ideogram, and more), video generation, text-to-speech, music generation, vision analysis, web scraping, 850+ OAuth connectors, and much more. The tables below are a summary.
-
-**Always use `askMindStudioSdk` before writing code that uses the SDK.** Treat it as an expert consultant, not a docs search. Describe what you're trying to build at the method level — the full workflow, not just "how do I call generateText." The assistant knows every action, model, connector, configuration option, and the user's configured OAuth connections. It can advise on AI orchestration patterns (structured output, chaining calls, batch processing), help you avoid common mistakes (like manually parsing JSON when the SDK has structured output options), and provide complete working code for your use case.
+There is a huge amount of capability here: hundreds of text generation models (OpenAI, Anthropic, Google, Meta, Mistral, and more), dozens of image generation models (FLUX, DALL-E, Stable Diffusion, Ideogram, and more), video generation, text-to-speech, music generation, vision analysis, web scraping, 850+ OAuth connectors, and much more. The tables below are a summary. Always use `askMindStudioSdk` before writing SDK code.
 
 ## Usage in Methods