stitch-design
Create and adapt screens, bring code into Stitch and manage design assets.
6 skills
Install Stitch Agent Skills with an agent-specific plan from Loop Engineering. Choose plugins or individual skills, connect Stitch MCP and check that your agent can discover the workflow.
Choose a setup. Review commands before running them.
This Loop Engineering tool only displays and copies instructions. Nothing runs, connects or uploads from this page.
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
16 skills across stitch-design, stitch-build, stitch-utilities. Recommended here means the complete suite; choose a family or one skill for a smaller setup.
Registered marketplace; install and enable the chosen plugins in Codex.
Keep plugin-managed files in their managed location. Individual skill installers show the destination before confirmation.
Last verified: 2026-10-05 · Source README
Last verified: . Based on Google Labs Code’s open-source Stitch Skills repository and Stitch MCP documentation. The repository is not an officially supported Google product. This installer is maintained independently by Loop Engineering.
An Agent Skill is a workflow package centered on SKILL.md: a name, a description of when to use it and instructions the coding agent can load for a relevant task. The Stitch repository packages design and implementation workflows with supporting resources, examples and scripts. Preserve those files when installing a skill; the markdown alone may refer to missing tools or templates.
The agent discovers the skill and follows its procedure. Work that reads or changes Stitch projects also needs a connected Stitch MCP server. For Loop Engineering, treat each skill as a maintained procedure: inspect its permissions, define a stop rule and verify a small task before granting broader access. Agent Skills format reference.
| Check | Stitch Agent Skills | Stitch MCP |
|---|---|---|
| Purpose | Tell the agent how to carry out a workflow. | Give the agent tools to access Stitch. |
| Installation | Plugin packages or SKILL.md folders and their resources. | Remote server configuration and authentication. |
| Successful setup | The intended skill is discoverable in the agent. | Stitch tools are visible and can list your projects. |
| Credentials | Copying a skill folder does not authenticate Stitch. | The client holds local credentials and project access. |
Three plugin families organize the current repository. The recommended setup in this tool selects all three; it is a complete starting point, with narrower choices available. The inspected source tree contains 16 skills, including site-md, which was not yet in the README’s summary table on the verification date.
Create and adapt screens, bring code into Stitch and manage design assets.
6 skills
Turn designs into components, dashboards and walkthrough assets.
5 skills
Prepare design and site specifications, improve prompts and coordinate build loops.
5 skills
Match the task to a source skill. Names below are the repository’s frontmatter names; OpenCode needs the naming adaptation described in its setup. A selective install may need supporting skills: code-to-design orchestrates extraction and upload workflows; generate-design has conditional design-system and image-upload branches; stitch-loop uses design/site context.
Generate or edit screens and create variants.
designMove an existing frontend into a Stitch design.
designUpload design specifications and apply themes.
designExtract DESIGN.md from frontend source.
designCapture a running app as self-contained HTML.
designUpload local assets to a Stitch project.
designCreate React components from Stitch screens.
buildAdapt designs for React Native.
buildBuild React + Vite dashboards from screens.
buildCreate project walkthrough videos.
buildIntegrate shadcn/ui components.
buildDerive DESIGN.md from a Stitch project.
utilitiesMake a UI request more precise.
utilitiesCoordinate repeated page-building work.
utilitiesPrepare design standards for visual consistency.
utilitiesWrite SITE.md project context for a build loop.
utilitiesRegistered marketplace; install and enable the chosen plugins in Codex.
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
Stitch MCP authentication guide · Codex skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.
Current project (--scope project). Run from the intended project root.
npx plugins add google-labs-code/stitch-skills --scope project --target claude-code
MCP registration example — replace api-key locally
claude mcp add stitch --transport http https://stitch.googleapis.com/mcp --header "X-Goog-Api-Key: api-key" -s user
Stitch MCP authentication guide · Claude Code skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.
Current workspace (--scope workspace). Open the intended workspace first.
npx plugins add google-labs-code/stitch-skills --scope workspace --target cursor
.cursor/mcp.json — merge into existing configuration
{"mcpServers": {"stitch": {"url": "https://stitch.googleapis.com/mcp","headers": {"X-Goog-Api-Key": "YOUR-API-KEY"}}}}
Stitch MCP authentication guide · Cursor skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.
Compatible, but no dedicated one-command flow is documented here.
Project skill path: .gemini/skills/<folder>/SKILL.md. The skill folders are under plugins/stitch-design/skills, plugins/stitch-build/skills and plugins/stitch-utilities/skills in the source repository. Copy complete folders, then check the scope: Workspace skills in .gemini/skills; user skills in ~/.gemini/skills.
Stitch MCP extension — does not install this skills repository
gemini extensions install https://github.com/gemini-cli-extensions/stitch
Stitch MCP authentication guide · Gemini CLI skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.
Manual setup required. The repository explicitly excludes npx plugins and npx skills for OpenCode.
Project skill path: .opencode/skills/<folder>/SKILL.md. The skill folders are under plugins/stitch-design/skills, plugins/stitch-build/skills and plugins/stitch-utilities/skills in the source repository. Copy complete folders, then check the scope: Project-local .opencode/skills; optional user path ~/.config/opencode/skills.
opencode.json — template, not a complete authenticated configuration
{"$schema": "https://opencode.ai/config.json","mcp": {"stitch": {"type": "remote","url": "YOUR_STITCH_MCP_URL","enabled": true}}}
Stitch MCP authentication guide · OpenCode skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.
Compatible, but no dedicated one-command flow is documented here.
Project skill path: .agents/skills/<folder>/SKILL.md. The skill folders are under plugins/stitch-design/skills, plugins/stitch-build/skills and plugins/stitch-utilities/skills in the source repository. Copy complete folders, then check the scope: Workspace skills in .agents/skills. Global locations vary by Antigravity surface.
Antigravity MCP configuration — merge, do not overwrite
{"mcpServers": {"stitch": {"serverUrl": "https://stitch.googleapis.com/mcp","headers": {"X-Goog-Api-Key": "YOUR-API-KEY"}}}}
Stitch MCP authentication guide · Antigravity skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.
For Codex, Claude Code or Cursor, open the current README’s interactive skills installer below. Select a skill by its exact name, the target agent and the intended scope. This entry point does not automatically narrow the installation to the skill selected on this webpage. The README does not document noninteractive selection flags, so this tool does not generate them. Inspect referenced supporting skills before confirming; a single folder may not cover an orchestrated workflow.
npx skills add google-labs-code/stitch-skills
For example, choose enhance-prompt for prompt refinement, or stitch::react-components for React output. For OpenCode, use the complete-folder manual route and normalize the frontmatter name. Gemini CLI and Antigravity have manual paths in this guide because the repository lists compatibility without a dedicated plugin command. Interactive skills CLI reference.
Check skill discovery first, then MCP connectivity. Finally try a small, relevant task in a disposable project with an explicit stop rule and human approval before any upload or design change. The connection check below only asks to list existing projects; it does not create or edit screens.
Install instructions and a successful copy do not prove connectivity. Authenticate the remote server in your agent, confirm the tools appear, then ask to list your Stitch projects.
Check the destination belongs to the working project and SKILL.md is directly inside the skill folder. Confirm the plugin is enabled, or use the agent’s discovery checks below. Preserve referenced resources when copying.
Replace legacy npx add-skill examples with the current README’s npx skills add entry point. Recheck the source instead of adapting old flags by guesswork.
Run the plugin command from the intended project/workspace. In the interactive skills installer, confirm both target and scope before accepting. Manual global paths differ by agent.
Register the stitch-skills marketplace with the README’s ref and four sparse paths. Then install and enable a plugin in the interface; registration alone is insufficient.
Use the source frontmatter name in the selected-skill list. Several Design names include stitch::. Selective installs may need supporting skills referenced by their SKILL.md; review those workflow branches.
Rename namespaced frontmatter to lowercase kebab-case and match the containing folder. Review renamed cross-skill references and webfetch/bash tool mappings. Check skill permissions if names remain hidden.
npx flows require Node.js/npm and an available installer. MCP requires the provider’s authentication and project access. Keep keys local, avoid committing them, and use the official setup guide for OAuth renewal or changed authentication steps.
Use Stitch skills for a specific design workflow. Use Loop Engineering to write the surrounding goal, verification steps, budget and approval gate. Keep the workflow small enough that a reviewer can tell whether it succeeded.
Reusable SKILL.md workflow packages from Google Labs Code’s open-source Stitch Skills repository. They help compatible coding agents follow design and implementation procedures, using supporting files where needed.
Choose your agent in the installer. Codex registers the marketplace before plugin installation in its interface; Claude Code and Cursor have documented plugin commands. Other supported agents have manual steps here. Configure Stitch MCP separately.
Yes. The repository documents marketplace registration with four sparse paths. Install and enable the chosen plugins afterward, then check discovery through /skills or the $ skill picker.
Yes. The repository provides a project-scoped plugin installation command targeting claude-code. Confirm the installed plugin’s skills in the / menu and separately verify Stitch MCP connectivity.
Yes. The README documents workspace-scoped plugin installation targeting cursor. Check Customize → Skills in the intended workspace and verify the MCP connection.
Stitch-dependent workflows need an authenticated Stitch MCP connection. Local preparation tasks may not call Stitch, but installing skill files alone does not connect your agent to the service.
Skills describe how to carry out a workflow. MCP supplies the tool interface and authentication needed to access Stitch projects and screens. Both discovery and connectivity need separate verification.
Yes. Use the README’s npx skills add entry point and choose the desired skill, target agent and scope interactively. Review any supporting workflows first. OpenCode requires manual folder installation.
That legacy command is deprecated for this guide. The current Stitch README uses npx skills add. The installer never recommends or generates npx add-skill.
The README provides manual setup for OpenCode. Copy full skill folders into .opencode/skills, use lowercase kebab-case names matching folders, adapt tool references and configure Stitch MCP separately.
The repository lists Gemini CLI compatibility without a dedicated one-command plugin flow. This guide uses documented .gemini/skills folders and /skills reload plus /skills list for discovery. The Stitch MCP extension is installed separately.
The repository belongs to Google Labs Code, but its README says it is not an officially supported Google product. This Loop Engineering installer is an independent guide and command preview.
No. It generates static instructions in your browser, with no shell execution, account connection, credential input or data upload. Review commands before running them in your own environment.
Commands were checked against the README on 2026-10-05; skill names and folders were checked against the repository tree and individual SKILL.md files. These instructions are a dated snapshot. Recheck the upstream documentation before installing after a product update.