stitch-kit 1.5.0

package/skills/stitch-loop/examples/next-prompt.md

@@ -0,0 +1,24 @@
+---
+page: contact
+---
+A warm, inviting contact page for Oakwood Furniture Co.
+
+**DESIGN SYSTEM (REQUIRED):**
+- Platform: Web, Desktop-first
+- Theme: Light, minimal, photography-first
+- Background: Warm barely-there cream (#FCFAFA)
+- Surface: Crisp very light gray (#F5F5F5) for cards
+- Primary Accent: Deep muted teal-navy (#294056) for buttons and links
+- Text Primary: Charcoal near-black (#2C2C2C) for headlines
+- Text Secondary: Soft warm gray (#6B6B6B) for body copy
+- Font: Modern sans-serif (Manrope or similar), clean and approachable
+- Buttons: Subtly rounded corners (8px), comfortable padding
+- Cards: Gently rounded corners (12px), whisper-soft shadows on hover
+- Layout: Centered content, max-width container, generous whitespace
+
+**Page Structure:**
+1. **Header:** Navigation with logo, Shop, Collections, About, Contact (active)
+2. **Hero Section:** Warm headline "Get in Touch" with a brief welcome message
+3. **Contact Form:** Name, email, message fields with the teal-navy submit button
+4. **Showroom Info:** Address, hours, and an embedded map or showroom photo
+5. **Footer:** Sustainability, Craftsmanship, Shipping links, and social icons

package/skills/stitch-loop/examples/usage.md

@@ -0,0 +1,77 @@
+# stitch-loop — Usage Examples
+
+## When to use
+
+- User wants to **iteratively build a multi-page site** with Stitch (e.g. marketing site, product pages).
+- You have or will create a `DESIGN.md` (via `stitch-design-md`) and a `SITE.md`.
+
+---
+
+## First-time setup
+
+1. Create or identify a Stitch project; save project ID to `stitch.json`.
+2. Generate `DESIGN.md` from an existing screen using `stitch-design-md`.
+3. Create `SITE.md` with vision, sitemap, roadmap, creative freedom (see `examples/SITE.md`).
+4. Create initial `next-prompt.md` with `page` frontmatter and full prompt including DESIGN SYSTEM block (see `examples/next-prompt.md`).
+
+---
+
+## Each iteration
+
+1. Read `next-prompt.md` → generate page with Stitch MCP → save to `queue/`.
+2. Move `queue/{page}.html` to `site/public/`; fix links and nav.
+3. Update `SITE.md` (sitemap, roadmap, creative freedom).
+4. Write next `next-prompt.md` so the next run continues the loop.
+
+---
+
+## Example 1: Furniture e-commerce site
+
+**User:** "Use Stitch to build my Oakwood Furniture site. I have DESIGN.md and SITE.md — run the loop until the roadmap is done."
+
+**Skill activates because:** User explicitly mentions "Stitch" and wants multi-page iterative building.
+
+**What the skill does:**
+1. Reads `SITE.md` → identifies next page in roadmap (`contact.html`)
+2. Reads `next-prompt.md` → uses it as the Stitch generation prompt
+3. Calls `stitch-mcp-generate-screen-from-text` with the assembled prompt
+4. Downloads HTML to `queue/contact.html` via `scripts/fetch-stitch.sh`
+5. Validates nav consistency, moves to `site/public/contact.html`
+6. Updates `SITE.md` — marks `contact.html` as `[x]`
+7. Writes next `next-prompt.md` for the next page in roadmap
+
+**Output:**
+```
+## Loop iteration complete: contact.html
+
+**Stitch Screen:** projects/13534454087919359824/screens/abc123
+**File:** site/public/contact.html
+
+### What was built
+Contact page with form, showroom info, and consistent nav.
+
+### SITE.md updated
+contact.html → [x] complete
+
+### Next iteration
+next-prompt.md → Product Detail Page
+Run stitch-loop again to continue.
+```
+
+---
+
+## Example 2: SaaS landing site (starting fresh)
+
+**User:** "Use Stitch to design and build a 5-page SaaS landing site for my project management tool."
+
+**What the skill does:**
+1. Creates a new Stitch project
+2. Generates the homepage design
+3. Calls `stitch-design-md` → extracts `DESIGN.md` with the visual system
+4. Creates `SITE.md` with 5-page roadmap
+5. Runs loop iterations for each page, maintaining visual consistency via `DESIGN.md` Section 6 in every prompt
+
+**Tips:**
+- Always include the full DESIGN SYSTEM block from `DESIGN.md` Section 6 in every `next-prompt.md`
+- The `page:` frontmatter is used for file naming (e.g., `page: pricing` → `pricing.html`)
+- `stitch.json` persists the project ID between sessions so you don't lose track

package/skills/stitch-mcp-apply-design-system/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: stitch-mcp-apply-design-system
+description: Applies a Stitch Design System to existing screens — updates their colors, fonts, and roundness to match the design system's theme. Requires an assetId from list or create operations.
+allowed-tools:
+  - "stitch*:*"
+---
+
+# Stitch MCP — Apply Design System
+
+Applies a previously created Stitch Design System to one or more screens. This updates the screen's visual theme (colors, font, roundness) to match the design system, ensuring visual consistency across a project.
+
+## Critical prerequisite
+
+**Only use this skill when the user explicitly mentions "Stitch".**
+
+You must have:
+1. A `projectId` (numeric)
+2. One or more `screenId` values (numeric)
+3. An `assetId` from a design system (from `list_design_systems` or `create_design_system`)
+
+## When to use
+
+- After creating a design system and wanting to apply it to screens
+- User says "make all screens match this theme" or "apply the design system"
+- The orchestrator's Step 5b stores an assetId and offers to apply it
+- Ensuring visual consistency across a multi-screen project
+
+## Call the MCP tool
+
+```json
+{
+  "name": "apply_design_system",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "selectedScreenIds": ["88805abc123def456", "99906xyz789ghi012"],
+    "assetId": "ds_abc123"
+  }
+}
+```
+
+## Parameter reference
+
+### `projectId` — numeric ID only, no prefix
+
+```
+✅ "3780309359108792857"
+❌ "projects/3780309359108792857"
+```
+
+### `selectedScreenIds` — array of numeric screen IDs
+
+```
+✅ ["88805abc123def456"]
+❌ ["projects/123/screens/88805abc123def456"]
+```
+
+All selected screens will have the design system applied.
+
+### `assetId` — the design system identifier
+
+The `name` field from a design system asset, or just the ID portion:
+
+```
+✅ "ds_abc123"
+```
+
+Get this from:
+- `stitch-mcp-list-design-systems` → extract from the `name` field of each asset
+- `stitch-mcp-create-design-system` → returned in the response `name` field
+
+## Output
+
+Returns updated screen data reflecting the applied design system.
+
+## After applying
+
+1. Re-fetch affected screens: `stitch-mcp-get-screen` for each screenId
+2. Show updated screenshots to the user
+3. Offer:
+   - "Edit the updated screens?" → `stitch-mcp-edit-screens`
+   - "Convert to code?" → framework conversion
+   - "Apply to more screens?" → another `apply_design_system` call

package/skills/stitch-mcp-create-design-system/SKILL.md

@@ -0,0 +1,117 @@
+---
+name: stitch-mcp-create-design-system
+description: Creates a reusable Stitch Design System from theme tokens — colors, fonts, roundness, saturation. Can be applied to future screens for visual consistency.
+allowed-tools:
+  - "stitch*:*"
+---
+
+# Stitch MCP — Create Design System
+
+Creates a new Stitch Design System — a reusable theme configuration that can be applied to any screen. This bridges the gap between local CSS token extraction (via `stitch-design-system`) and Stitch-native design tokens that persist across generations.
+
+## Critical prerequisite
+
+**Only use this skill when the user explicitly mentions "Stitch".**
+
+## When to use
+
+- After extracting CSS tokens via `stitch-design-system` and wanting to persist them in Stitch
+- User wants consistent theming across multiple screens or projects
+- The orchestrator's Step 7 offers to create a Stitch Design System from extracted tokens
+- User explicitly asks to create a design system in Stitch
+
+## Call the MCP tool
+
+```json
+{
+  "name": "create_design_system",
+  "arguments": {
+    "designSystem": {
+      "displayName": "SaaS Dashboard Theme",
+      "theme": {
+        "colorMode": "LIGHT",
+        "font": "DM_SANS",
+        "roundness": "ROUND_EIGHT",
+        "saturation": 3,
+        "customColor": "#6366F1",
+        "backgroundLight": "#FFFFFF",
+        "backgroundDark": "#18181B",
+        "description": "Professional SaaS aesthetic — clean, indigo accent, airy spacing"
+      },
+      "designTokens": "--color-primary: #6366F1;\n--color-bg: #FFFFFF;\n--font-family: 'DM Sans';",
+      "styleGuidelines": "Use indigo for interactive elements. Gray-50 backgrounds for cards. 8px border radius."
+    },
+    "projectId": "3780309359108792857"
+  }
+}
+```
+
+## Parameter reference
+
+### `designSystem` — required object
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| `displayName` | string | Yes | Human-readable name for the design system |
+| `theme` | DesignTheme | Yes | Visual configuration — see below |
+| `designTokens` | string | No | CSS custom properties or token definitions |
+| `styleGuidelines` | string | No | Natural-language design rules |
+
+### `theme` (DesignTheme) — the visual configuration
+
+| Field | Type | Values | Description |
+|-------|------|--------|-------------|
+| `colorMode` | enum | `LIGHT`, `DARK` | Base appearance mode |
+| `font` | enum | See font list below | Primary typeface |
+| `roundness` | enum | `ROUND_FOUR`, `ROUND_EIGHT`, `ROUND_TWELVE`, `ROUND_FULL` | Border radius scale |
+| `saturation` | int | 1–4 | Color vibrancy (1 = muted, 4 = vivid) |
+| `customColor` | string | Hex color | Primary brand color |
+| `backgroundLight` | string | Hex color | Light mode background |
+| `backgroundDark` | string | Hex color | Dark mode background |
+| `preset` | string | — | Optional preset theme name |
+| `description` | string | — | Brief aesthetic description |
+
+### Available fonts (28 options)
+
+**Sans-serif:** `INTER`, `DM_SANS`, `GEIST`, `SORA`, `MANROPE`, `RUBIK`, `MONTSERRAT`, `WORK_SANS`, `SPACE_GROTESK`, `PLUS_JAKARTA_SANS`, `PUBLIC_SANS`, `SOURCE_SANS_THREE`, `NUNITO_SANS`, `ARIMO`, `HANKEN_GROTESK`, `IBM_PLEX_SANS`, `SPLINE_SANS`, `LEXEND`, `EPILOGUE`, `BE_VIETNAM_PRO`, `METROPOLIS`
+
+**Serif:** `NOTO_SERIF`, `NEWSREADER`, `DOMINE`, `LIBRE_CASLON_TEXT`, `EB_GARAMOND`, `LITERATA`, `SOURCE_SERIF_FOUR`
+
+### `projectId` — optional, numeric only
+
+```
+✅ "3780309359108792857"
+❌ "projects/3780309359108792857"
+```
+
+If provided, associates the design system with a specific project. If omitted, creates a global design system.
+
+## Mapping CSS tokens to DesignTheme
+
+When creating from extracted `design-tokens.css`:
+
+| CSS Variable | → DesignTheme field |
+|---|---|
+| `--color-primary` | `customColor` |
+| `--color-bg` or `--bg-light` | `backgroundLight` |
+| `--bg-dark` | `backgroundDark` |
+| `--font-family` | `font` (map to closest enum value) |
+| `--radius` or `--border-radius` | `roundness` (4px→FOUR, 8px→EIGHT, 12px→TWELVE, 16px+→FULL) |
+
+## Output
+
+Returns an Asset object with a `name` field — **store this** for future `update_design_system` and `apply_design_system` calls:
+
+```json
+{
+  "name": "assets/ds_abc123",
+  "displayName": "SaaS Dashboard Theme",
+  "designSystem": { ... }
+}
+```
+
+## After creating
+
+- Store the `name` value (e.g., `assets/ds_abc123`) — you'll need it for apply/update
+- Offer: "Apply this design system to existing screens?" → `stitch-mcp-apply-design-system`
+- The orchestrator stores this for automatic application in Step 5b

package/skills/stitch-mcp-create-project/SKILL.md

@@ -0,0 +1,77 @@
+---
+name: stitch-mcp-create-project
+description: Creates a new Stitch project container (a design workspace). Call this when starting a new design session to get a projectId for screen generation.
+allowed-tools:
+  - "stitch*:*"
+---
+
+# Stitch MCP — Create Project
+
+Creates a new Stitch project. A project is a container that holds one or more generated screens. You need a projectId before you can call `generate_screen_from_text`.
+
+## Critical prerequisite
+
+**Only use this skill when the user explicitly mentions "Stitch"** in their request. Never trigger Stitch operations silently during regular conversation.
+
+## When to use
+
+- Starting a new design task or app concept
+- The user says "create a Stitch project", "start a new project in Stitch", "design X using Stitch"
+- You need a `projectId` before calling `generate_screen_from_text`
+- Starting work in a new domain (keep related screens in one project)
+
+## Step 1: Extract a meaningful title
+
+Infer a descriptive project title from the user's request:
+
+| User says | → title |
+|-----------|---------|
+| "Design a pet adoption app" | `"PawPals"` or `"Pet Adoption App"` |
+| "Make a login page" | `"Login Page"` |
+| "SaaS dashboard for analytics" | `"Analytics Dashboard"` |
+| "E-commerce product listing" | `"Product Listing"` |
+
+If no clear name is evident, use a descriptive label: `"Design Project [date]"`.
+
+## Step 2: Call the MCP tool
+
+```json
+{
+  "name": "create_project",
+  "arguments": {
+    "title": "[Descriptive project title]"
+  }
+}
+```
+
+## Step 3: Extract and store the project ID — CRITICAL
+
+The tool returns a `name` field in the format `projects/NUMERIC_ID`. You must extract the numeric portion:
+
+**Tool response:**
+```json
+{
+  "name": "projects/3780309359108792857",
+  "title": "Analytics Dashboard"
+}
+```
+
+**Extract:**
+- **Full name:** `projects/3780309359108792857` → use for `list_screens`, `get_project`
+- **Numeric ID:** `3780309359108792857` → use for `generate_screen_from_text`, `get_screen`
+
+Store both values. Announce to the user:
+> "Created project **'Analytics Dashboard'** (ID: `3780309359108792857`). Ready to generate screens."
+
+## ID format rules (critical — different tools need different formats)
+
+| Tool | ID format required |
+|------|-------------------|
+| `generate_screen_from_text` | Numeric only: `3780309359108792857` |
+| `get_screen` | Numeric only: `3780309359108792857` |
+| `list_screens` | Full path: `projects/3780309359108792857` |
+| `get_project` | Full path: `projects/3780309359108792857` |
+
+## Integration
+
+After creating a project, the next step is always `stitch-mcp-generate-screen-from-text` to generate the first screen.

package/skills/stitch-mcp-delete-project/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: stitch-mcp-delete-project
+description: Permanently deletes a Stitch project and all its screens. Destructive — requires explicit user confirmation before calling.
+allowed-tools:
+  - "stitch*:*"
+---
+
+# Stitch MCP — Delete Project
+
+Permanently deletes a Stitch project and all its screens, designs, and history. This action is irreversible.
+
+## Critical prerequisite
+
+**Only use this skill when the user explicitly mentions "Stitch".**
+
+**This is a destructive action.** You MUST ask the user to confirm before calling `delete_project`. Never auto-delete.
+
+## When to use
+
+- User explicitly asks to delete a Stitch project
+- Cleaning up test/scratch projects after confirming with the user
+- The orchestrator offers project cleanup and the user accepts
+
+## Step 1: Confirm the project
+
+Show the user what they're about to delete:
+
+1. Call `stitch-mcp-get-project` with `projects/[ID]` to get the project title and screen count
+2. Present: "You're about to permanently delete **[title]** ([N] screens). This cannot be undone. Proceed?"
+3. Only continue if the user explicitly confirms
+
+## Step 2: Call the MCP tool
+
+```json
+{
+  "name": "delete_project",
+  "arguments": {
+    "name": "projects/3780309359108792857"
+  }
+}
+```
+
+### `name` — full path with `projects/` prefix
+
+```
+✅ "projects/3780309359108792857"
+❌ "3780309359108792857"
+```
+
+This follows the same format as `get_project` — both use `projects/ID`.
+
+## After deleting
+
+- Confirm: "Project **[title]** has been deleted."
+- Offer: "Want to see your remaining projects?" → `stitch-mcp-list-projects`
+- Do NOT attempt to access the deleted project's screens or data
+
+## Anti-patterns
+
+- **Never delete without explicit user confirmation** — even if the orchestrator suggests cleanup
+- **Never delete multiple projects in a batch** without confirming each one
+- **Never use numeric ID** — `delete_project` requires the full `projects/ID` path

package/skills/stitch-mcp-edit-screens/SKILL.md

@@ -0,0 +1,121 @@
+---
+name: stitch-mcp-edit-screens
+description: Edits existing Stitch screens with text prompts — the iteration tool. Change colors, layout, content, or style without regenerating from scratch. Supports refinement loops via output_components suggestions.
+allowed-tools:
+  - "stitch*:*"
+  - "Bash"
+  - "Read"
+  - "Write"
+---
+
+# Stitch MCP — Edit Screens
+
+Edits one or more existing screens using a text prompt. This is the primary iteration tool — instead of regenerating a screen from scratch (60–180s), you can refine what you already have with targeted changes.
+
+## Critical prerequisite
+
+**Only use this skill when the user explicitly mentions "Stitch".**
+
+You must have both a `projectId` AND at least one `screenId` before calling this. If you don't:
+- List screens via `stitch-mcp-list-screens` to find screen IDs
+- Parse from context: `projects/123/screens/456` → projectId: `123`, screenId: `456`
+
+## When to use
+
+- User wants to modify an existing Stitch screen (change colors, layout, content, style)
+- After generation, user says "make it darker", "change the font", "move the nav to the side"
+- The orchestrator's Step 5b offers "Edit this screen"
+- Any iterative refinement on a Stitch design
+
+## Call the MCP tool
+
+```json
+{
+  "name": "edit_screens",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "selectedScreenIds": ["88805abc123def456"],
+    "prompt": "Change the background to dark mode (#09090B). Make the primary color indigo (#818CF8). Increase the font size of the header to 32px bold.",
+    "deviceType": "DESKTOP",
+    "modelId": "GEMINI_3_PRO"
+  }
+}
+```
+
+## Parameter reference
+
+### `projectId` — numeric ID only, no prefix
+
+```
+✅ "3780309359108792857"
+❌ "projects/3780309359108792857"
+```
+
+### `selectedScreenIds` — array of numeric screen IDs
+
+```
+✅ ["88805abc123def456"]
+❌ ["projects/123/screens/88805abc123def456"]
+❌ ["screens/88805abc123def456"]
+```
+
+Select one or more screens to edit. All selected screens receive the same edit instruction.
+
+### `prompt` — the edit instruction
+
+Apply the same quality bar as generation prompts:
+- Be specific: "Change background to #09090B" not "make it darker"
+- Name exact components: "the header navigation" not "the top part"
+- Include values: hex colors, px sizes, specific content text
+- One focused change per call produces better results than many changes at once
+
+### `deviceType` — optional
+
+Same enum as `generate_screen_from_text`: `MOBILE`, `DESKTOP`, `TABLET`, `AGNOSTIC`
+
+### `modelId` — optional
+
+| Value | Use when |
+|-------|---------|
+| `GEMINI_3_PRO` | Complex edits — layout changes, multi-component updates |
+| `GEMINI_3_FLASH` | Simple edits — color swaps, text changes, quick iterations |
+
+## Handling `output_components`
+
+The response may contain `output_components` with suggestions:
+
+```json
+{
+  "outputComponents": [
+    { "text": "I've updated the background color and adjusted contrast ratios." },
+    { "suggestion": "Would you also like me to update the sidebar to match the dark theme?" }
+  ]
+}
+```
+
+**When you see suggestions:**
+1. Present them to the user
+2. If the user accepts: call `edit_screens` again with the suggestion as the new `prompt`
+3. This creates a natural refinement loop — keep going until the user is satisfied
+
+## Timing
+
+Same as generation: 60–180 seconds is normal.
+- Do NOT retry during this window
+- Do NOT assume failure if it takes > 60 seconds
+- Each call creates a new edit — retries mean duplicate edits
+
+## After editing
+
+1. Re-fetch the screen: `stitch-mcp-get-screen` with the same projectId and screenId
+2. Show the updated screenshot to the user
+3. Offer:
+   - "Continue editing?" → another `edit_screens` call
+   - "Generate variants of this version?" → `stitch-mcp-generate-variants`
+   - "Convert to code?" → framework conversion workflow
+
+## Anti-patterns
+
+- **Never send vague edit prompts** — "make it better" will produce unpredictable results
+- **Never use `projects/ID` format** for projectId or screenId — both must be numeric
+- **Never batch unrelated edits** — "change the color AND completely redo the layout" works poorly

package/skills/stitch-mcp-generate-screen-from-text/SKILL.md

@@ -0,0 +1,102 @@
+---
+name: stitch-mcp-generate-screen-from-text
+description: Generates a high-fidelity UI screen or wireframe from a text prompt using Stitch. This is the core text-to-UI generation tool — the heart of the Stitch workflow.
+allowed-tools:
+  - "stitch*:*"
+---
+
+# Stitch MCP — Generate Screen from Text
+
+Generates a UI design screen from a structured text prompt. This is the central action in any Stitch workflow — everything before it (spec generation, prompt assembly) is preparation, and everything after it (screen retrieval, code conversion) is follow-through.
+
+## Critical prerequisite
+
+**Only use this skill when the user explicitly mentions "Stitch".**
+
+You must have a `projectId` before calling this. If you don't have one:
+- Create a new project via `stitch-mcp-create-project`
+- Or find an existing project via `stitch-mcp-list-projects`
+
+## When to use
+
+- User asks to "design", "generate", "create", or "make" a screen using Stitch
+- The orchestrator has assembled a prompt via `stitch-ui-prompt-architect`
+- User provides specific visual requirements and wants a Stitch-generated result
+
+## Call the MCP tool
+
+```json
+{
+  "name": "generate_screen_from_text",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "prompt": "[Full structured prompt — see below]",
+    "deviceType": "MOBILE",
+    "modelId": "GEMINI_3_PRO"
+  }
+}
+```
+
+## Parameter reference
+
+### `projectId` — numeric ID only, no `projects/` prefix
+```
+✅ "3780309359108792857"
+❌ "projects/3780309359108792857"
+```
+
+### `prompt` — use the `[Context] [Layout] [Components]` structure
+```
+[Context & Style]
+[Device] [Mode] [screen type] for [product]. [aesthetic]. [theme]. [colors]. [font].
+
+[Layout]
+[Describe the structural arrangement]
+
+[Components]
+[Specific named UI components with details]
+```
+
+For best results, use the `stitch-ui-prompt-architect` skill to assemble the prompt before calling this tool.
+
+### `deviceType`
+| Value | Use when |
+|-------|---------|
+| `MOBILE` | Mobile app, phone-sized UI (default if uncertain) |
+| `DESKTOP` | Web dashboard, landing page, SaaS UI |
+| `TABLET` | Tablet-specific layout |
+| `AGNOSTIC` | Not tied to a specific device — responsive/fluid layout |
+
+### `modelId`
+| Value | Use when |
+|-------|---------|
+| `GEMINI_3_PRO` | **Recommended** — high-fidelity, complex layouts, production quality |
+| `GEMINI_3_FLASH` | Wireframes, rapid iteration, when speed matters more than quality |
+
+## After generating
+
+This tool returns session info but **not the actual screenshot/HTML**. To retrieve the design:
+1. Call `stitch-mcp-list-screens` with `projects/[projectId]` to find the new screen
+2. Call `stitch-mcp-get-screen` with the `projectId` and `screenId` to get the screenshot and HTML
+
+## Prompt quality checklist
+
+Before calling this tool, verify the prompt:
+- [ ] Specifies device type consistently with `deviceType` parameter
+- [ ] Names specific components (not "some buttons" — "primary 'Sign In' button")
+- [ ] Includes colors (hex codes or clear color names)
+- [ ] Uses realistic content (not Lorem Ipsum)
+- [ ] Specifies light or dark mode explicitly
+
+## Timing
+
+Stitch generation takes 60–180 seconds. This is normal behavior, not a timeout.
+- Do NOT retry during this window
+- Do NOT assume failure if it takes > 60 seconds
+- If it fails: wait 60 seconds, retry ONCE max
+- Each call creates a new generation — retries mean duplicate screens
+
+## References
+
+- `examples/desktop.md` — Desktop dashboard prompts (SaaS analytics, admin panel)
+- `examples/mobile.md` — Mobile app prompts (login, social feed, e-commerce)