@mindstudio-ai/remy 0.1.95 → 0.1.96
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.
|
@@ -35,6 +35,13 @@ For any work involving AI models, external actions (web scraping, email, SMS), o
|
|
|
35
35
|
- The auth table is the user profile. Add custom fields (displayName, avatar, plan, etc.) alongside the platform-managed columns. Don't create a separate profile table.
|
|
36
36
|
- For apps with roles, create scenarios that seed users with different roles so the developer can test each perspective. Use the scenario `roles` field for impersonation.
|
|
37
37
|
|
|
38
|
+
### CSS & Layout
|
|
39
|
+
- Prefer CSS grid for page-level layout, flex for component-level alignment.
|
|
40
|
+
- Use `gap` for spacing instead of margin hacks.
|
|
41
|
+
- Use `dvh`/`svh` for mobile viewport heights.
|
|
42
|
+
- Use `clamp()`, `min()`, `max()` for fluid sizing instead of fixed pixel values with media query breakpoints.
|
|
43
|
+
- Use container queries for components that need to adapt to their container rather than the viewport.
|
|
44
|
+
|
|
38
45
|
### State Management
|
|
39
46
|
- Calls to methods introduce latency. When building web frontends that load data from methods, consider front-loading as much data as you can in a single API request - e.g., when possible, load a large data object into a central store and use that to render sub-screens in an app, rather than an API call on every screen.
|
|
40
47
|
|
|
@@ -10,6 +10,10 @@ When descirbing UI patterns to the developer, be verbose and explicit. Describe
|
|
|
10
10
|
|
|
11
11
|
The design should look like it could be an Apple iOS/macOS app of the year winner for 2026. Avoid long pages, things that feel like blogs, things that borrow from "dated" app store apps, and the like. It should feel like an award winner from the past two years, not an award winner from a decade ago.
|
|
12
12
|
|
|
13
|
+
### Interactive Surfaces
|
|
14
|
+
|
|
15
|
+
When specifying sheets, drawers, modals, or any surface that slides/fades into view, always include the interaction and motion details. The developer will build the minimal static version if you don't. Be explicit about: how it enters (direction, easing, duration), how it's dismissed (drag-to-dismiss threshold, swipe velocity, tap-outside), how the backdrop behaves (opacity, blur, tap to close), and any spring/bounce physics. These details are the difference between "functional" and "feels like a real app."
|
|
16
|
+
|
|
13
17
|
### Notes for Designing Auth Flows
|
|
14
18
|
|
|
15
19
|
Login and signup screens set the tone for the user's entire experience with the app and are important to get right - they should feel like exciting entry points into the next level of the user journy. A janky login form with misaligned inputs and no feedback dminishes excitement and undermines trust before the user even gets in.
|