@mindstudio-ai/remy 0.1.28 → 0.1.30

package/dist/headless.js

@@ -2646,13 +2646,13 @@ var DESIGN_EXPERT_TOOLS = [
   },
   {
     name: "runBrowserTest",
-    description: "Run an automated browser test against the live app preview. Use to verify visual implementation: check computed styles, navigate between pages, take analyzed screenshots. Describe what you want to verify and the browser agent handles the interaction.",
+    description: "Run an automated browser test against the live app preview. Use to verify implementation details via getComputedStyle: font-family names, exact colors, spacing, borders, shadows, font sizes, transforms. Also supports navigation between pages and screenshots. Use this to confirm the right fonts are loaded and CSS values match the spec.",
     inputSchema: {
       type: "object",
       properties: {
         task: {
           type: "string",
-          description: 'What to verify, in natural language. E.g., "Check that the hero section cards have border-radius: 24px and the correct rotation angles" or "Navigate to /about and screenshot it".'
+          description: 'What to verify, in natural language. Focus on measurable properties: "Check the hero cards have border-radius: 24px and box-shadow" or "Verify the background color of the CTA section is #C4FF0D".'
         }
       },
       required: ["task"]

package/dist/index.js

@@ -2767,13 +2767,13 @@ var init_tools2 = __esm({
       },
       {
         name: "runBrowserTest",
-        description: "Run an automated browser test against the live app preview. Use to verify visual implementation: check computed styles, navigate between pages, take analyzed screenshots. Describe what you want to verify and the browser agent handles the interaction.",
+        description: "Run an automated browser test against the live app preview. Use to verify implementation details via getComputedStyle: font-family names, exact colors, spacing, borders, shadows, font sizes, transforms. Also supports navigation between pages and screenshots. Use this to confirm the right fonts are loaded and CSS values match the spec.",
         inputSchema: {
           type: "object",
           properties: {
             task: {
               type: "string",
-              description: 'What to verify, in natural language. E.g., "Check that the hero section cards have border-radius: 24px and the correct rotation angles" or "Navigate to /about and screenshot it".'
+              description: 'What to verify, in natural language. Focus on measurable properties: "Check the hero cards have border-radius: 24px and box-shadow" or "Verify the background color of the CTA section is #C4FF0D".'
             }
           },
           required: ["task"]

package/dist/subagents/designExpert/prompts/images.md

@@ -26,7 +26,7 @@ Lead with the visual style, then describe the content. This order helps the mode
 - Describing positions of arms, legs, or specific limb arrangements.
 - Conflicting style instructions ("photorealistic cartoon").
 - Describing what you don't want — say "empty street" not "street with no cars."
-- Words like "editorial", "magazine", "Vogue", "cover" — the model interprets these literally and renders magazine masthead text over the image. Describe the lighting, composition, and mood you want instead of referencing publications.
+- Image models have a high risk of rendering text. Any word or phrase in your prompt that could be interpreted as a title, label, or caption risks appearing as literal text in the image. Triggers like "magazine cover" also risk making it render a literal mockup of a magazine masthread, even if all you wanted was a certain photography stype. Common triggers: "poster", "editorial", "magazine", "cover", "sign", or brand names, industry jargon, etc. Be thoughtful, careful, and intentional with your prompt - especially when describing abtract visualizations - and describe the visual qualities you want instead of referencing formats or concepts as shorthand.
 
 ### How generated images work in the UI
 

package/dist/subagents/designExpert/prompts/instructions.md

@@ -1,7 +1,9 @@
 ## Tool usage
 
 - Use `analyzeReferenceImageOrUrl` to analyze any image URL or website URL. Websites are automatically screenshotted. Omit the prompt for a standard design analysis, or provide a custom prompt for specific questions. Do not screenshot font specimen pages, documentation, or other text-heavy pages — use `fetchUrl` for those instead.
-- Use `screenshot` to capture the current state of the app preview. Use this when reviewing the UI being built — for gut checks, design feedback, or verifying that your recommendations were implemented correctly.
+- Use `screenshot` to see the current state of the app preview. This is your primary tool for visual review. Use `fullPage: true` to see the entire page at once. Remember, the screenshot analysis is not overly precise - for example, it cannot reliably identify specific fonts by name — it can only describe what letterforms look like.
+- Use `runBrowserTest` only to verify specific computed values that a screenshot can't tell you: exact font-family names, hex colors, pixel measurements, border-radius, box-shadow, transforms. Keep requests focused — ask it to check specific properties on specific elements, not to take screenshots or scroll around.
+- **screenshot vs runBrowserTest**: Screenshot to *see* the page. Browser test to *measure* specific CSS values. Never use the browser agent for tasks your screenshot tool can handle, or vice versa.
 - Use `searchGoogle` and `fetchUrl` only when the user references something specific: a particular website to match, a brand to look up, a company whose identity you need to research. You already have curated fonts, inspiration references, and strong internal knowledge — don't search the web for generic inspiration or "best X apps." The web is for specific lookups, not creative direction.
 - When proposing multiple options, make them genuinely different directions (dark + bold vs. light + editorial) rather than minor variations.
 - When multiple tool calls are independent, make them all in a single turn. Searching for three different products, or fetching two reference sites: batch them instead of doing one per turn.

package/package.json

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