Wiring Google Stitch Into Your Coding Agent
You've probably got a coding agent you rely on by now. Codex, Claude Code, Cursor, whatever you settled on. And if you're doing UI work with Google Stitch, you've got two separate things that don't know about each other. Stitch Design Skills is a collection of agent skills and plugins that bridges that gap, following the Agent Skills open standard so it works across the agents you're already using.
What It Does
This repo packages Stitch-related capabilities as agent skills and plugins. If you haven't run into the term, a skill is a bundle of instructions and tooling that a coding agent can load and use—the Agent Skills standard is what makes these portable across different agents rather than locked to one vendor.
The collection is organized into three plugins: stitch-design for design-focused skills, stitch-build for build and component skills, and stitch-utilities for helper skills. You can install the full suite or cherry-pick individual skills. The README notes that skills often have inter-dependencies, so if you go selective, you'll want to pull in everything a given skill needs. Under the hood, these skills rely on the Stitch MCP server, which you'll need to set up separately.
Why It's Cool
-
It meets your agent where it lives. The install paths are genuinely per-agent—Codex gets a marketplace registration (via CLI or UI), Claude Code and Cursor get
npx pluginscommands scoped to project or workspace, and OpenCode gets manual instructions. That's more thought than most cross-agent tooling bothers with. -
The Codex sparse checkout is a nice touch. The marketplace command supports
--sparseflags so you only clone the plugin paths you actually need. Optional, but a small, considerate default for anyone who doesn't want the whole repo on disk. -
The OpenCode section is admirably honest. Rather than pretending everything just works, the README spells out the friction: OpenCode requires skill
namefrontmatter to be lowercase kebab-case and match the directory name, so skills usingstitch::…names need renaming first. It also flags that tool names inside skill instructions may not match OpenCode's builtins (webfetchandbashinstead ofweb_fetchandrun_command). That kind of caveat saves you an hour of confused debugging. -
Selective install is there if you want it.
npx skills addlets you grab specific skills instead of the full plugin suite—useful if you only care about design work and don't need the build or utility skills cluttering your agent's context.
How to Try It
Start with the plugins route, which the README recommends as the fastest path to the full suite.
For Codex, register the marketplace via CLI:
codex plugin marketplace add google-labs-code/stitch-skills --ref main \
--sparse .agents/plugins \
--sparse plugins/stitch-design \
--sparse plugins/stitch-build \
--sparse plugins/stitch-utilities
Or do it through the Codex UI under Settings → Plugin Marketplaces → Add, using the repo URL and main as the git ref.
For Claude Code and Cursor:
# Claude Code — installs into the current project
npx plugins add google-labs-code/stitch-skills --scope project --target claude-code
# Cursor — installs into the current workspace
npx plugins add google-labs-code/stitch-skills --scope workspace --target cursor
For OpenCode, it's manual. Copy the skill folders you need into .opencode/skills (project-local is recommended), or into .claude/skills/ or .agents/skills/, which OpenCode also discovers:
mkdir -p .opencode/skills
cp -R plugins/stitch-design/skills/generate-design .opencode/skills/generate-design
Then add the Stitch MCP server to your opencode.json after completing the Stitch MCP setup:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stitch": {
"type": "remote",
"url": "YOUR_STITCH_MCP_URL",
"enabled": true
}
}
}
If you'd rather pick individual skills, run npx skills add google-labs-code/stitch-skills and remember the dependency warning. Both npx plugins --help and npx skills --help will show you the available options.
One thing to note up front: the skills require the Stitch MCP server, so budget time for that setup before expecting anything to work.
The repo lives at github.com/google-labs-code/stitch-skills.
Final Thoughts
This is infrastructure, not a product—it's for developers already working with Google Stitch who want their coding agent to participate in that workflow rather than sitting on the sidelines. The multi-agent support is the real value here, and the README's willingness to document per-agent quirks (especially the OpenCode naming constraints) suggests the maintainers actually tested the paths they describe. If you're on Codex or Claude Code, setup is a single command; if you're on OpenCode, read the notes carefully before you start. Either way, it's a small install for a meaningful reduction in context-switching.
Follow @githubprojects for more developer tools and open source projects.