@mindstudio-ai/remy 0.1.69 → 0.1.71
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/README.md +1 -1
- package/dist/headless.js +103 -27
- package/dist/index.js +106 -28
- package/dist/prompt/compiled/auth.md +207 -32
- package/dist/prompt/compiled/design.md +15 -1
- package/dist/prompt/compiled/interfaces.md +8 -4
- package/dist/prompt/compiled/manifest.md +21 -0
- package/dist/prompt/compiled/methods.md +2 -4
- package/dist/prompt/compiled/platform.md +1 -1
- package/dist/prompt/compiled/tables.md +10 -0
- package/dist/prompt/static/authoring.md +13 -3
- package/dist/prompt/static/coding.md +13 -0
- package/dist/prompt/static/intake.md +51 -28
- package/dist/subagents/browserAutomation/prompt.md +4 -1
- package/dist/subagents/designExpert/prompts/instructions.md +3 -0
- package/dist/subagents/designExpert/prompts/ui-patterns.md +14 -0
- package/package.json +1 -1
|
@@ -10,6 +10,20 @@ 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
|
+
### Notes for Designing Auth Flows
|
|
14
|
+
|
|
15
|
+
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.
|
|
16
|
+
|
|
17
|
+
Authentication moments must feel natural and intuitive - they should not feel jarring or surprising. Take care to integrate them into the entire experience when building. MindStudio apps support SMS code verification, email verification, or both, depending on how the app is configured.
|
|
18
|
+
|
|
19
|
+
**Verification code input:** The 6-digit code entry is the critical moment. Prefer to design it as individual digit boxes (not a single text input), with auto-advance between digits, auto-submit on paste, and clear visual feedback. The boxes should be large enough to tap easily on mobile. Show a subtle animation on successful verification. Error states should be inline and immediate, not a separate alert.
|
|
20
|
+
|
|
21
|
+
**The send/resend flow:** After the user enters their email or phone and taps "Send code," show clear confirmation that the code was sent ("Check your email" with the address displayed). Include a resend option with a cooldown timer (e.g., "Resend in 30s"). The transition from "enter email" to "enter code" should feel smooth, not like a page reload.
|
|
22
|
+
|
|
23
|
+
**The overall login page:** This is a branding moment. Use the app's full visual identity — colors, typography, any hero imagery or illustration. A centered card on a branded background is a classic pattern. Don't make it look like a generic SaaS login template. The login page should feel like it belongs to this specific app.
|
|
24
|
+
|
|
25
|
+
**Post-login transition:** After successful verification, the transition into the app should feel seamless. Avoid a blank loading screen — if data needs to load, show the app shell with skeleton states.
|
|
26
|
+
|
|
13
27
|
### Notes for Designing AI Chat Interfaces
|
|
14
28
|
|
|
15
29
|
If the app includes an AI chat interface, take care to make it beautiful and intentional. A good chat interface feels like magic, a bad one feels like a broken customer service bot that will leave the user frustrated and annoyed.
|