@mindstudio-ai/remy 0.1.29 → 0.1.31

package/dist/headless.js

@@ -2579,7 +2579,7 @@ var DESIGN_REFERENCE_PROMPT = fs14.readFileSync(resolvePath("prompts/tool-prompt
 var DESIGN_EXPERT_TOOLS = [
   {
     name: "searchGoogle",
-    description: "Search Google for web results. Use for finding design inspiration, font recommendations, UI patterns, real products in a domain, and reference material.",
+    description: 'Search Google for web results. Reserch 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 from the results and then use `fetchUrl` to get their text content.',
     inputSchema: {
       type: "object",
       properties: {
@@ -2593,7 +2593,7 @@ var DESIGN_EXPERT_TOOLS = [
   },
   {
     name: "fetchUrl",
-    description: "Fetch the content of a web page as markdown. Optionally capture a screenshot to see the visual design. Use to analyze reference sites, read font specimen pages, or extract design details.",
+    description: "Fetch the content of a web page as markdown. Optionally capture a screenshot to see the visual design. Use when reading sites from search results or specific things the user wants to incorporate.",
     inputSchema: {
       type: "object",
       properties: {

package/dist/index.js

@@ -2700,7 +2700,7 @@ var init_tools2 = __esm({
     DESIGN_EXPERT_TOOLS = [
       {
         name: "searchGoogle",
-        description: "Search Google for web results. Use for finding design inspiration, font recommendations, UI patterns, real products in a domain, and reference material.",
+        description: 'Search Google for web results. Reserch 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 from the results and then use `fetchUrl` to get their text content.',
         inputSchema: {
           type: "object",
           properties: {
@@ -2714,7 +2714,7 @@ var init_tools2 = __esm({
       },
       {
         name: "fetchUrl",
-        description: "Fetch the content of a web page as markdown. Optionally capture a screenshot to see the visual design. Use to analyze reference sites, read font specimen pages, or extract design details.",
+        description: "Fetch the content of a web page as markdown. Optionally capture a screenshot to see the visual design. Use when reading sites from search results or specific things the user wants to incorporate.",
         inputSchema: {
           type: "object",
           properties: {

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

@@ -4,6 +4,8 @@
 - 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` 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.
 - 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.29",
+  "version": "0.1.31",
   "description": "MindStudio coding agent",
   "repository": {
     "type": "git",