研究检索external-servicegithub未标认证来源可访问许可证需确认审计提醒

stitch-react-components（stitch React 组件）

Agent Skill

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码，整理组件结构，或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式，避免只生成孤立片段；涉及页面改动时，应配合本地预览和构建检查确认视觉效果。

总安装

582

周安装

GitHub Stars

下载量

190

CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：stitch-react-components（stitch React 组件）
来源仓库：https://github.com/gabelul/stitch-kit
仓库路径：skills/stitch-react-components
安装命令：
npx skills add https://github.com/gabelul/stitch-kit --skill stitch-react-components
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills

npx skills add https://github.com/gabelul/stitch-kit --skill stitch-react-components

简介

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。

它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码，整理组件结构，或定位布局和性能问题。
使用时需要结合项目现有设计系统、路由和构建方式，避免只生成孤立片段。
涉及页面改动时，应配合本地预览和构建检查确认视觉效果。
stitch-react-components 属于研究检索类 Skill，可作为该场景下的辅助能力补充。

SKILL.md

Stitch → Vite / React Components

Constraint: Only use this skill when the user explicitly mentions "Stitch" and React (Vite, CRA, or just "React app" without Next.js).

You are a frontend engineer converting Stitch mobile/desktop designs into clean, modular React components using Vite + TypeScript. This skill targets plain React apps — not Next.js App Router. For Next.js, use stitch-nextjs-components instead.

When to use this skill vs. Next.js

Scenario	Use
User says "React app", "Vite", "CRA"	`stitch-react-components`
User says "Next.js", "App Router", "SSR"	`stitch-nextjs-components`
User wants shadcn/ui components added after	`stitch-react-components` → then `stitch-shadcn-ui`
User wants server-side rendering or file-based routing	`stitch-nextjs-components`

Prerequisites

Stitch MCP Server configured (or use downloaded HTML directly)
Node.js + npm/pnpm
Vite + React project initialized: npm create vite@latest my-app -- --template react-ts

Step 1: Retrieve the design

Run list_tools → find Stitch MCP prefix
Call [prefix]:get_screen with numeric projectId and screenId
Download HTML: bash scripts/fetch-stitch.sh "[htmlCode.downloadUrl]" "temp/source.html"
Check screenshot.downloadUrl — verify layout matches expectations

Step 2: Project structure

src/
├── components/           ← One file per component
│   └── [Name].tsx
├── data/
│   └── mockData.ts       ← Static content (never in components)
├── theme/
│   ├── tokens.ts         ← Design token constants
│   └── useTheme.ts       ← Dark mode hook
├── types/
│   └── index.ts          ← Shared TypeScript types
├── App.tsx               ← Root component
└── main.tsx              ← Entry point

Step 3: Extract design tokens

From the Stitch HTML <head>, find the tailwind.config or CSS variable definitions.

// src/theme/tokens.ts — extract hex values from Stitch HTML
export const lightTokens = {
  background: '#FFFFFF',
  surface:    '#F4F4F5',
  primary:    '#6366F1',
  primaryFg:  '#FFFFFF',
  text:       '#09090B',
  textMuted:  '#71717A',
  border:     '#E4E4E7',
} as const

export const darkTokens = {
  background: '#09090B',
  surface:    '#18181B',
  primary:    '#818CF8',
  primaryFg:  '#09090B',
  text:       '#FAFAFA',
  textMuted:  '#A1A1AA',
  border:     '#27272A',
} as const

export type ThemeTokens = typeof lightTokens

// src/theme/useTheme.ts
import { useEffect, useState } from 'react'
import { lightTokens, darkTokens, type ThemeTokens } from './tokens'

/**
 * Returns current theme tokens based on system color scheme.
 * Listens for system-level dark/light mode changes.
 */
export function useTheme(): ThemeTokens {
  const [isDark, setIsDark] = useState(
    () => window.matchMedia('(prefers-color-scheme: dark)').matches
  )

  useEffect(() => {
    const mq = window.matchMedia('(prefers-color-scheme: dark)')
    const handler = (e: MediaQueryListEvent) => setIsDark(e.matches)
    mq.addEventListener('change', handler)
    return () => mq.removeEventListener('change', handler)
  }, [])

  return isDark ? darkTokens : lightTokens
}

Step 4: Component conversion rules

Layout mapping

HTML/CSS	→ React / Tailwind
`display:flex; flex-direction:column`	`<div className="flex flex-col gap-4">`
`display:flex; flex-direction:row`	`<div className="flex items-center gap-2">`
`justify-content:space-between`	`<div className="flex justify-between">`
`display:grid; grid-template-columns:1fr 1fr`	`<div className="grid grid-cols-2 gap-4">`
`overflow-y:scroll`	`<div className="overflow-y-auto">`
Long list	`items.map(item => <Card key={item.id} {...item} />)`
`<img>`	`<img src="..." alt="..." className="object-cover">`

Tailwind class mapping

Use the Stitch HTML classes directly in JSX where they don't reference Stitch-specific tokens. Map Stitch tokens to CSS variables:

// Stitch HTML: bg-primary → CSS variable → Tailwind arbitrary value
// OR: use inline style with token value

// Option A — Tailwind arbitrary value (if custom tokens in tailwind.config)
<div className="bg-[--color-primary] text-[--color-primaryFg]">

// Option B — inline style with useTheme()
const theme = useTheme()
<div style={{ backgroundColor: theme.primary, color: theme.primaryFg }}>

Component template

// src/components/StitchComponent.tsx

/**
 * Props for StitchComponent — all data via props, never fetched inside.
 */
interface StitchComponentProps {
  /** Primary heading text */
  title: string
  /** Supporting description — optional */
  description?: string
  /** Primary action callback */
  onAction?: () => void
}

/**
 * StitchComponent — [describe purpose in one sentence]
 */
export function StitchComponent({
  title,
  description,
  onAction,
}: Readonly<StitchComponentProps>) {
  const theme = useTheme()

  return (
    <div
      className="rounded-xl border p-4 gap-2 flex flex-col"
      style={{
        backgroundColor: theme.surface,
        borderColor: theme.border,
      }}
    >
      <h3 className="text-base font-semibold" style={{ color: theme.text }}>
        {title}
      </h3>

      {description ? (
        <p className="text-sm" style={{ color: theme.textMuted }}>
          {description}
        </p>
      ) : null}

      {onAction ? (
        <button
          onClick={onAction}
          className="rounded-lg px-4 py-2 text-sm font-medium transition-opacity hover:opacity-90"
          style={{ backgroundColor: theme.primary, color: theme.primaryFg }}
          type="button"
        >
          Action
        </button>
      ) : null}
    </div>
  )
}

Step 5: Architectural rules

One component per file — no single-file spaghetti
Static data in src/data/mockData.ts — never hardcoded in JSX
Shared types in src/types/index.ts
Every component has Readonly<ComponentNameProps> interface
No hardcoded hex colors — use useTheme() or CSS variables
No any types

Step 6: Integration with shadcn/ui

After converting the Stitch design to base React components, you can layer in shadcn/ui:

npx shadcn@latest init    # Set up shadcn in your Vite project
npx shadcn@latest add button card input dialog

Then use stitch-shadcn-ui skill to replace raw HTML elements with shadcn components while preserving the Stitch design tokens.

Troubleshooting

Issue	Fix
Tailwind classes not applying	Check `tailwind.config.js` includes `./src/*/.{ts,tsx}` in content
Dark mode not toggling	Verify `useTheme()` is called at component level, not hoisted
Images not showing	Add explicit `width` and `height` or use `className="w-full h-auto"`
Type error on props	Ensure `Readonly<>` wrapper and all required props are provided

References

resources/component-template.tsx — Boilerplate component
resources/architecture-checklist.md — Pre-ship checklist
references/tailwind-to-react.md — Token + class mapping guide (Stitch HTML → React/Tailwind)
scripts/fetch-stitch.sh — Reliable GCS HTML downloader
stitch-shadcn-ui — Add shadcn/ui components after base conversion
docs/tailwind-reference.md — Tailwind utility class lookup

适合场景

用户想查找某类 Agent Skill 时

需要根据任务场景推荐可安装能力包时

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.05%

按下载量换算70

Claude

29.38%

按下载量换算56

Cursor

19.72%

按下载量换算37

Gemini CLI

9.99%

按下载量换算19

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

可疑

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API，使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果，不能写成本站确认安全。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/gabelul/stitch-kit

SKILL.md 来源

github.com

/gabelul/stitch-kit/tree/main/skills/stitch-react-components

skills-sh

skills.sh

/gabelul/stitch-kit/stitch-react-components

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

stitch-orchestrator（缝合编排器）

stitch-orchestrator 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

stitch-react-native-components（stitch React native 组件）