stitch-kit 1.5.0

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

@@ -0,0 +1,53 @@
+# Desktop Screen Generation Examples
+
+## 1. SaaS Analytics Dashboard
+
+**User request:** "Build a dashboard showing revenue and user growth."
+
+```json
+{
+  "name": "generate_screen_from_text",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "prompt": "Desktop High-Fidelity analytics dashboard for a SaaS platform. Enterprise clean aesthetic. Light mode. Background: White (#ffffff). Primary: Indigo (#6366F1). Font: DM Sans.\n\nLeft sidebar navigation (200px): Logo top-left, nav items with icons (Overview, Projects, Reports, Settings), user avatar and name at bottom. Top bar: 'Analytics Overview' title, date range picker, 'Export' button.\n\nKPI row: 4 metric cards — Total Revenue ($142,800, +12% MoM), Active Users (8,420, +5%), Churn Rate (2.1%, -0.3%), Avg Session (4m 32s). Main chart: 'Monthly Recurring Revenue' line chart, last 12 months, indigo line with subtle fill. Bottom split: 'Top Performing Plans' bar chart left, 'Recent Signups' table right.",
+    "deviceType": "DESKTOP",
+    "modelId": "GEMINI_3_PRO"
+  }
+}
+```
+
+---
+
+## 2. Admin Panel (Dark Mode)
+
+**User request:** "Dark mode admin panel for server monitoring."
+
+```json
+{
+  "name": "generate_screen_from_text",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "prompt": "Desktop High-Fidelity admin console for server monitoring. Developer aesthetic. Dark mode. Background: Zinc-900 (#18181B). Primary: Emerald (#10B981). Font: IBM Plex Mono.\n\nDense information layout. Top bar: 'System Status' title, 'All Systems Operational' badge in green. Main grid: 6 server status cards in 3-column grid — each card shows Server name, CPU gauge (%), Memory gauge (%), Uptime, Status indicator (green/red dot). Bottom panel: Terminal-style log stream with color-coded severity (ERROR in red, WARN in yellow, INFO in emerald).",
+    "deviceType": "DESKTOP",
+    "modelId": "GEMINI_3_PRO"
+  }
+}
+```
+
+---
+
+## 3. SaaS Landing Page
+
+**User request:** "Landing page for a project management tool."
+
+```json
+{
+  "name": "generate_screen_from_text",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "prompt": "Desktop High-Fidelity landing page for 'Taskflow', a project management SaaS. Clean minimalist aesthetic. Light mode. Background: White (#ffffff). Primary: Violet (#7C3AED). Font: Inter.\n\nSticky top nav: Logo left, links center (Features, Pricing, Blog, Docs), 'Sign in' ghost button and 'Start free' primary button right. Hero: Large headline 'Ship projects faster, together', subtext 'The only PM tool your team will actually use', two CTA buttons ('Get started free' primary, 'See demo' ghost), hero mockup screenshot of dashboard. Features section: 3-column grid of feature cards with icon, title, description. Social proof: Logos row of known companies.",
+    "deviceType": "DESKTOP",
+    "modelId": "GEMINI_3_PRO"
+  }
+}
+```

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

@@ -0,0 +1,71 @@
+# Mobile App Screen Generation Examples
+
+## 1. Login Screen (Cyberpunk Style)
+
+**User request:** "Cyberpunk login page for a mobile game."
+
+```json
+{
+  "name": "generate_screen_from_text",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "prompt": "Mobile High-Fidelity login screen for a cyberpunk game 'NetRunner'. Neon aesthetic. Dark mode. Background: Deep black (#050505). Primary: Neon blue (#00D9FF). Font: Orbitron.\n\nCenter-aligned vertical stack. Header: Glitch-effect 'NETRUNNER' logo with horizontal scan-line overlay. Form: 'NetID' input field with neon blue glowing border, 'Passcode' input with eye-toggle icon, neon pink glow on focus. Primary CTA: Full-width 'JACK IN' button with animated neon border. Divider: 'OR CONNECT VIA' with subtle lines. OAuth row: Ghost buttons for Google and Discord. Footer: 'New agent? Register your ID' link in muted cyan.",
+    "deviceType": "MOBILE",
+    "modelId": "GEMINI_3_PRO"
+  }
+}
+```
+
+---
+
+## 2. Social Media Feed
+
+**User request:** "Instagram-style home feed."
+
+```json
+{
+  "name": "generate_screen_from_text",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "prompt": "Mobile High-Fidelity home feed for a photo-sharing social app. Clean minimalist aesthetic. Light mode. Background: White (#ffffff). Primary: Pink (#EC4899). Font: Inter.\n\nTop bar: App logo left, search icon + DM icon right. Stories bar: Horizontal scroll of circular avatars with gradient rings — 'Your story' first, then Emma, Jake, Sophia, Carlos. Feed: Full-width post cards — user avatar + name + timestamp header, full-width photo, action bar (heart, comment, share, bookmark icons), like count 'Liked by Anna and 842 others', caption with 'more' link. Bottom nav: Home (active), Search, Reels, Shop, Profile icons.",
+    "deviceType": "MOBILE",
+    "modelId": "GEMINI_3_FLASH"
+  }
+}
+```
+
+---
+
+## 3. E-commerce Product Detail
+
+**User request:** "Product detail page for a sneaker store."
+
+```json
+{
+  "name": "generate_screen_from_text",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "prompt": "Mobile High-Fidelity product detail screen for a premium sneaker store. Streetwear aesthetic. Light mode. Background: White (#ffffff). Primary: Black (#18181B). Font: Space Grotesk.\n\nTop: Back arrow + share icon. Hero: Full-width image carousel showing 'Air Max 90 OG' sneaker from multiple angles, dot indicators. Info section: Brand tag 'Nike', product name 'Air Max 90 OG White/Infrared', price '$140', 5-star rating '(1,247 reviews)'. Size selector: Row of size chips (US 7, 8, 9, 10, 11, 12) — 9 highlighted as selected, 7 greyed out (unavailable). Color options: 3 circular swatches. Description: Short collapsible text. Sticky bottom bar: 'Add to Cart' full-width black button, heart icon (save) to its left.",
+    "deviceType": "MOBILE",
+    "modelId": "GEMINI_3_PRO"
+  }
+}
+```
+
+---
+
+## 4. Fitness Tracker Home
+
+**User request:** "Home screen for a fitness app."
+
+```json
+{
+  "name": "generate_screen_from_text",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "prompt": "Mobile High-Fidelity home screen for a fitness tracking app 'FlexOS'. Dark athletic aesthetic. Dark mode. Background: Zinc-900 (#18181B). Primary: Neon green (#22C55E). Font: DM Sans.\n\nTop: Greeting 'Good morning, Alex 👋', date subtitle. Today's goal ring: Large circular progress ring (67% complete), center shows '2,847 / 4,200 cal'. Quick stats row: 3 cards — Steps 8,432, Active Minutes 52, Water 6/8 cups. Workout recommendations: Horizontal scroll of workout cards — gradient thumbnail, workout name, duration, difficulty badge. Recent activity: List of today's logged exercises with icon, name, duration, calories. Bottom nav: Home (active), Workout, Nutrition, Progress, Profile.",
+    "deviceType": "MOBILE",
+    "modelId": "GEMINI_3_PRO"
+  }
+}
+```

package/skills/stitch-mcp-generate-variants/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: stitch-mcp-generate-variants
+description: Generates design variants of existing Stitch screens using the native variant API. Explore alternative layouts, color schemes, fonts, or content with configurable creativity levels.
+allowed-tools:
+  - "stitch*:*"
+---
+
+# Stitch MCP — Generate Variants
+
+Generates alternative versions of existing screens using Stitch's native variant generation API. This is more efficient than the text-prompt approach (1 API call vs. 3) and offers fine-grained control over what aspects to vary.
+
+## Critical prerequisite
+
+**Only use this skill when the user explicitly mentions "Stitch".**
+
+You must have both a `projectId` AND at least one `screenId` of an existing screen. Variants are always based on an existing design — you can't generate variants from scratch.
+
+## When to use
+
+- User wants to explore alternative versions of an existing screen
+- After generation, user says "show me some variations" or "try different styles"
+- The orchestrator's Step 5b offers "Generate variants"
+- A/B testing — creating multiple options for stakeholder review
+
+## Call the MCP tool
+
+```json
+{
+  "name": "generate_variants",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "selectedScreenIds": ["88805abc123def456"],
+    "prompt": "Explore different color schemes while keeping the layout structure",
+    "variantOptions": {
+      "variantCount": 3,
+      "creativeRange": "EXPLORE",
+      "aspects": ["COLOR_SCHEME", "IMAGES"]
+    },
+    "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"]
+```
+
+The source screen(s) to generate variants from.
+
+### `prompt` — optional guidance for variant direction
+
+Provide context about what kind of variations the user wants. The `variantOptions` do the heavy lifting, but the prompt adds nuance.
+
+### `variantOptions` — controls what and how much to vary
+
+| Field | Type | Values | Description |
+|-------|------|--------|-------------|
+| `variantCount` | int | 1–5 | Number of variants to generate |
+| `creativeRange` | enum | `REFINE`, `EXPLORE`, `REIMAGINE` | How much to deviate from the original |
+| `aspects` | array | See below | Which design aspects to vary |
+
+#### `creativeRange` mapping from user language
+
+| User says | → creativeRange | What it does |
+|-----------|----------------|-------------|
+| "subtle changes", "minor tweaks", "polish" | `REFINE` | Small refinements, stays close to original |
+| "alternatives", "different options", "explore" | `EXPLORE` | Meaningful differences while keeping the concept |
+| "radical", "completely different", "reimagine" | `REIMAGINE` | Major departures from the original design |
+
+#### `aspects` — what to vary
+
+| Value | Varies | Keeps stable |
+|-------|--------|-------------|
+| `LAYOUT` | Structure, spacing, component arrangement | Colors, fonts, content |
+| `COLOR_SCHEME` | Colors, gradients, contrast | Layout, fonts, content |
+| `IMAGES` | Photography, illustrations, icons | Layout, colors, text |
+| `TEXT_FONT` | Typography, font choices, sizes | Layout, colors, content |
+| `TEXT_CONTENT` | Copy, labels, placeholder text | Layout, colors, fonts |
+
+You can combine aspects: `["LAYOUT", "COLOR_SCHEME"]` varies both simultaneously.
+
+### `deviceType` — optional
+
+Same enum: `MOBILE`, `DESKTOP`, `TABLET`, `AGNOSTIC`
+
+### `modelId` — optional
+
+| Value | Use when |
+|-------|---------|
+| `GEMINI_3_PRO` | Higher quality variants, complex designs |
+| `GEMINI_3_FLASH` | Faster iteration, simpler screens |
+
+## Output
+
+Returns new screens added to the project. Each variant appears as a separate screen in `list_screens`.
+
+## After generating variants
+
+1. Call `stitch-mcp-list-screens` to find all new variant screens
+2. Call `stitch-mcp-get-screen` for each to get screenshots
+3. Present side by side: "Here are your 3 variants: [screenshots]. Which one do you prefer?"
+4. Once the user picks a winner, offer:
+   - "Edit the chosen variant further?" → `stitch-mcp-edit-screens`
+   - "Convert to code?" → framework conversion workflow
+   - "Generate more variants from the winner?" → another `generate_variants` call
+
+## Anti-patterns
+
+- **Never generate variants without an existing screen** — you need a source design
+- **Never use `projects/ID` format** for projectId or screenId — both must be numeric
+- **Never set `variantCount` above 5** — the API caps at 5

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

@@ -0,0 +1,67 @@
+---
+name: stitch-mcp-get-project
+description: Retrieves metadata for a specific Stitch project — title, theme, create/update time. Use to inspect a project before generating new screens. Do NOT use this if you already have a screenId — use stitch-mcp-get-screen instead.
+allowed-tools:
+  - "stitch*:*"
+---
+
+# Stitch MCP — Get Project
+
+Retrieves full metadata for a specific Stitch project. Useful for understanding an existing project's theme and screen list before generating additional screens.
+
+## Critical prerequisite
+
+**Only use this skill when the user explicitly mentions "Stitch".**
+
+**Do NOT call this if you already have both `projectId` AND `screenId`.** In that case, call `stitch-mcp-get-screen` directly — it's more efficient.
+
+## When to use
+
+- User provides a Stitch project URL and you need its details
+- You need to know the existing design theme before generating new consistent screens
+- Verifying a project exists before proceeding
+
+## Step 1: Parse the project ID from context
+
+The user may provide the project reference in several formats — always extract to the `projects/ID` format:
+
+| Input format | → Argument for `get_project` |
+|---|---|
+| `3780309359108792857` (numeric) | `projects/3780309359108792857` |
+| `projects/3780309359108792857` | `projects/3780309359108792857` (use as-is) |
+| `https://stitch.withgoogle.com/projects/3780309359108792857` | Extract ID → `projects/3780309359108792857` |
+
+## Step 2: Call the MCP tool
+
+```json
+{
+  "name": "get_project",
+  "arguments": {
+    "name": "projects/3780309359108792857"
+  }
+}
+```
+
+## Output schema
+
+```json
+{
+  "name": "projects/3780309359108792857",
+  "title": "Analytics Dashboard",
+  "createTime": "2024-11-10T09:00:00Z",
+  "updateTime": "2024-11-15T10:30:00Z",
+  "designTheme": {
+    "colorMode": "LIGHT",
+    "primaryColor": "#6366F1"
+  },
+  "screenInstances": [
+    { "name": "projects/3780309359108792857/screens/88805..." }
+  ]
+}
+```
+
+## After getting the project
+
+- Note the `designTheme` — use it to keep new screens visually consistent
+- Note the `screenInstances` list — extract screenId values if you need to inspect specific screens
+- Use `stitch-mcp-list-screens` for a richer view of the screen list including thumbnails

package/skills/stitch-mcp-get-screen/SKILL.md

@@ -0,0 +1,117 @@
+---
+name: stitch-mcp-get-screen
+description: Retrieves full details of a specific Stitch screen — HTML download URL, screenshot URL, dimensions. This is the final step in design retrieval before code conversion.
+allowed-tools:
+  - "stitch*:*"
+  - "Bash"
+  - "Read"
+  - "Write"
+---
+
+# Stitch MCP — Get Screen
+
+Retrieves the full output of a Stitch-generated screen: the HTML source code URL and the screenshot image URL. This is the gateway between Stitch design and framework conversion.
+
+## Critical prerequisite
+
+**Only use this skill when the user explicitly mentions "Stitch".**
+
+**If you already have both `projectId` AND `screenId`, call this directly** — do not call `get_project` first.
+
+## When to use
+
+- After `list_screens` has returned a screenId
+- User provides a Stitch screen URL and wants to convert it to code
+- Retrieving assets for any conversion skill: Next.js, Svelte, HTML, React Native, or SwiftUI
+
+## Step 1: Parse IDs from context
+
+The user may provide the screen reference in different formats:
+
+| Input format | → projectId | → screenId |
+|---|---|---|
+| `projects/123/screens/456` | `123` | `456` |
+| `https://stitch.withgoogle.com/projects/123?node-id=456` | `123` | `456` |
+| Separate numeric IDs already known | Use as-is | Use as-is |
+
+## Step 2: Call the MCP tool
+
+**Important: Both IDs must be numeric — no `projects/` or `screens/` prefix.**
+
+```json
+{
+  "name": "get_screen",
+  "arguments": {
+    "projectId": "3780309359108792857",
+    "screenId": "88805abc123def456"
+  }
+}
+```
+
+```
+✅ projectId: "3780309359108792857"
+❌ projectId: "projects/3780309359108792857"
+
+✅ screenId: "88805abc123def456"
+❌ screenId: "screens/88805abc123def456"
+```
+
+## Output schema
+
+```json
+{
+  "name": "projects/3780309359108792857/screens/88805abc123def456",
+  "htmlCode": {
+    "downloadUrl": "https://storage.googleapis.com/stitch-output/..."
+  },
+  "screenshot": {
+    "downloadUrl": "https://storage.googleapis.com/stitch-screenshots/..."
+  },
+  "figmaExport": {
+    "downloadUrl": "https://storage.googleapis.com/stitch-figma/..."
+  },
+  "width": 390,
+  "height": 844,
+  "deviceType": "MOBILE"
+}
+```
+
+## Step 3: Download the HTML reliably
+
+AI fetch tools frequently fail on Google Cloud Storage URLs. Use the bash script:
+
+```bash
+bash scripts/fetch-stitch.sh "[htmlCode.downloadUrl]" "temp/source.html"
+```
+
+Always quote the URL to handle special characters.
+
+## Step 4: Determine framework and route to conversion
+
+After retrieving the screen, check what the user wants to do with it.
+
+Check the `deviceType` in the response first — it shapes which options to suggest:
+
+| `deviceType` | Sensible defaults to suggest |
+|---|---|
+| `DESKTOP` | Next.js, Svelte, HTML |
+| `MOBILE` | Next.js (PWA), Svelte, HTML, React Native, SwiftUI |
+| `AGNOSTIC` | Any |
+
+Then route based on user intent:
+
+| User intent | → Load skill |
+|---|---|
+| "Convert to Next.js", "React app", "App Router" | `stitch-nextjs-components` |
+| "Convert to Svelte", "SvelteKit" | `stitch-svelte-components` |
+| "Convert to HTML", "PWA", "Capacitor", "Ionic", "web app" | `stitch-html-components` |
+| "React Native", "Expo", "iOS and Android", "cross-platform" | `stitch-react-native-components` |
+| "SwiftUI", "Xcode", "native iOS", "iOS only" | `stitch-swiftui-components` |
+| "Extract design system", "get the colors/fonts" | `stitch-design-system` |
+| "Just show me the screenshot" | Present `screenshot.downloadUrl` |
+| No framework mentioned, desktop design | Ask: Next.js, Svelte, or HTML? |
+| No framework mentioned, mobile design | Ask: React Native, SwiftUI, or HTML (Capacitor)? |
+
+## References
+
+- `scripts/fetch-stitch.sh` — Reliable GCS HTML downloader

package/skills/stitch-mcp-get-screen/scripts/fetch-stitch.sh

@@ -0,0 +1,35 @@
+#!/usr/bin/env bash
+# fetch-stitch.sh
+# Reliably downloads Stitch HTML from Google Cloud Storage URLs.
+# GCS URLs require redirect handling and security handshakes that AI fetch tools fail on.
+#
+# Usage:
+#   bash scripts/fetch-stitch.sh "<url>" "<output-path>"
+#
+# Example:
+#   bash scripts/fetch-stitch.sh "$htmlCode_downloadUrl" "temp/source.html"
+
+set -euo pipefail
+
+URL="${1:?Usage: fetch-stitch.sh <url> <output-path>}"
+OUTPUT="${2:?Usage: fetch-stitch.sh <url> <output-path>}"
+
+mkdir -p "$(dirname "$OUTPUT")"
+
+curl -L \
+  -A "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36" \
+  --compressed \
+  --retry 3 \
+  --retry-delay 1 \
+  --max-time 30 \
+  --silent \
+  --show-error \
+  --output "$OUTPUT" \
+  "$URL"
+
+if [ ! -s "$OUTPUT" ]; then
+  echo "Error: Downloaded file is empty. URL may be expired or invalid." >&2
+  exit 1
+fi
+
+echo "Downloaded to: $OUTPUT ($(wc -c < "$OUTPUT") bytes)"

package/skills/stitch-mcp-list-design-systems/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: stitch-mcp-list-design-systems
+description: Lists all Stitch Design Systems, optionally filtered by project. Returns asset names needed for apply and update operations.
+allowed-tools:
+  - "stitch*:*"
+---
+
+# Stitch MCP — List Design Systems
+
+Lists all available Stitch Design Systems. These are reusable theme configurations (colors, fonts, roundness, saturation) that can be applied to screens for visual consistency across a project.
+
+## Critical prerequisite
+
+**Only use this skill when the user explicitly mentions "Stitch".**
+
+## When to use
+
+- Before applying a design system — need to find the `assetId`
+- User asks "what design systems do I have?"
+- The orchestrator checks for existing design systems during project setup (Step 4b)
+- Before creating a new design system — check if one already exists
+
+## Call the MCP tool
+
+```json
+{
+  "name": "list_design_systems",
+  "arguments": {
+    "projectId": "3780309359108792857"
+  }
+}
+```
+
+### `projectId` — numeric ID only, optional
+
+```
+✅ "3780309359108792857"
+❌ "projects/3780309359108792857"
+```
+
+If omitted, returns all design systems across all projects.
+
+## Output schema
+
+Returns an array of Asset objects:
+
+```json
+{
+  "assets": [
+    {
+      "name": "assets/ds_abc123",
+      "displayName": "SaaS Dashboard Theme",
+      "designSystem": {
+        "theme": {
+          "colorMode": "LIGHT",
+          "font": "DM_SANS",
+          "roundness": "ROUND_EIGHT",
+          "saturation": 3,
+          "customColor": "#6366F1",
+          "backgroundLight": "#FFFFFF",
+          "backgroundDark": "#18181B"
+        },
+        "designTokens": "...",
+        "styleGuidelines": "..."
+      }
+    }
+  ]
+}
+```
+
+## After listing
+
+Present as a readable table:
+
+| # | Name | Font | Color | Mode | Asset ID |
+|---|------|------|-------|------|----------|
+| 1 | SaaS Dashboard Theme | DM Sans | #6366F1 | Light | `ds_abc123` |
+
+Then offer:
+- "Apply one of these to a screen?" → `stitch-mcp-apply-design-system`
+- "Update an existing design system?" → `stitch-mcp-update-design-system`
+- "Create a new design system?" → `stitch-mcp-create-design-system`
+
+Extract the `name` field from each asset — this is the `assetId` needed for `apply_design_system`.

package/skills/stitch-mcp-list-projects/SKILL.md

@@ -0,0 +1,77 @@
+---
+name: stitch-mcp-list-projects
+description: Lists all Stitch projects accessible to the user. Use this to find an existing project ID before resuming work or generating new screens in an existing project.
+allowed-tools:
+  - "stitch*:*"
+---
+
+# Stitch MCP — List Projects
+
+Lists Stitch projects available to the user. Use this when you need to find an existing projectId rather than creating a new project.
+
+## Critical prerequisite
+
+**Only use this skill when the user explicitly mentions "Stitch".**
+
+## When to use
+
+- User says "continue working on my Stitch project" without providing an ID
+- User says "list my Stitch projects" or "what projects do I have?"
+- You need to find an existing projectId before calling `generate_screen_from_text`
+- Checking whether a project already exists before creating a new one
+
+## Call the MCP tool
+
+**To list owned projects (default):**
+```json
+{
+  "name": "list_projects",
+  "arguments": {
+    "filter": "view=owned"
+  }
+}
+```
+
+**To list projects shared with the user:**
+```json
+{
+  "name": "list_projects",
+  "arguments": {
+    "filter": "view=shared"
+  }
+}
+```
+
+**To list all accessible projects (owned + shared):**
+```json
+{
+  "name": "list_projects",
+  "arguments": {}
+}
+```
+
+## Output schema
+
+```json
+{
+  "projects": [
+    {
+      "name": "projects/3780309359108792857",
+      "title": "Analytics Dashboard",
+      "updateTime": "2024-11-15T10:30:00Z"
+    }
+  ]
+}
+```
+
+## After listing
+
+1. Present the project list to the user with titles and last-updated timestamps
+2. Ask which project to work in (if multiple)
+3. Extract the numeric ID from the chosen `name` field: `projects/ID` → `ID`
+4. Store both the full name and numeric ID for subsequent calls
+
+## ID format reminder
+
+- `list_screens`, `get_project` → use `projects/NUMERIC_ID`
+- `generate_screen_from_text`, `get_screen` → use `NUMERIC_ID` only