Skip to main content
skill CX Codex

google-stitch-skills — Claude Code skill: features and setup

A skill collection for taking Google Stitch designs toward code, from screen generation to React components. It requires a configured Stitch MCP server with credentials.

MIT 207 installs ★ 35 updated 2026-10-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add podo/design-agent-skills --skill google-stitch-skills -a claude-code
Open on GitHub

What google-stitch-skills does

Use the skills to create or revise Google Stitch screens, maintain DESIGN.md and SITE.md, refine UI prompts, and turn Stitch output into React, React Native, or shadcn/ui components. They can also bring existing web code into a Stitch project and support repeated design improvements.

The package contains separate skills for design generation, design systems, specification extraction, and component work. Install the collection as a whole: its skills rely on one another. A configured Stitch MCP server with credentials is required; without the running server, the skills cannot perform Stitch operations.

There is a naming conflict with standalone shadcn-ui and remotion skills: both use directory names that this collection also writes to. If either is already installed, check those directories before adding the package.

What it helps with

  • create and revise Google Stitch screens
  • write a design specification in DESIGN.md
  • turn Stitch designs into React or React Native components
  • move existing web code into a Stitch project
  • iterate on a design through Stitch MCP

Example prompts for the agent

  • Create a Google Stitch screen from this brief and make a mobile variant.
  • Turn this Stitch design into React components.
  • Bring this existing web code into Stitch and extract a DESIGN.md specification.

How to install google-stitch-skills

1Skills CLI (Vercel)

npx skills add podo/design-agent-skills --skill google-stitch-skills -a claude-code

2Manually: put the files in place

~/.claude/skills/google-stitch-skills/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/google-stitch-skills/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about google-stitch-skills

How do I install google-stitch-skills in Claude Code?

Run npx skills add podo/design-agent-skills --skill google-stitch-skills -a claude-code. The skill file is at ~/.claude/skills/google-stitch-skills/SKILL.md.

What does google-stitch-skills do?

It provides skills for creating and editing Google Stitch screens, managing design specifications, and generating UI components from Stitch designs. It also supports moving existing code into Stitch and iterating on designs.

What does google-stitch-skills need to run?

It requires a configured Stitch MCP server with credentials. The skills use that server to carry out Stitch operations.

Source text

SKILL.md · MIT
---
name: google-stitch-skills
description: |
  Official Google Stitch skills for the design-to-code pipeline: generate and edit Stitch screens,
  DESIGN.md and SITE.md management, prompt enhancement, React / React Native / shadcn/ui component
  generation, code-to-design upload, and iterative Stitch build loops.
triggers:
  - "Stitch skill"
  - "google stitch"
  - "design-md"
  - "stitch loop"
  - "enhance prompt"
  - "stitch shadcn"
das:
  category: figma-code
  upstream: "https://github.com/google-labs-code/stitch-skills"
  version: latest
  install: false
---

# google-stitch-skills

> Catalogue stub — full package: [google-labs-code/stitch-skills](https://github.com/google-labs-code/stitch-skills)

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->
## Decision tree

1. **Is the full skill already installed?**
   This package installs 16 skills (`stitch-loop`, `design-md`, `enhance-prompt`, `site-md`, `taste-design`, `stitch-extract-design-md`, `stitch-extract-static-html`, `stitch-generate-design`, `stitch-code-to-design`, `stitch-manage-design-system`, `stitch-upload-to-stitch`, `stitch-react-components`, `stitch-react-native`, `react-vite-dashboard`, `shadcn-ui`, `remotion`); checking the first.
   - Global: `f=~/.agents/skills/stitch-loop/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"`
   - Project: `f=.agents/skills/stitch-loop/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"`
   - `installed` → the skill is installed as `stitch-loop`, invoke it and proceed
   - `pointer` → go to step 2

2. **Detect scope, then install:**

   ```bash
   [ -e ~/.agents/skills/google-stitch-skills ] && echo "global" || echo "project"
   ```

   **Global:**
   ```bash
   npx skills add google-labs-code/stitch-skills -g -y
   ```

   **Project:**
   ```bash
   npx skills add google-labs-code/stitch-skills -y
   ```
   > **Claude Code:** send a command as a chat message starting with `!` to run it without leaving the conversation.

**Heads-up**

- **Requires:** Stitch MCP server configured with its credentials (Stitch MCP setup guide: https://stitch.withgoogle.com/docs/mcp/setup/); upstream says the skills need it running
- **License:** Apache-2.0
- **Name collision:** `shadcn-ui` is also written by `shadcn-ui` (its install or its catalogue pointer); installing both overwrites the earlier one.
- **Name collision:** `remotion` is also written by `remotion` (its install or its catalogue pointer); installing both overwrites the earlier one.
<!-- das:install:end -->

## Invoke after install

Skills prefixed `stitch::` install into a `stitch-…` directory (for example `stitch::react-components` becomes `stitch-react-components`). Upstream says the skills depend on each other, so install the package rather than single skills.

- `stitch-loop` — "stitch loop", "iterate design"
- `design-md` — "DESIGN.md", "create design spec"
- `site-md` — a SITE.md project constitution for the Stitch build loop
- `enhance-prompt` — "enhance my prompt", "improve UI prompt"
- `taste-design` — a DESIGN.md that enforces premium, anti-generic UI standards
- `stitch::generate-design` — generate and edit screens and variants through the Stitch MCP
- `stitch::manage-design-system` — manage Stitch design systems and apply them to screens
- `stitch::extract-design-md` (installed as `stitch-extract-design-md`) — "extract design md", "Stitch to DESIGN.md"
- `stitch::react-components` (installed as `stitch-react-components`) — "Stitch to React", "convert to React"
- `stitch::react-native` (installed as `stitch-react-native`) — Stitch HTML to React Native components
- `react-vite-dashboard` — Stitch designs to React + Vite dashboards
- `shadcn-ui` — "Stitch to shadcn", "build with shadcn"
- `remotion` — walkthrough videos from Stitch projects
- `stitch::code-to-design`, `stitch::extract-static-html`, `stitch::upload-to-stitch` — move existing web code into a Stitch project

## What it does

Google Labs' official Stitch skill collection for the complete design-to-code pipeline: manages DESIGN.md and SITE.md specification files, enhances prompts with UI/UX vocabulary, generates and edits Stitch screens, converts Stitch output to React, React Native or shadcn/ui components, extracts design specs, uploads existing code into Stitch, and runs iterative improvement loops. The skills drive the Stitch MCP server.

Upstream also recommends its plugin suite (`npx plugins add google-labs-code/stitch-skills --scope project --target claude-code`); the command above installs the same skills without plugin packaging.

## When NOT to use

- Designs that do not live in Google Stitch — use `figma-official-skills` for Figma, or `design-consultation` to build a design system from scratch
- Only the shadcn/ui component workflow, not the Stitch pipeline — use the official `shadcn-ui` stub; this package installs a different (Stitch-specific) skill into the directory `shadcn-ui`, the same name the catalogue pointer for that stub uses, so installing both overwrites one
- Only the Remotion video workflow — use the `remotion` stub; the Stitch `remotion` skill is Stitch-specific and installs into a directory with the same name as that stub

© podo · MIT · podo/design-agent-skills

Similar skills

All skills for Design →

From the same set108

The whole set →
assimovt-productskills assimovt-productskills is a Claude Code skill with 16 product management skills for discovery, prioritization, planning, and experiment design. CX Codex +1 209installs huashu-design huashu-design builds interactive HTML prototypes, slide decks, and animations right inside your agent. It offers three visual directions first and exports files to PPTX, PDF, MP4, and GIF. CX Codex +1 208installs expo-skills A suite of 25 skills for Expo and EAS development, covering Expo Router, native modules, SDK upgrades, and cloud builds. CX Codex +1 207installs coreyhaines-marketing coreyhaines-marketing — a pointer skill that pulls three Corey Haines CRO skills into your agent: cro, onboarding and signup. CX Codex +1 207installs cloudai-threejs cloudai-threejs is a Claude Code skill covering Three.js, WebGL, WebGPU/TSL, and React Three Fiber for building 3D scenes, shaders, and animations without deprecated patterns. CX Codex +1 207installs platform-design-skills platform-design-skills is a Claude Code skill for creating and reviewing interfaces against Apple HIG, Material Design 3, and WCAG 2.2. It includes guidance for eight platforms. CX Codex +1 207installs frontend-slides frontend-slides builds animated HTML presentations from scratch or turns PPT/PPTX files into browser slides. Useful for decks that need a fixed stage and smooth transitions. CX Codex +1 207installs swiftui-claude-skills Eight SwiftUI skills covering iOS 26 Liquid Glass, HIG design audits, SwiftData, and on-device Foundation Models. Built for Xcode 26.3 workflows in Claude Code. CX Codex +1 207installs

Project sponsors

Companies that keep this analytics open