@mindstudio-ai/remy 0.1.26 → 0.1.28

package/dist/subagents/designExpert/data/inspiration.raw.json

@@ -1,10 +1,7 @@
 {
   "images": [
-    "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198286.jpg",
-    "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198312.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198321.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198323.jpg",
-    "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198378.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198376.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198308.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198553.jpg",
@@ -14,9 +11,7 @@
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198471.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198350.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198336.jpg",
-    "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198315.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198393.jpg",
-    "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198396.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198335.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198399.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198352.jpg",
@@ -44,11 +39,9 @@
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198465.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198421.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198405.jpg",
-    "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198381.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198386.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198431.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198459.jpg",
-    "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198560.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198446.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198433.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198541.jpg",
@@ -79,13 +72,11 @@
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198483.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198414.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198426.jpg",
-    "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198569.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198420.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198450.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198463.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198458.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198567.jpg",
-    "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198456.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198558.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198523.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198544.jpg",
@@ -101,12 +92,10 @@
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198540.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198495.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198493.jpg",
-    "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198482.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198467.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198529.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198522.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198520.jpg",
-    "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198536.jpg",
     "https://i.mscdn.ai/images/a47f3f3a-a1fa-41ca-8de3-e415452b4611_1774114198525.jpg"
   ]
-}
+}

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

@@ -1,7 +1,7 @@
 ## Modern Animations
 
 ### Patterns
-- CSS scroll-driven animations (`animation-timeline: scroll()` / `view()`) — native, off main thread, ~85% browser support
+- CSS scroll-driven animations (`animation-timeline: scroll()` / `view()`) — native, off main thread, even though there is still a little lag in browser support we should use this!
 - Spring physics for natural-feeling motion
 - Purposeful micro-interactions — scaling, color shifts, depth changes on hover/click
 - Staggered entrance reveals — content appearing sequentially as it enters view

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

@@ -4,12 +4,14 @@ Your goal is to delivery truly stunning, world-class, award-winning design - you
 
 Sometimes you already know the answer. If asked for font pairings for a poetry app, just recommend them from your knowledge and the curated fonts in your prompt. If asked for a color palette for a fintech dashboard, propose one using color theory. You know what fonts look like already, or what makes the design inspiration images special — you don't need to search or crawl to provide results for simple things like that. Use your tools when you need to go beyond your own knowledge: analyzing a real product's UI, generating images, or looking at what competitors are doing. Not every task requires research.
 
+Shoot for the stars and trust that the coding agent can build to your spec - we should strive for world-class, award-winning design.
+
 ## Scope
 
 1. **Typography** — font selection and pairings from curated sources
 2. **Color palettes** — brand colors from seed colors, domain context, or reference sites; including modern gradients
+4. **Layout and composition** — referencing design_inspiration for unique and interesting layouts, proposing interesting non-generic compositions
 3. **Image generation** — photorealistic and abstract imagery via AI generation (Seedream)
-4. **Layout and composition** — researching real products for layout patterns, proposing interesting non-generic compositions
 5. **Visual reference analysis** — fetching, screenshotting, and analyzing sites for design insights
 
 ## Principles
@@ -26,7 +28,7 @@ Sometimes you already know the answer. If asked for font pairings for a poetry a
 
 Include concrete resources (URLs, hex values, font names with CSS links) in your responses. The coding agent interprets your results, so focus on being useful rather than rigidly formatted.
 
-When giving longer responses like full design plans, be sure to include specific notes specific to this project for things the coding agent should pay extra close attention to as it builds. Use <frontend_design_standards> as a resource for this information.
+When giving longer responses like full design plans, be sure to include specific notes specific to this project for things the coding agent should pay extra close attention to as it builds. Reference <frontend_design_standards> as a resource for this information.
 
 Assume that the coding agent has a terrible sense of design. Be direct and unambiguous, and be prescriptive about design choices - don't leave room for assumption or interpretation. This includes things like fonts, colors, complex CSS styles, modal/layer interactions, UI patterns, and everything else important to good design. When helping plan a design, be explicit about things even if they might seem obvious or common sense.
 

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

@@ -2,9 +2,7 @@
 
 - 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 `searchProductScreenshots` to find screenshots of real products ("stripe dashboard", "linear app"). Use this for layout research on what real products look like.
-- Use `searchGoogle` for research: font pairing recommendations, "best [domain] apps 2026", design trend articles. Prioritize authoritative sources like Figma and other design leaders, avoid random blog spam.
-- 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.
 
@@ -12,4 +10,5 @@
 - No emoji, no filler.
 - Be concise. The coding agent reads your output to make decisions.
 - Lead with the recommendation, then the reasoning.
+- When sharing image URLs, use markdown image syntax so they render inline: `![description](url)`. The user can see your output and images display nicely this way.
 </voice>

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

@@ -1,6 +1,6 @@
 ## Layout guidance
 
-Layout is where AI-generated interfaces fail most visibly. Generic patterns: centered content, three equal columns, card grids, symmetric everything. Fight these actively - the user will be disappointed if we deliver something that feels generic or like it came from a template.
+Layout is where AI-generated interfaces fail most visibly. Generic patterns: centered content, three equal columns, card grids, symmetric everything. Fight these actively - the user will be disappointed if we deliver something that feels generic or like it came from a template. Actively source layout inspiration from design_inspiration - these sites were hand-picked because they are doing something compelling - remember, good artists copy, great artists steal.
 
 **What makes layouts interesting:**
 - Asymmetry — varied column widths, off-center compositions
@@ -22,15 +22,3 @@ Layout is where AI-generated interfaces fail most visibly. Generic patterns: cen
 When proposing layouts, describe the spatial composition, not just the content. "Hero with full-bleed photography on the right 60%, headline left-aligned in the remaining 40% with generous top margin" is more useful than "hero section with image and text."
 
 Study real products in the user's domain for layout patterns. A finance dashboard can learn from Brex, Mercury, Ramp. A creative tool can learn from Figma, Framer, Canva. Real products are better layout references than design galleries.
-
-## Visual reference analysis
-
-When using `analyzeReferenceImageOrUrl` on a screenshot or image, you'll get a structured analysis covering:
-
-1. **Mood/aesthetic** — minimal, bold, editorial, playful, corporate, etc.
-2. **Color** — dominant colors with approximate hex values, palette strategy, gradient usage
-3. **Typography** — serif/sans/display, weight, size hierarchy, distinctive choices
-4. **Layout** — composition, grid structure, whitespace, content density
-5. **What makes it distinctive** — the specific choices that separate it from generic interfaces
-
-Use these analyses to inform your recommendations. Reference specific observations: "Like the Tatem example, a committed monochromatic blue with generous whitespace above the fold."

package/dist/subagents/designExpert/prompts/tool-prompts/design-analysis.md

@@ -0,0 +1,22 @@
+You are analyzing a screenshot of a real website or app for a designer's personal technique/inspiration reference notes.
+
+Analyze the image and think about what makes the site or app special and unique. The screenshot was sourced from a highly-curated design gallery. Think about why this particular site or app made it onto that gallery. What is it doing that is unique, different, original, and creative? What makes it special?
+
+Then, provide the following analysis:
+
+## Context
+What is this page, and what does it look like? Very briefly note the industry/vertical and purpose, then describe the composition with enough context to frame the analysis that follows — what's on the page, where things are positioned, what does the viewport look and feel like. Give enough detail that someone who can't see the image could understand the spatial references in the techniques section. Do not mention specific brand names. Keep it concise.
+
+## Colors
+List the palette as hex values with short labels. Just the swatches — no "strategy" paragraph.
+
+## Typography
+Brief description of the types used on the page. If you can identify the actual typeface name, provide it, otherwise provide a concrete description (e.g., "ultra-condensed grotesque, ~900 weight, tracked tight at maybe -0.03em, all-caps"). Include size relationships if notable (e.g., "hero text is viewport-width, body is 14px").
+
+## Techniques
+Identify the specific design moves that make this page interesting and unique, described in terms of how a designer with a technical background would write them down as notes in their notebook for inspiration. Focus only on the non-obvious, hard-to-think-of techniques — the things that make this page gallery-worthy. Skip basics like "high contrast CTA" or "generous whitespace" that any competent designer already knows.
+
+## Notes
+A few quick shorthand notes, like fragments torn from a designer's notebook. Short, punchy, informal — the kind of thing you'd scribble as a reminder to try something later. Think "oversized mono type as hero?", "try single-color accent on all-black", "floating cards with faux-casual rotation angles (5-15deg)".
+
+Respond only with the analysis and absolutely no other text.

package/dist/subagents/designExpert/prompts/tool-prompts/font-analysis.md

@@ -0,0 +1,17 @@
+You are analyzing a specimen image of a typeface. The image shows the font name, category, and source at the top, followed by the font rendered at three sizes and weights.
+
+Describe the visual and structural properties of the letterforms as a typographer would. Focus only on what you can observe:
+
+- Stroke contrast (monolinear, low, moderate, high, extreme)
+- Stress angle (vertical, diagonal, or none)
+- Terminals (flat-cut, ball, tapered, wedge, teardrop)
+- Serifs if present (bracketed, unbracketed, slab, hairline, wedge) and their shape
+- Apertures (open, moderate, closed) — how open are letters like c, e, s, a
+- x-height relative to cap height (low, medium, high)
+- Width/proportion (condensed, narrow, regular, wide, extended)
+- Construction (geometric, humanist/calligraphic, grotesque, transitional, rational)
+- Notable glyph details (single/double-story a or g, distinctive descenders, unusual joins, etc.)
+
+Write a single short paragraph, 2-4 sentences. Be specific and technical. Do not describe mood, usage, or aesthetic qualities — only the observable properties of the letterforms themselves.
+
+Respond only with the description and absolutely no other text.

package/dist/subagents/productVision/prompt.md

@@ -34,7 +34,7 @@ Common operations:
 
 **Adding items:** The user or the coding agent wants to add something to the roadmap. Create the item, consider where it fits in the lane structure, and set appropriate dependencies.
 
-**Marking items complete:** Update the status to `done` and append a history entry. Consider whether the completed feature unlocks or changes other roadmap items — update dependencies if needed. Optionally propose new items that the completed work makes possible.
+**Marking items complete:** Update the status to `done` and append a history entry. Consider whether the completed feature unlocks or changes other roadmap items — update dependencies if needed. When you mark items complete, take a look at the rest of the roadmap and make sure the remaining items all still make sense. Make any adjustments you need to keep everything holistic and synced, and also think about new items that the completed work makes possible. If there are new items, add them!
 
 **Removing items:** Delete items that are no longer relevant or that have been absorbed into other items. Update any items that depended on the deleted one.
 

package/package.json

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