owndesign 0.1.8 → 0.1.9

package/dist/index.js

@@ -15,7 +15,7 @@ async function main(argv) {
     return;
   }
   if (options === "version") {
-    console.log("0.1.8");
+    console.log("0.1.9");
     return;
   }
   const cliRoot = path.dirname(fileURLToPath(import.meta.url));

package/dist/server/index.js

@@ -57383,25 +57383,15 @@ function buildToolWorkflowPrompt() {
     "Choose tools by intent:",
     "- Use `createHtml` only to create a missing `index.html` file.",
     "- Use `edit` for small, focused replacements in one existing file.",
-    "- Use `patch` for coordinated changes, repeated replacements, or multi-file edits.",
-    "- Use `write` only for deliberate full-file replacement or non-preview support files.",
+    "- Use `patch` for coordinated changes or repeated replacements.",
+    "- Use `write` only for deliberate full-file replacement of `index.html`.",
     "- Do not use `write` to create the initial `index.html`; use `createHtml` first.",
     "- Use `copyFile` only when the current user message explicitly asks you to duplicate an existing file.",
     "- Use `delete` only after confirming the file is not referenced.",
     "",
-    "For Single HTML creation:",
-    '- Call `createHtml({ path: "index.html" })` when `index.html` is missing.',
-    "- After `createHtml`, read `index.html`.",
-    "- Replace the default placeholder markup, CSS, and script with a complete designed prototype.",
-    "",
-    "For Single HTML updates:",
-    "- If `index.html` exists, read it before editing and do not call `createHtml`.",
-    "- Keep visible page structure, styling, and local interactions in `index.html`.",
-    "- Use internal views for multi-screen workflows instead of additional HTML files.",
-    "",
-    "After page changes:",
-    "- Use `previewRefresh` when the current preview page changed and should reload.",
-    "- Call exactly one `previewRefresh` after successful previewable changes.",
+    "Single HTML create vs update flow:",
+    '- When `index.html` is missing, call `createHtml({ path: "index.html" })`, then read it and replace the default placeholder markup, CSS, and script with a complete designed prototype.',
+    "- When `index.html` exists, read it before editing and do not call `createHtml`.",
     "",
     "Recover from tool failures:",
     "- If an edit fails, read the file again and retry with a smaller edit or patch.",

package/dist/server/prompts/agents/design-page.md

@@ -19,7 +19,7 @@ Before editing, make the design decision first:
 1. Identify the interface purpose, target user, primary task, and product tone.
 2. Choose one clear visual direction that fits the domain and makes the page memorable.
 3. Plan the first viewport, key workflow, primary actions, supporting content, and interaction states.
-4. Plan the mobile structure as a real responsive layout, not as a device mockup.
+4. When the product needs mobile support, plan the mobile structure as a real responsive layout, not as a device mockup.
 5. Then implement the design in `index.html`.
 
 Prefer finishing the visible page over maintaining abstractions. One coherent single file is the intended architecture.
@@ -42,7 +42,7 @@ Every rendered `index.html` should feel like a complete product-quality prototyp
 - Use CSS variables or clear repeated values for the page's color, spacing, radius, shadow, and motion system.
 - Build realistic labels, concise content, minimal mock data, and useful interface states. Avoid lorem ipsum, vague placeholder copy, and empty marketing filler.
 - Make common workflows visible and understandable, including relevant hover, focus, active, selected, empty, loading, or error states.
-- Design responsive layouts for desktop and mobile; mobile should reorganize navigation, actions, and dense content instead of only shrinking columns.
+- Adapt to mobile when the interface calls for it (for example consumer-facing or touch-first products); when you do, reorganize navigation, actions, and dense content for small screens instead of only shrinking columns. Desktop-only tools do not need a mobile layout.
 - For mobile interfaces, design the real app/page layout only. Do not add simulated system status bars, notches, home indicators, phone frames, device chrome, browser chrome, or screenshot containers unless the user explicitly asks for a device mockup or app-store-style screenshot.
 - Keep text readable and prevent overflow, clipping, and accidental overlap.
 - Prefer polished, domain-specific UI over generic sections.
@@ -95,15 +95,19 @@ Forms may validate required fields, show error/success states, and update local
 
 ## Resource Rules
 
-The default `index.html` template already configures the Inter and Noto Sans SC web fonts on the `html` element. Unless the user explicitly asks for a different typeface, do not change `font-family`; design typography through size, weight, line-height, spacing, and hierarchy instead.
+Fonts, icons, and external dependencies follow the `resource_policy` section provided with these instructions. In short: keep the configured fonts and design typography through size, weight, line-height, spacing, and hierarchy; use the configured icon set (Lucide by default) rather than other icon systems or emoji; and keep external dependencies minimal and purposeful. Prefer code that works directly when `index.html` is loaded by the Preview Pane.
 
-Lucide icons are already configured by the default template. Use Lucide icon elements with the syntax `<i data-lucide="menu"></i>` and choose the icon name that matches the UI action. Do not use other icon systems, inline SVG icons, emoji icons, or decorative emoji as UI icons.
+## Pre-Output Checklist
 
-When styling Lucide icons, do not target `i`, `i[data-lucide]`, or tag selectors. Lucide replaces `<i data-lucide="..."></i>` with inline `<svg>` elements. Give the icon a semantic class or wrap it in a classed element, then style the class and its child `svg`, such as `.nav-icon svg { width: 18px; height: 18px; stroke-width: 2; }`.
+Before calling `previewRefresh`, re-read the rendered `index.html` and verify every item below. If any item fails, fix it first; do not refresh on a page that fails the checklist.
 
-If JavaScript dynamically inserts markup that contains Lucide placeholders, call `lucide.createIcons()` after updating the DOM.
-
-Use local CSS and configured assets first. Keep external dependencies minimal and purposeful; add an extra external resource only when the user explicitly requests it or when it is necessary for the prototype quality. Prefer code that works directly when `index.html` is loaded by the Preview Pane.
+- First viewport: at least one clear primary action or workflow entry point is visible without scrolling.
+- Readability: body text is at least 14px and has enough contrast against its background to read comfortably; no low-contrast gray-on-gray text.
+- Design tokens: every color, spacing, radius, and shadow value comes from a CSS variable or a consistent repeated value, with no one-off magic numbers.
+- Icons: each Lucide icon is vertically centered with its adjacent text or control.
+- No dead ends: every nav item, filter, tab, button, modal, and drawer produces a visible response; there are no placeholder sections, unfinished scripts, or controls that do nothing.
+- States: interactive elements show the relevant hover, focus, active, or selected states.
+- Content: labels and copy are specific to the product domain, with no lorem ipsum or vague placeholder text.
 
 ## Final Reply
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "owndesign",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "private": false,
   "bin": {
     "owndesign": "./dist/index.js"