You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/daemon/src/prompts/discovery.ts
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -285,7 +285,7 @@ Show something visible early, even if it is a wireframe with grey blocks and lab
285
285
Prefer the active design system's palette OR the chosen direction's palette. If extending, derive harmonious colors with \`oklch()\` instead of inventing hex. The background must be selected from the user's product domain, brand assets, screenshots, or chosen direction — never from generic app chrome or a default cozy canvas. For product utilities, marketplaces, dashboards, and SaaS, start from neutral or brand-colored foundations; do not fall back to warm beige / peach / pink / orange-brown Claude-style canvases just because no brand was provided. Pair a display face with a quieter body face — never let body and display be the same family (the only exception is "tech / utility" direction which is intentionally one family). One accent colour, used at most twice per screen.
286
286
287
287
### G. Slides + prototypes
288
-
Slides: follow the active deck directive or skill seed and tag slides with \`data-screen-label="01 Title"\`. Slide numbers are 1-indexed. Do not add a second navigation layer or place navigation inside the slide canvas; group any standalone navigation chrome in one \`data-deck-nav\` container outside the canvas so the host can hide it. Surface hierarchy: unless the user or active design system explicitly requires another surface program, choose one dominant light/dark surface from the brand or direction. Consecutive same-surface slides are valid. Use an inverse surface only for a named narrative role such as a chapter break, key reveal, proof point, or closing; never alternate by slide index or quota.
288
+
Slides: follow the active deck directive or skill seed and tag slides with \`data-screen-label="01 Title"\`. Slide numbers are 1-indexed. Open Design owns visible navigation: do not render controls, counters, dots, progress trackers, reset buttons, or keyboard hints in the artifact. Keep artifact navigation nonvisual with keyboard commands and click/tap on the left or right half of the canvas unless the brief explicitly requires another interaction. Surface hierarchy: unless the user or active design system explicitly requires another surface program, choose one dominant light/dark surface from the brand or direction. Consecutive same-surface slides are valid. Use an inverse surface only for a named narrative role such as a chapter break, key reveal, proof point, or closing; never alternate by slide index or quota.
289
289
Product prototypes: do **not** include floating Tweaks panels, platform/settings choosers, theme knobs, viewport toggles, or other designer/demo controls in the artifact. If variation controls are useful for internal iteration, keep them out of final product files unless the user explicitly asks for a design-system/spec dashboard.
290
290
291
291
### H. Cross-platform + multi-device layouts — use platform contracts and shared frames
Avoid \`type="module"\` on script imports — it breaks Babel transpilation.
84
84
85
85
## Decks (slide presentations)
86
-
For decks, follow the active deck directive or skill seed. Do not invent a second deck framework or place navigation inside the slide canvas. If standalone navigation chrome is needed, group it in one \`data-deck-nav\` container outside the slide canvas so Open Design can hide it when host navigation is present.
86
+
For decks, follow the active deck directive or skill seed. Open Design owns visible navigation: do not render controls, counters, dots, progress trackers, reset buttons, or keyboard hints in the artifact. Keep artifact navigation nonvisual with keyboard commands and click/tap on the left or right half of the canvas unless the brief explicitly requires another interaction.
87
87
88
88
Tag each slide with \`data-screen-label="01 Title"\` etc. so the user can reference them. Slide numbers are **1-indexed**.
0 commit comments