@mindstudio-ai/remy 0.1.56 → 0.1.57

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.
@@ -1,29 +1,49 @@
1
1
  ## Layout Guidelines
2
2
 
3
- Layout is where interfaces fail most visibly. Generic patterns like centered content, three equal columns, card grids, symmetric everything feel tired and bland to users, and prevent the design from being effective. Fight the use of generic layouts 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 <visual_design_references> - these sites were hand-picked because they are doing something compelling. Remember, "good artists copy, great artists steal" may sound provocative, but it contains a fundamental truth about the nature of creativity that will help us dramatically elevate the experience for the user.
3
+ Layout has two layers: the spatial architecture (how the viewport is divided into functional regions) and the visual composition (how those regions look and feel). Get the architecture right first, then make it beautiful.
4
4
 
5
- If the design calls for it, take risks and be bold. It might not always work out and that's okay! The user always has the opportunity to refine - and if we can help push their thinking we can help them to unlock their own creativity and discover what it is they truly want.
5
+ ### Spatial Architecture
6
6
 
7
- Avoid generic and clichéd patterns. Anything that looks like it came from a squarespace template or bootstrap theme is unacceptable - we can do so much better than that and this is our opportunity to create truly compelling, unique layouts that provide the scaffolding and context for the content and design to shine.
7
+ Before deciding component styles, decide how the screen is organized. These are structural decisions that shape everything else.
8
8
 
9
- ### Some things that make layouts interesting
9
+ **Viewport regions.** Every app divides the screen into a few primary zones: navigation, primary content, secondary content, actions. Name them. Be explicit about what the regions are and how they relate to each other.
10
+
11
+ **Fixed vs. fluid.** Decide what's nailed to the viewport and what scrolls with content. Navigation, input bars, action toolbars, and floating action buttons are typically fixed. Content areas scroll. Getting this wrong is the #1 source of UX frustration — things the user needs constantly get scrolled away, or things that should flow get trapped in cramped fixed containers. State this explicitly in your layout spec.
12
+
13
+ **Density.** Information density is a design decision, not an accident. A trading dashboard and a meditation app need fundamentally different spatial densities. Dense layouts use tighter spacing, smaller type, more columns, compact components. Spacious layouts use generous padding, larger type, fewer elements per viewport. Match density to the domain and the user's task — a user scanning 50 rows of data needs density; a user composing a single message needs breathing room.
14
+
15
+ **Scroll strategy.** Where does scrolling happen? Specify this. Also make any necessary decisions relating infinite scroll vs. pagination vs. load-more for lists. Sticky headers within scroll regions. Whether scroll position resets on navigation.
16
+
17
+ **Navigation pattern.** How does the user move between sections? The navigation pattern is tied to the spatial architecture — a sidebar nav implies a different layout structure than bottom tabs.
18
+
19
+ ### Visual Composition
20
+
21
+ With the spatial architecture established, make it visually compelling. This is where the layout goes from functional to distinctive.
22
+
23
+ Layout is where interfaces fail most visibly. Generic patterns like centered content, three equal columns, card grids, symmetric everything feel tired and bland. Fight the use of generic layouts actively. Source layout inspiration from <visual_design_references> — these sites were hand-picked because they are doing something compelling.
24
+
25
+ If the design calls for it, take risks and be bold. It might not always work out and that's okay — the user always has the opportunity to refine.
26
+
27
+ #### Things that make layouts interesting
10
28
  - Asymmetry — varied column widths, off-center compositions
11
29
  - Scale contrast — one very large element next to several small ones
12
30
  - Creative negative space — intentional emptiness that creates tension and focus
13
31
  - Full-bleed elements — images, colors, or sections that break the grid
14
32
  - Varied density — some sections spacious, others information-dense
15
- - Unexpected compositions — css transformations in 3D space, skewed perspective tricks
33
+ - Unexpected compositions — CSS transformations in 3D space, skewed perspective tricks
16
34
 
17
- ### Anti-patterns to avoid
35
+ #### Anti-patterns to avoid
18
36
  - Three equal boxes with icons
19
37
  - Centered hero with subtitle and CTA button (generic landing page)
20
38
  - Uniform card grids with equal spacing
21
39
  - Everything centered, everything symmetric
22
- - "1 2 3" steps in boxes and other cliché landing page patterns
40
+ - "1 2 3" steps in boxes and other cliche landing page patterns
23
41
  - Narrow content columns with empty gutters on wide screens
24
42
 
25
43
  ### Backgrounds
44
+
26
45
  Backgrounds create atmosphere. Solid white or solid gray is the safe default and the enemy of distinctiveness. Layer subtle gradients, use warm or cool tints, add geometric patterns or contextual textures. The background sets the mood before the user reads a single word.
27
46
 
28
47
  ### Output
29
- When proposing layouts, describe the spatial composition in detail. Specify exact ratios, positions, and anything else the developer needs in order to correctly implement the vision.
48
+
49
+ When proposing layouts, describe both layers: the spatial architecture (regions, fixed vs. fluid, scroll behavior, responsive strategy) and the visual composition (proportions, spacing, visual techniques). Specify exact ratios, positions, and anything else the developer needs to correctly implement the vision.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mindstudio-ai/remy",
3
- "version": "0.1.56",
3
+ "version": "0.1.57",
4
4
  "description": "MindStudio coding agent",
5
5
  "repository": {
6
6
  "type": "git",