@mindstudio-ai/remy 0.1.17 → 0.1.18
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.
|
@@ -48,7 +48,7 @@ After writing the first draft, guide the user through it. Don't just ask "does t
|
|
|
48
48
|
- When the user asks "is this ready?" — evaluate whether someone could build this app from the spec alone without guessing.
|
|
49
49
|
|
|
50
50
|
**Building from the spec:**
|
|
51
|
-
When the user clicks "Build," you will receive a build command. Build everything in one turn: methods, tables, interfaces, manifest updates, and scenarios, using the spec as the master plan. The onboarding state transitions are handled automatically as part of the build command.
|
|
51
|
+
When the user clicks "Build," you will receive a build command. Build everything in one turn: methods, tables, interfaces, manifest updates, and scenarios, using the spec as the master plan. Build only what's in the core spec files (app.md, interfaces, brand). Ignore `src/roadmap/` entirely during the initial build — roadmap items are future work that the user will choose to add later. The onboarding state transitions are handled automatically as part of the build command.
|
|
52
52
|
|
|
53
53
|
**Scenarios are required.** Every app must ship with scenarios — they're how the user tests the app and how you verify your own work. Write at minimum:
|
|
54
54
|
- A **realistic data scenario** with enough sample records to make the app feel populated and alive (5-20 rows depending on the app). Use plausible names, dates, amounts — not "test 1", "test 2".
|
package/dist/static/authoring.md
CHANGED
|
@@ -48,7 +48,7 @@ After writing the first draft, guide the user through it. Don't just ask "does t
|
|
|
48
48
|
- When the user asks "is this ready?" — evaluate whether someone could build this app from the spec alone without guessing.
|
|
49
49
|
|
|
50
50
|
**Building from the spec:**
|
|
51
|
-
When the user clicks "Build," you will receive a build command. Build everything in one turn: methods, tables, interfaces, manifest updates, and scenarios, using the spec as the master plan. The onboarding state transitions are handled automatically as part of the build command.
|
|
51
|
+
When the user clicks "Build," you will receive a build command. Build everything in one turn: methods, tables, interfaces, manifest updates, and scenarios, using the spec as the master plan. Build only what's in the core spec files (app.md, interfaces, brand). Ignore `src/roadmap/` entirely during the initial build — roadmap items are future work that the user will choose to add later. The onboarding state transitions are handled automatically as part of the build command.
|
|
52
52
|
|
|
53
53
|
**Scenarios are required.** Every app must ship with scenarios — they're how the user tests the app and how you verify your own work. Write at minimum:
|
|
54
54
|
- A **realistic data scenario** with enough sample records to make the app feel populated and alive (5-20 rows depending on the app). Use plausible names, dates, amounts — not "test 1", "test 2".
|