@mindstudio-ai/remy 0.1.75 → 0.1.76
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/headless.js +107 -67
- package/dist/index.js +125 -75
- package/dist/subagents/designExpert/data/sources/ui_inspiration.json +49 -1
- package/dist/subagents/designExpert/data/sources/ui_inspiration_compiled.json +192 -0
- package/dist/subagents/designExpert/prompts/images.md +4 -2
- package/dist/subagents/designExpert/tools/images/enhance-image-prompt.md +4 -3
- package/package.json +1 -1
|
@@ -71,9 +71,11 @@ The developer should never need to source their own imagery. Always provide URLs
|
|
|
71
71
|
|
|
72
72
|
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.
|
|
73
73
|
|
|
74
|
-
**What works:**
|
|
74
|
+
**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.
|
|
75
75
|
|
|
76
|
-
**
|
|
76
|
+
**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.
|
|
77
|
+
|
|
78
|
+
**What doesn't work:** Flat illustration looks dated, photorealistic rendering is too noisy at small sizes, overly detailed scenes become illegible.
|
|
77
79
|
|
|
78
80
|
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.
|
|
79
81
|
|
|
@@ -51,11 +51,12 @@ For photorealistic images, be specific about:
|
|
|
51
51
|
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.
|
|
52
52
|
|
|
53
53
|
- 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.
|
|
54
|
-
-
|
|
55
|
-
-
|
|
54
|
+
- 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.
|
|
55
|
+
- One clear object or symbol, not a scene. Simplify aggressively — detail that looks good at 1024px becomes mud at 64px.
|
|
56
56
|
- Specify "reads well at small sizes" as an explicit constraint.
|
|
57
57
|
- 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.
|
|
58
|
-
-
|
|
58
|
+
- **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.
|
|
59
|
+
- **Logos and icons used inside the product** (headers, splash screens, favicons) should use transparent backgrounds so they composite onto any layout.
|
|
59
60
|
|
|
60
61
|
## Output
|
|
61
62
|
|