Stitch

Use this skill when the task needs to actually talk to the Stitch service. Prefer the bundled runner in scripts/run.sh over ad-hoc one-off code when the request is operational: listing projects, generating screens, editing, variants, design systems, or exports.

The runner wraps the official @google/stitch-sdk, pinned to v0.3.5 by default (override with --sdk-package), and exposes the same surface as the documented Stitch SDK at stitch.withgoogle.com/docs.

Workflow

1. Resolve configuration first.

   • Use --config /abs/path/to/file.json when the user points to a config file.
   • Otherwise the runner checks STITCH_SKILL_CONFIG, then .stitch.json, then stitch.json in the current working directory.
   • Config schema and an example file live in references/config.md and assets/stitch.example.json.
   • Use save-config or --save-config when the user wants resolved parameters written back to .stitch.json or another target config path.

2. Resolve authentication.

   • Prefer STITCH_API_KEY for local scripted use.
   • OAuth is supported through STITCH_ACCESS_TOKEN plus GOOGLE_CLOUD_PROJECT. The official SDK requires both together when not using apiKey.
   • STITCH_HOST overrides the MCP server URL when the user is pointed at a non-default endpoint.
   • CLI flags override env vars, and env vars override config-file values.