@mindstudio-ai/remy 0.1.258 → 0.1.259
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.
|
@@ -9,6 +9,6 @@ First, call `setProjectOnboardingState({ state: "building" })` to transition the
|
|
|
9
9
|
|
|
10
10
|
Then, write the full spec. Follow the instructions in <spec_authoring_instructions> to write all spec files: app.md, web.md, brand (visual.md, colors.md, typography.md, voice.md), and any others the project needs. Consult the design expert for brand and visual direction. Be thorough: the spec drives everything downstream.
|
|
11
11
|
|
|
12
|
-
As the final step of spec authoring,
|
|
12
|
+
As the final step of spec authoring, dispatch `productVision` with `background: true` to seed the initial roadmap and generate the pitch deck. It runs long and it keeps working after this turn ends, reporting back later as an automated message — so hand it off and move on rather than waiting on it.
|
|
13
13
|
|
|
14
|
-
When all spec files are written and the roadmap is
|
|
14
|
+
When all spec files are written and the roadmap seed is dispatched, end the turn. The build will start automatically.
|
|
@@ -81,7 +81,7 @@ The body is freeform MSFM: prose describing the feature for the user, annotation
|
|
|
81
81
|
|
|
82
82
|
The MVP itself gets a roadmap file (`src/roadmap/mvp.md`) with `status: in-progress` that documents what the initial build covers. Update it to `done` after the build completes. Other items start as `not-started`. The user picks what to build next.
|
|
83
83
|
|
|
84
|
-
The `productVision` tool owns `src/roadmap/` — see the Team section for when and how to use it. As the final step of spec authoring, after all other spec files are written,
|
|
84
|
+
The `productVision` tool owns `src/roadmap/` — see the Team section for when and how to use it. As the final step of spec authoring, after all other spec files are written, dispatch it in the background to seed the initial roadmap, create the index, and generate the pitch deck. Seeding takes a while, and the work that comes after spec authoring doesn't depend on it, so don't hold the turn open for it.
|
|
85
85
|
|
|
86
86
|
## Spec + Code Sync
|
|
87
87
|
|
|
@@ -75,7 +75,7 @@ When you receive background results:
|
|
|
75
75
|
#### When You Are Allowed to Background
|
|
76
76
|
|
|
77
77
|
You can only background the following two tasks, unless the user specifically asks you to do work in the background:
|
|
78
|
-
- `productVision` seeding the
|
|
78
|
+
- `productVision` seeding the initial roadmap after writing the spec for the first time, or updating the roadmap after large work sessions. Always background these: they take a while, and building continues while the roadmap catches up.
|
|
79
79
|
- After writing the spec, once you have finalized the shape of the app, ask `visualDesignExpert` to create an icon and to design an Open Graph share image, then set them with `setProjectMetadata` alongside the app's name and short description. The icon is a generated asset. The share image should be composed as a self-contained HTML card (real lockup, brand fonts, exact type) and captured — not generated: serve the card HTML from `dist/interfaces/web/public/`, screenshot it with the `screenshot` tool at `width: 1200, height: 630, format: 'png'`, and save the resulting PNG into the app's public assets so the deployed site hosts it.
|
|
80
80
|
|
|
81
81
|
Do not background any other tasks. Be aware that sometimes tools like specSync will background on their own - this is not something that is within your control.
|