@mindstudio-ai/remy 0.1.14 → 0.1.16

package/dist/compiled/sdk-actions.md

@@ -2,7 +2,9 @@
 
 `@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 the `askMindStudioSdk` tool to look up exact method signatures, model IDs, and config options before writing code that uses the SDK.** The SDK assistant knows every action, every model, every connector, and the user's configured OAuth connections. Don't guess at parameters or model IDs from memory.
+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.
 
 ## Usage in Methods
 

package/dist/headless.js

@@ -1245,13 +1245,20 @@ import { exec } from "child_process";
 var askMindStudioSdkTool = {
   definition: {
     name: "askMindStudioSdk",
-    description: "Ask the MindStudio SDK assistant about available actions, AI models, connectors, and integrations using natural language. Returns code examples with correct method signatures, model IDs, and config options. Always use this to verify correct SDK usage, especially model IDs and configuration options. Describe what you need, not what API methods you need; the assistant will figure out the right approach. This runs its own LLM call so it has a few seconds of latency; batch multiple questions into a single query.",
+    description: `An expert consultant on building with the MindStudio SDK. Knows every action, model, connector, and configuration option. Use this as an architect, not just a docs lookup:
+
+- Describe what you're trying to build at the method level ("I need a method that takes user text, generates a summary with GPT, extracts entities, and returns structured JSON") and get back architectural guidance + working code.
+- Ask about AI orchestration patterns: structured output, chaining model calls, batch processing, streaming, error handling.
+- Ask about connectors and integrations: what's available, whether the user has configured it, how to use it.
+- Always use this before writing SDK code. Model IDs, config options, and action signatures change frequently. Don't guess.
+
+Batch related questions into a single query. This runs its own LLM call so it has a few seconds of latency.`,
     inputSchema: {
       type: "object",
       properties: {
         query: {
           type: "string",
-          description: "Natural language question about the SDK."
+          description: "Describe what you want to build or what you need to know. Be specific about the goal, not just the API method."
         }
       },
       required: ["query"]

package/dist/index.js

@@ -1021,13 +1021,20 @@ var init_askMindStudioSdk = __esm({
     askMindStudioSdkTool = {
       definition: {
         name: "askMindStudioSdk",
-        description: "Ask the MindStudio SDK assistant about available actions, AI models, connectors, and integrations using natural language. Returns code examples with correct method signatures, model IDs, and config options. Always use this to verify correct SDK usage, especially model IDs and configuration options. Describe what you need, not what API methods you need; the assistant will figure out the right approach. This runs its own LLM call so it has a few seconds of latency; batch multiple questions into a single query.",
+        description: `An expert consultant on building with the MindStudio SDK. Knows every action, model, connector, and configuration option. Use this as an architect, not just a docs lookup:
+
+- Describe what you're trying to build at the method level ("I need a method that takes user text, generates a summary with GPT, extracts entities, and returns structured JSON") and get back architectural guidance + working code.
+- Ask about AI orchestration patterns: structured output, chaining model calls, batch processing, streaming, error handling.
+- Ask about connectors and integrations: what's available, whether the user has configured it, how to use it.
+- Always use this before writing SDK code. Model IDs, config options, and action signatures change frequently. Don't guess.
+
+Batch related questions into a single query. This runs its own LLM call so it has a few seconds of latency.`,
         inputSchema: {
           type: "object",
           properties: {
             query: {
               type: "string",
-              description: "Natural language question about the SDK."
+              description: "Describe what you want to build or what you need to know. Be specific about the goal, not just the API method."
             }
           },
           required: ["query"]

package/dist/prompt/compiled/sdk-actions.md

@@ -2,7 +2,9 @@
 
 `@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 the `askMindStudioSdk` tool to look up exact method signatures, model IDs, and config options before writing code that uses the SDK.** The SDK assistant knows every action, every model, every connector, and the user's configured OAuth connections. Don't guess at parameters or model IDs from memory.
+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.
 
 ## Usage in Methods
 

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

@@ -16,35 +16,20 @@ Do not provide images as "references" - images must be ready-to-use assets that
 
 ### Writing good generation prompts
 
-Write prompts as natural sentences describing a scene, not as comma-separated keyword lists. Describe what a camera would see, not art direction instructions.
+Lead with the visual style, then describe the content. This order helps the model establish the look before filling in details.
 
-**Structure:** Subject and action first, then setting, then style and technical details. Include the intended use when relevant.
+**Structure:** Style/medium first, then subject, then details.
+- "Digital photography, soft natural window light, shallow depth of field. A ceramic coffee cup on a marble countertop, morning light casting long shadows, warm tones."
+- "Flat vector illustration, clean lines, limited color palette. An isometric view of a workspace with a laptop, plant, and notebook."
+- "Abstract digital art, fluid gradients, high contrast. Deep navy flowing into warm amber, organic liquid shapes, editorial feel."
 
-- "A woman laughing while reading on a sun-drenched balcony overlooking a Mediterranean harbor. Editorial photography, shot on Kodak Portra 400, 85mm lens at f/2, soft golden hour light, shallow depth of field. For a lifestyle app hero section."
-- "An overhead view of a cluttered designer's desk with fabric swatches, sketches, and a coffee cup. Natural window light from the left, slightly desaturated tones, Canon 5D with 35mm lens. For an about page."
-- "Smooth organic shapes in deep navy and warm amber, flowing liquid forms with subtle grain texture. Abstract digital art, high contrast, editorial feel."
-
-**Photography vocabulary produces the best results.** The model responds strongly to specific references:
-- Film stocks: Kodak Portra, Fuji Superia, Cinestill 800T, expired film
-- Lenses: 85mm f/1.4, 35mm wide angle, 50mm Summilux, macro
-- Lighting: golden hour, chiaroscuro, tungsten warmth, soft diffused studio light, direct flash
-- Shot types: close-up, overhead flat lay, low angle, eye-level candid, aerial
-- Techniques: shallow depth of field, halation around highlights, film grain, motion blur
-
-**Declare the medium early.** Saying "editorial photograph" vs "watercolor painting" vs "3D render" doesn't just change style — it changes the model's entire approach to composition, color, and detail. Set this expectation in the first sentence.
-
-**For text in images**, wrap the exact text in double quotes and specify the style: `A neon sign reading "OPEN" in cursive pink lettering against a dark brick wall.`
-
-**Compose for the layout.** If you know the image will have text overlaid, request space for it: "negative space in the upper left for headline text" or "clean sky area above the subject." If it's a background, consider "centered subject with clean margins." The first few words of the prompt carry the most weight — lead with the medium and subject.
+**For photorealistic images:** Specify the photography style (editorial, portrait, product, aerial), lighting (natural, studio, golden hour, direct flash), and camera characteristics (close-up, wide angle, shallow depth of field, slightly grainy texture).
 
 **Avoid:**
 - Hex codes in prompts — the model renders them as visible text. Describe colors by name instead.
-- Keyword lists separated by commas — write sentences.
 - 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."
-- UI component language — "glass morphism effect", "card design", "button with hover state". Write prompts as if briefing a photographer or artist, not describing CSS.
-- Generating text that should be HTML. Headlines, body copy, CTAs, and any text the user needs to read or interact with belongs in the markup, not baked into an image. Text *within a scene* is fine — a neon sign, a logo on a t-shirt, text on a billboard in a cityscape, an app screen in a device mockup. That's part of the visual content.
 
 ### How generated images work in the UI
 

package/package.json

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