@mindstudio-ai/remy 0.1.74 → 0.1.76

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

@@ -62,10 +62,23 @@ Remember: It's 2026. Everything is lifestyle and editorial these days. Even a la
 Default to photography with real subjects — people, scenes, moments, environments. Use editorial and fashion photography vocabulary in your prompts. When abstract art is the right call (textures, editorial collages, gradient art), make it bold and intentional, not generic gradient blobs.
 
 #### Match style to context
+
 Editorial photography is the right call for hero images, landing pages, marketing sites, and branding. But when generating images for scenario seed data — sample posts, user uploads, profile content, anything that's supposed to look like a real user created it — the target is authentic user-generated content, not a photographer's portfolio. A social app's seed photos should look like they came from someone's phone camera roll in 2026: well-lit because the phone's computational photography is good, but casually framed, slightly imperfect, real-life backgrounds. Think "my friend posted this on Instagram" not "Unsplash top pick." The difference between a compelling demo and a fake-feeling one is whether the seed content feels like real people made it.
 
 The developer should never need to source their own imagery. Always provide URLs.
 
+### Icons and logos
+
+App icons and logos require work and thinking to get right. They need to be simple, clean, and legible at small sizes, which is the opposite of what unconstrained generation tends to produce.
+
+**What works:** Polished 3D rendering in the style of current macOS/iOS app icons. One clear, simplified object or symbol with crisp geometry. Polished surfaces with specular highlights, tight gradients, and clean reflections. Two or three accent colors, not a rainbow.
+
+**App icons vs. in-product logos:** App icons must be full-bleed squares with a solid background — no transparency, no baked-in rounded corners. The OS applies its own mask. Generate these *without* `transparentBackground`. Logos and icons used inside the product (headers, splash screens, favicons) should use `transparentBackground: true` so they composite onto any layout.
+
+**What doesn't work:** Flat illustration looks dated, photorealistic rendering is too noisy at small sizes, overly detailed scenes become illegible.
+
+Generate multiple variants — small-size readability is hard to predict from a prompt. What looks great at full resolution may turn to mush at 64px. When reviewing generated icons, mentally shrink them to favicon size and ask if the subject is still recognizable.
+
 ### When to use images
 
 Include image recommendations in your designs when the product calls for it. A landing page without photography feels like a wireframe. A feature section with a real image feels finished. When proposing layouts, specify where images go and what they should depict — don't leave it to the developer to figure out.

package/dist/subagents/designExpert/tools/images/enhance-image-prompt.md

@@ -46,6 +46,18 @@ For photorealistic images, be specific about:
 
 **Casual / phone photography:** When the brief calls for candid, user-generated, or social-media-style photos, steer away from professional photography language. Instead describe the qualities of a good 2026 smartphone photo: sharp subject with computational HDR, natural ambient lighting, slightly busy or imperfect backgrounds, centered or off-center casual framing, no deliberate composition or artistic bokeh. The subject should look like someone pointed their phone and tapped — not posed, not art-directed. Describe it as "phone photo" or "iPhone photo" style, not "digital photography with shallow depth of field." Real people's photos are well-lit (phones are good now) but unpolished — a messy kitchen counter in frame, a friend mid-laugh with eyes half-closed, a dog blurry because it moved. That imperfection is what makes them feel authentic.
 
+## Icons and logos
+
+For app icons and logos, the goal is something that reads clearly at small sizes and feels polished enough to sit on a home screen or in an app header.
+
+- Frame as "A 3D icon against a white background:" followed by the subject. Do NOT use the phrase "app icon" — it triggers mockup framing (the model renders an icon inset on a phone screen or mounted on a wall). "3D icon" works.
+- Think current macOS/iOS app icon design language. Polished surfaces, crisp geometry, specular highlights, tight controlled gradients. The dimensionality comes from lighting and material quality.
+- One clear object or symbol, not a scene. Simplify aggressively — detail that looks good at 1024px becomes mud at 64px.
+- Specify "reads well at small sizes" as an explicit constraint.
+- Keep color intentional and limited — two or three accent colors plus the object's base tone. Colors should complement the app's brand if known.
+- **App icons** should be full-bleed squares with a solid background — no transparency, no baked-in rounded corners. The OS applies its own mask (squircle, rounded rect, circle) so the asset must fill the entire frame edge-to-edge.
+- **Logos and icons used inside the product** (headers, splash screens, favicons) should use transparent backgrounds so they composite onto any layout.
+
 ## Output
 
 Respond with ONLY the enhanced prompt. 3-5 sentences maximum. Be specific and visual, not abstract or conceptual.

package/package.json

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