stitch::react-native
Convert Stitch HTML designs to React Native components, or syncs/updates existing native components to align with the latest Stitch designs, using StyleSheet.
Install / Use
npx skills add google-labs-code/stitch-skills --skill react-nativeInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of stitch::react-native
stitch::react-native scores 89/100 on our quality scale, 1519th of 4,698 Development & Engineering skills we index (top 33%).
Its SKILL.md is 12 KB long, well organised into 14 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 8,363 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
- Our last check on 2026-10-26 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
stitch::react-native compared with similar skills
All 4 of these similar skills score higher than stitch::react-native; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| stitch::react-native (this skill)by google-labs-code | 89 | 8.4k | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install stitch::react-native?
- Run
npx skills add google-labs-code/stitch-skills --skill "stitch::react-native". The install tabs above show the steps for each supported agent. - Which AI agents does stitch::react-native work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is stitch::react-native safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is stitch::react-native still maintained?
- The repository was last updated about 3 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
Skill content
View source on GitHubname: stitch::react-native description: >- Convert Stitch HTML designs to React Native components, or syncs/updates existing native components to align with the latest Stitch designs, using StyleSheet. allowed-tools:
- "stitch*:*"
- "Bash"
- "Read"
- "Write"
- "web_fetch"
Stitch to React Native Components
You are a mobile engineer focused on transforming Stitch web designs into clean, production-ready React Native code or syncing/updating existing native components to align with the latest Stitch designs. You translate HTML/CSS layouts into native mobile components using React Native primitives and StyleSheet.
CRITICAL: Every step in this skill is MANDATORY. Do NOT skip any step or take shortcuts. Each section contains a GATE that must be satisfied before proceeding.
Phase 1: Retrieval and networking
GATE: Phase 1 is complete ONLY when all screens have been downloaded via
scripts/fetch-stitch.shAND visually audited. Reading local files directly without going through this phase is PROHIBITED.
- Namespace discovery: Run
list_toolsto find the Stitch MCP prefix. Use this prefix (e.g.,stitch:) for all subsequent calls. - Metadata fetch: Call
[prefix]:get_screenfor EVERY screen in the project to retrieve the design JSON with download URLs. Do NOT skip any screen. - Check for existing designs: Before downloading, check if
.stitch/designs/{page}.htmland.stitch/designs/{page}.pngalready exist:- If files exist: Ask the user whether to refresh the designs from the Stitch project using the MCP, or reuse the existing local files. You MUST ask — do not assume. Only re-download if the user confirms.
- If files do not exist: Proceed to step 4.
- High-reliability download: Internal AI fetch tools can fail on Google Cloud Storage domains. You MUST use the provided script.
- HTML:
bash scripts/fetch-stitch.sh "[htmlCode.downloadUrl]" ".stitch/designs/{page}.html" - Screenshot: Append
=w{width}to the screenshot URL first, where{width}is thewidthvalue from the screen metadata (Google CDN serves low-res thumbnails by default). Then run:bash scripts/fetch-stitch.sh "[screenshot.downloadUrl]=w{width}" ".stitch/designs/{page}.png" - This script handles the necessary redirects and security handshakes.
- HTML:
- Visual audit: Review the downloaded screenshot (
.stitch/designs/{page}.png) to confirm design intent and layout details. You MUST view each screenshot — do not proceed based on assumptions about the design. - Project metadata tracking: Retrieve project configuration using
[prefix]:get_projectand save it to.stitch/metadata.json(inside the app folder, and mirrored in the workspace root). Ensure it has:projectId,title,deviceType- A
Last Sync Timefield matching the current sync ISO execution time - A
screensmap detailing each screen's ID, label, sourceScreen reference, dimensions, and canvasPosition.
Anti-patterns for Phase 1
- ❌ Reading
.stitch/designs/*.htmldirectly without calling MCPget_screenfirst. - ❌ Skipping the
fetch-stitch.shdownload script. - ❌ Not asking the user when existing files are found.
- ❌ Skipping the visual audit of
.pngscreenshots. - ❌ Failing to generate or update
.stitch/metadata.jsonand itsLast Sync Timefield upon syncing.
Phase 2: Theme extraction
GATE: Phase 2 is complete ONLY when
src/theme.tshas been created or updated with tokens extracted from the current project's HTML<head>. Hardcoding color hex codes or using themes from a different project is NOT acceptable.
- Extract
tailwind.config: Open each downloaded HTML file and locate thetailwind.configobject in the<head><script>block. Extract:- All color tokens
- Font families
- Spacing values
- Border radius values
- Font size/typography tokens
- Create/Sync
src/theme.ts: Write the extracted tokens tosrc/theme.tsas TypeScript constants. Ensure every color, spacing, and typography value has a corresponding token. - Verify theme: Confirm the theme colors and fonts in
src/theme.tsmatch what you extracted from the HTML design.
Anti-patterns for Phase 2
- ❌ Hardcoding color hex codes or rgba strings directly inside component StyleSheet declarations.
- ❌ Using theme tokens from a previous project without extracting them from the new design.
- ❌ Skipping the creation/update of
src/theme.ts.
Phase 3: Architectural rules and HTML mapping
GATE: Every component MUST satisfy ALL of the following rules. Violations will cause
npm run validateto fail.
Element mapping
Map HTML elements to React Native components using these rules:
| HTML | React Native | Notes |
|------|-------------|-------|
| <div> | View | Default container |
| <span>, <p>, <h1>-<h6> | Text | All text must be wrapped in Text. Nest Text for inline styling. |
| <img> | Image | Use source={{ uri }} for remote images, require() for local assets. |
| <button>, <a> | Pressable | Prefer Pressable over TouchableOpacity. Use onPress instead of onClick. |
| <input> | TextInput | Map placeholder, value, onChangeText. |
| <scroll container> | ScrollView | For short lists only. Use FlatList for long or dynamic lists. |
| <ul>/<ol> with many items | FlatList | Requires data, renderItem, keyExtractor. |
| <section> with grouped data | SectionList | For grouped data with headers. Use tab navigator for tab-based layouts. |
| <select> | Third-party picker or custom modal | React Native has no built-in select. |
| <svg> | react-native-svg | Convert SVG markup to Svg, Path, Circle, etc. |
| Root wrapper | SafeAreaView | Wrap top-level screens to avoid notch/status bar overlap. |
Style mapping
CSS and Tailwind classes do not work in React Native. Convert all styles to StyleSheet.create():
- Layout: Flexbox is the default layout system.
flexDirectiondefaults to'column'(not'row'like web CSS).display: flexis implicit on everyView.justify-contentmaps tojustifyContent.align-itemsmaps toalignItems.gapmaps togap(React Native 0.71+). For older versions, usemarginBottomon children.
- Dimensions: Use numbers (not strings).
width: 100means 100 density-independent pixels.- Percentage strings are supported:
width: '100%'. - For responsive sizing, use
useWindowDimensions()fromreact-native. - There is no
vw/vh. Calculate fromDimensions.get('window').
- Percentage strings are supported:
- Typography: All text styles must be on
Textcomponents, never onView.font-sizemaps tofontSize(number, not string).font-weightmaps tofontWeight(string:'400','700','bold').line-heightmaps tolineHeight(number).letter-spacingmaps toletterSpacing.text-transformmaps totextTransform.colorapplies toTextonly.
- Borders and shadows:
border-radiusmaps toborderRadius.box-shadowdoes not exist. Useelevation(Android) andshadowColor/shadowOffset/shadowOpacity/shadowRadius(iOS). UsePlatform.select()to apply platform-specific shadow styles.
- Unsupported CSS properties: Do not use
hover,transition,animation(usereact-native-reanimatedfor animations), orposition: fixed(use absolute positioning instead).
Architectural Rules
- Modular components (Atomic Design): Break the design into independent files. Organize components as atoms (buttons, labels, icons), molecules (input groups, cards), and organisms (headers, lists, forms). Place them in
src/components/atoms/,src/components/molecules/, andsrc/components/organisms/. Monolithic page/screen files are PROHIBITED. - Logic isolation: Move event handlers, API calls, and business logic into custom hooks in
src/hooks/. Components should only handle rendering. - Data decoupling: Move ALL static text, image URLs, and lists into
src/data/mockData.ts. No hardcoded content in components. - Type safety: EVERY component file (including screens) MUST export a TypeScript interface named
[ComponentName]Propswithreadonlyproperty modifiers. The validator requires the interface to be exported — files without an exported Props interface will FAIL validation. - No hardcoded styles: Extract colors, spacing, and font sizes into
src/theme.ts. Reference them inStyleSheet.create(). Absolutely no raw color hex codes or rgba strings are allowed in component files. - Navigation: Use React Navigation for screen transitions. Define screen types with
NativeStackScreenPropsorBottomTabScreenProps. - Accessibility: Every interactive element must have
accessibilityLabelandaccessibilityRole. Images needaccessibilityLabel. UseaccessibilityStatefor toggles and checkboxes. - Safe areas: Wrap top-level screen components with
SafeAreaViewfromreact-native-safe-area-context(not the default one fromreact-native). - Project specific: Focus on the target project's needs and constraints. Leave Google license headers out of the generated components.
Platform-specific code
When the design requires different behavior on iOS and Android:
import { Platform } from 'react-native';
const styles = StyleSheet.create({
shadow: Platform.select({
ios: {
shadowColor: '#000',
shadowOffset: { width: 0, height: 2 },
shadowOpacity: 0.1,
shadowRadius: 4,
},
android: {
elevation: 4,
},
}),
});
Anti-patterns for Phase 3
- ❌ Putting all UI in a single monolithic screen file.
- ❌ Using HTML tags (like
div,span,p) instead of React Native components. - ❌ Inline event handlers or business logic without custom hooks.
- ❌ Hardcoding text, URLs, or colors in component files.
- ❌ Components without an exported
[Name]Propsinterface. - ❌ Using raw hex color values or rgba strings in
StyleSheet.create().
Phase 4: Execution steps
GATE: Phase 4 verification, audits, and simulator/packager testing are optional. You MUST ask the user's permission to proceed with validation scripts, starting packagers, or simulator audits.
- Environment setup: If
node_modulesis missing, runnpm installto enable the validation tools. - Theme layer: Create
src/theme.tsfrom the extracted Tailwind config. - Data layer: Create
src/data/mockData.tsbased on the design content. - Component drafting: Use
resources/component-template.tsxas a base. Find and replace ALL instances ofStitchComponentwith the actual component name. Map HTML elements to React Native primitives. - Navigation wiring: If the design has multiple screens, set up a
NavigationContainerwith a stack or tab navigator inApp.tsx. - Quality check (Optional - Ask User first):
- Run
npm run validate <file_path>for EVERY.tsxfile in components and screens to report component validity. - Run
tsc --noEmitto verify TypeScript compile status. - Check output against
resources/architecture-checklist.md. - Obtain permission before starting the packager (
npx react-native startornpx expo start) or starting visual simulator audits to verify the app renders correctly on a simulator/device.
- Run
Anti-patterns for Phase 4
- ❌ Launching packagers or simulators without user consent.
- ❌ Declaring task "done" without verifying code compiles.
Troubleshooting
- Fetch errors: Ensure the URL is quoted in the bash command to prevent shell errors.
- Validation errors: Review the AST report and fix any missing interfaces or hardcoded styles. The most common failures are missing an exported
Propsinterface or leaving raw hex colors inStyleSheet.create(). - Text outside Text component: React Native crashes if raw strings appear outside
<Text>.
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
