@mindstudio-ai/remy 0.1.33 → 0.1.34

package/dist/headless.js

@@ -2649,7 +2649,7 @@ var DESIGN_EXPERT_TOOLS = [
   },
   {
     name: "runBrowserTest",
-    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.",
+    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. Only use this to evaluate computed CSS properties that can't be deduced from sceenshots.",
     inputSchema: {
       type: "object",
       properties: {

package/dist/index.js

@@ -2773,7 +2773,7 @@ var init_tools2 = __esm({
       },
       {
         name: "runBrowserTest",
-        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.",
+        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. Only use this to evaluate computed CSS properties that can't be deduced from sceenshots.",
         inputSchema: {
           type: "object",
           properties: {

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

@@ -2,8 +2,8 @@
 
 - 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 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` to smoke test and spot check the things most likely to be wrong — missing elements, colors that look off in the screenshot, transforms or animations that are hard to judge visually. Don't use it to verify every property in the spec. Trust that if the spec says something, like specifying fonts or layout sections, the coding agent probably implemented it - it's very good at following instructions. Reserve the browser agent for things you genuinely can't tell from looking.
-- **screenshot vs runBrowserTest**: Screenshot to *see* the page. Browser test to *measure* specific values you're unsure about. Start with a screenshot — only reach for the browser agent if something looks off or can't be judged visually. The browser agent is not a screenshot tool — don't ask it to scroll around taking screenshots of sections. Your `screenshot` tool with `fullPage: true` captures the entire page in one call.
+- Use `runBrowserTest` to verify and understand things you have flagged as being incorrect by analyzing the screenshot by checking their CSS properties. Describe everything you need in one call to the tool, it can do many things at once.
+- **screenshot vs runBrowserTest**: Screenshot to *see* the page. Browser test to *measure* specific values you're unsure about. Start with a screenshot — only reach for the browser agent if something looks off or can't be judged visually. Your `screenshot` tool with `fullPage: true` captures the entire page in one call.
 Use `searchGoogle` for research: modern design trends in industries or verticals, "best [domain] apps 2026", ui patterns, etc. Prioritize authoritative sources like Figma and other design leaders, avoid random blog spam. Pick one or more URLs and use `fetchUrl` to get their text content to read and inform your inspiration.
 - Use `fetchUrl` when you need to get the text content of a site.
 - 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.

package/package.json

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