From f4064b95c773910bc5c930182ac77fa9490d9316 Mon Sep 17 00:00:00 2001 From: Gabi Date: Mon, 20 Jul 2026 22:17:41 +0200 Subject: [PATCH] fix: replace fictional enum values and date-stamp volatile claims MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Closes the last two items from the Codex pass, and a real bug found while chasing one of them. `PHONE` was used as a deviceType in two skills' response examples, and get_project's field table listed it as a documented value. It isn't in the live enum, and it appears in zero of 85 real projects (68 DESKTOP, 13 MOBILE). Same class as the ROBOTO font bug — a value an agent would copy and the API would reject. Replaced with DESKTOP, and the table now lists the real five. Swept for the general case rather than fixing the two instances: every enum-valued field in every JSON example across skills/ and docs/ is now checked against the live enums (deviceType, colorMode, colorVariant, roundness, modelId, creativeRange, and all four font slots). No remaining mismatches. Date-stamped the two claims that will rot — Stitch's free-tier availability and the comparison against Google's official repo. Both now say when they were checked and tell the reader to verify rather than trust a snapshot. Deliberately did NOT add DEVICE_TYPE_UNSPECIFIED to the skills' "here are your options" lists. It's the zero-value sentinel; an agent choosing a value to send should omit the field instead. The schemas carry it, which is where it belongs. --- README.md | 4 ++-- skills/stitch-mcp-create-project/SKILL.md | 2 +- skills/stitch-mcp-get-project/SKILL.md | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 777ba2c..2e49695 100644 --- a/README.md +++ b/README.md @@ -43,7 +43,7 @@ All four of these came out of stitch-kit. Different briefs, genuinely different --- -> **Generating designs needs Google Stitch.** Sign in at [stitch.withgoogle.com](https://stitch.withgoogle.com) with any Google account, then grab an API key from [settings](https://stitch.withgoogle.com/settings). No waitlist, no invite, free as of mid-2026 — but there are monthly generation limits and Google has signalled paid tiers, so treat the allowance as generous-but-finite. +> **Generating designs needs Google Stitch.** Sign in at [stitch.withgoogle.com](https://stitch.withgoogle.com) with any Google account, then grab an API key from [settings](https://stitch.withgoogle.com/settings). As of July 2026: no waitlist, no invite, free to use — but there are monthly generation limits and Google has signalled paid tiers, so treat the allowance as generous-but-finite. Check Stitch's own site before relying on any of that; it's their pricing to change, not mine. > > **Converting to code doesn't.** The framework conversion skills take a local HTML file or a URL just as happily as a Stitch screen. If you already have markup and only want production components out of it, you need no Google account at all. @@ -198,7 +198,7 @@ The examples folder is the secret weapon. Agents produce dramatically better out ## vs. the official Google Stitch Skills -Google's [official repo](https://github.com/google-labs-code/stitch-skills) ships 15 skills across three plugins — `stitch-design`, `stitch-build`, `stitch-utilities`. It's a real toolkit, not a stub, and it does one whole thing stitch-kit doesn't (see the gaps below). +Google's [official repo](https://github.com/google-labs-code/stitch-skills) ships 15 skills across three plugins — `stitch-design`, `stitch-build`, `stitch-utilities`. (Checked July 2026; they move fast, so verify before taking this comparison as current.) It's a real toolkit, not a stub, and it does one whole thing stitch-kit doesn't (see the gaps below). Raw skill counts aren't a fair comparison: Google consolidated generate/edit/variants into one skill and the four design-system operations into another, where stitch-kit keeps them as separate wrappers. Different granularity, not more capability. Here's where both cover the same ground: diff --git a/skills/stitch-mcp-create-project/SKILL.md b/skills/stitch-mcp-create-project/SKILL.md index 6c546e9..e97df0a 100644 --- a/skills/stitch-mcp-create-project/SKILL.md +++ b/skills/stitch-mcp-create-project/SKILL.md @@ -55,7 +55,7 @@ The tool returns a `name` field in the format `projects/NUMERIC_ID`. You must ex "title": "Analytics Dashboard", "createTime": "2026-03-24T14:30:00Z", "visibility": "PRIVATE", - "deviceType": "PHONE", + "deviceType": "DESKTOP", "projectType": "TEXT_TO_UI", "designTheme": { "colorMode": "LIGHT", diff --git a/skills/stitch-mcp-get-project/SKILL.md b/skills/stitch-mcp-get-project/SKILL.md index 6a93fa7..4df7b97 100644 --- a/skills/stitch-mcp-get-project/SKILL.md +++ b/skills/stitch-mcp-get-project/SKILL.md @@ -50,7 +50,7 @@ The user may provide the project reference in several formats — always extract "title": "Analytics Dashboard", "createTime": "2024-11-10T09:00:00Z", "updateTime": "2024-11-15T10:30:00Z", - "deviceType": "PHONE", + "deviceType": "DESKTOP", "visibility": "PRIVATE", "projectType": "TEXT_TO_UI", "origin": "STITCH", @@ -158,7 +158,7 @@ The user may provide the project reference in several formats — always extract | Field | Type | Values / Notes | |-------|------|----------------| -| `deviceType` | string | `PHONE`, `TABLET`, `DESKTOP`, etc. | +| `deviceType` | string | `MOBILE`, `DESKTOP`, `TABLET`, `AGNOSTIC`, or `DEVICE_TYPE_UNSPECIFIED` | | `visibility` | enum | `PRIVATE`, `PUBLIC` | | `projectType` | enum | `TEXT_TO_UI`, `PROJECT_DESIGN`, etc. | | `origin` | enum | `STITCH`, `IMPORTED_FROM_GALILEO` |