[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C52CNEAH6HZ5YN3TBMS6ZY":3,"skill-same:01M7C52CNEAH6HZ5YN3TBMS6ZY":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M7C52CNEAH6HZ5YN3TBMS6ZY","stitch-design",null,"Use Google Stitch for design-to-code prototypes\u002Ftokens, then implement. Triggers: Stitch, screen prototypes.","EtanHey\u002Fgolems","EtanHey","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93338119?v=4","01M7C4SKC9HJC3B9TAX0D9MZ1E","Etan Heyman","01M7C4SKCT59Z49TTN4WWDDEYD",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FEtanHey\u002Fgolems\u002Fblob\u002Fmaster\u002Fskills\u002Fgolem-powers\u002Fstitch-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: stitch-design\ndescription: \"Use Google Stitch for design-to-code prototypes\u002Ftokens, then implement. Triggers: Stitch, screen prototypes.\"\nversion: 0.3.0\ntype: encoded-preference\ntriggers:\n  - stitch\n  - implement this design\n  - implement the design\n  - match this design\n  - generate a screen\n  - design system\n  - design tokens\n  - the product team's design\n  - warning screen\n  - extract colors from stitch\n---\n\n# Stitch Design — Read, Prompt, Grill, Implement\n\n> Claude = **prompt engineer** for Stitch. Stitch = **design generator**.\n> Claude understands the flow, the design system, the user's intent — then writes a detailed prompt that Stitch executes. Claude does NOT design. Stitch does.\n\n## The Flow\n\n```\nSYNC     →  Push app's theme (colors.ts, typography.ts) into Stitch's designMd field\nREAD     →  Pull existing admin designs (get_screen → screenshot URL + htmlCode, list_design_systems)\nPROMPT   →  Craft detailed prompts for Stitch to generate new screens WITHIN the design system\nGRILL    →  Ask user about behavior, flow, states, edge cases (Stitch = static, app = dynamic)\nIMPLEMENT → Build in React Native, matching Stitch visuals + wired behavior\n```\n\n## When This Skill Activates\n\n- Product\u002Fdesign teammates share a new design (screenshot or Stitch URL)\n- User says \"implement this design\" or \"match this screen\"\n- User wants to generate a new screen prototype in Stitch\n- User wants to extract design tokens for app theme sync\n- User asks about a specific Stitch screen's layout\u002Fcolors\u002Ffonts\n\n## Key Constraint\n\n**Always use the existing design system.** The target project has established colors, fonts, and theme tokens. When generating new screens:\n- Read the reference screen with the configured Stitch MCP's supported tools FIRST\n- Manually carry its colors, typography, spacing, and component patterns into `generate_screen_from_text`\n- Never invent new colors, fonts, or styles outside the system\n\n**The `designMd` field is the bridge.** This free-text field in the design system tells Stitch HOW to generate. Claude writes `designMd` from the target codebase (existing colors, fonts, components, and layout patterns) and pushes it to Stitch via `update_design_system`. This makes Stitch generations match the app automatically.\n\n## Example Design Context\n\n- **App:** ExampleApp (fictional React Native\u002FExpo consumer app)\n- **Designers:** Product owner + visual designer\n- **Design tool:** Google Stitch (stitch.withgoogle.com)\n- **Two Stitch projects:**\n  - **Shared:** `$STITCH_SHARED_PROJECT_ID` — source of truth, READ from here\n  - **Ours (remixed):** `$STITCH_REMIX_PROJECT_ID` — experiment\u002Fgenerate here\n  - Project IDs are deployment values and live only in gitignored env; never commit them.\n- **Screens (ours):** 4 — 3x \"Warning Screen Protection Off\" + 1x DNS setup mockup\n- **Color discrepancy:** Shared and app tokens may differ. The SYNC workflow aligns the remix.\n- **Theme:** Dark purple (#8B5CF6 primary, #0A0A1A background), DARK mode, system fonts (Inter\u002FDM Sans in Stitch only), round-12 corners\n- **Language:** Hebrew RTL\n- **Communication:** Teammates share designs via screenshots or Stitch links\n\n## Stitch MCP Config\n\nConfigure Stitch in `${APP_REPO_ROOT}\u002F.mcp.json`. Run `\u002Fmcp` to connect. Tools appear as `mcp__stitch__*`.\n\n## Stitch MCP Tools\n\n### ACTUAL Stitch MCP Tools (verified live April 6)\n\n**READ tools:**\n\n| Tool | What | When |\n|------|------|------|\n| `list_projects` | List all Stitch projects | Boot — find project ID |\n| `get_project` | Get project metadata | Verify project details |\n| `list_screens` | List screens in a project | See what designs exist |\n| `get_screen` | Get screen details + screenshot URL + htmlCode | **THE main read tool** — returns title, dimensions, downloadUrl, htmlCode |\n| `list_design_systems` | Read current design system | Verify theme tokens |\n\n**GENERATE tools (Claude = prompt engineer, Stitch = renderer):**\n\n| Tool | What | When |\n|------|------|------|\n| `generate_screen_from_text` | Generate screen from Claude's prompt | New screens — always use design system context |\n| `edit_screens` | Modify a screen with instructions | Iterate on a generated prototype |\n| `generate_variants` | Produce design variations | Explore options within the design system |\n\n**SYNC tools (bridge code ↔ design):**\n\n| Tool | What | When |\n|------|------|------|\n| `create_design_system` | Create design system with designMd | First-time setup |\n| `update_design_system` | Push updated designMd to Stitch | After app theme changes |\n| `apply_design_system` | Apply design system to screens | Propagate style changes |\n\n**Other:**\n\n| Tool | What | When |\n|------|------|------|\n| `create_project` | Create a new Stitch project | Only if starting from scratch |\n\n### Tools That DON'T Exist (corrected from research)\n\nThese were listed in community wrapper docs but are NOT in Google's official MCP:\n- ~~`get_screen`~~ → use `get_screen` (returns screenshot.downloadUrl)\n- ~~`get_screen_code`~~ → use `get_screen` (returns htmlCode)\n- ~~`extract_design_context`~~ → NOT available upstream. Read colors manually from get_screen htmlCode.\n- ~~`build_site`~~ → NOT in official MCP\n\n---\n\n## Workflow 0: SYNC — Bridge Code to Design System\n\n**Run this FIRST in any new project or after theme changes.** This writes the app's design reality into Stitch's `designMd` field so all generations match the app.\n\n```\n1. Read app theme files:\n   - app\u002Ftheme\u002Fcolors.ts → extract all color constants\n   - app\u002Ftheme\u002Ftypography.ts → extract font families, sizes, weights\n   - Scan components\u002F for common patterns (border radius, spacing, shadows)\n2. Read RTL patterns:\n   - Check I18nManager usage, writingDirection props\n   - Note which components handle RTL explicitly\n3. Craft designMd string from the ACTUAL app theme:\n   \"ExampleApp — fictional Hebrew RTL mobile app. Dark theme.\n   Colors: primary #8B5CF6, secondary #6366F1, accent #A855F7.\n   Backgrounds: #0A0A1A deepSpace (main), #150B2E midnight (secondary), #2A1B4E cosmic (cards).\n   Text: #FFFFFF white, #94A3B8 gray secondary. Gradients: #8B5CF6→#6366F1→#4F46E5.\n   Status: #10B981 green, #EF4444 red, #F59E0B amber. Blue borders #4F46E5.\n   Layout: RTL-first, bottom-anchored CTAs, shield icon for protection states.\n   Typography: sizes 12\u002F14\u002F16\u002F20\u002F28px, weights 400-700. Rank colors: green→blue progression.\"\n4. Push to Stitch:\n   update_design_system(projectId, { designSystem: { theme: { designMd: \"...\" } } })\n5. Verify: list_design_systems → confirm designMd is set\n```\n\n**designMd is the single most important field.** It's free-text that Stitch reads before every generation. A good designMd = every generated screen matches the app without manual adjustment.\n\n## Workflow 1: READ — Understand the Design\n\nWhen a teammate shares a new design or points to a Stitch screen:\n\n**READ from the shared source of truth. GENERATE in the remix project.**\n\n```\n1. list_screens(projectId: \"projects\u002F${STITCH_SHARED_PROJECT_ID}\") → shared designs (source of truth)\n2. get_screen(screenName) → returns:\n   - title, width, height\n   - screenshot.downloadUrl (Google CDN link to PNG)\n   - htmlCode (the design's HTML\u002FCSS)\n3. Download the screenshot URL with WebFetch or save for visual reference\n4. Parse htmlCode for colors, fonts, layout structure\n5. list_design_systems → read current theme tokens (colorMode, fonts, roundness)\n\nOutput: You now know WHAT it looks like. You do NOT know HOW it behaves.\n```\n\n**If a teammate shared a screenshot instead of a Stitch link:**\n1. Save the screenshot locally\n2. `list_screens` → scan screen names for a match\n3. `get_screen` for each candidate → compare title\u002Fdimensions\n4. If no match in Stitch: implement directly from the screenshot\n\n## Workflow 2: PROMPT — Generate New Screens via Stitch\n\nClaude = prompt engineer. Stitch = design generator. Claude crafts detailed, context-rich prompts. Stitch renders them.\n\n```\n1. `get_screen(referenceScreenId)` → inspect screenshot and HTML for existing \"design DNA\"\n2. Understand what the user wants: \"I need a settings screen\" or \"add a premium paywall\"\n3. Craft a detailed prompt for Stitch:\n\n   GOOD PROMPT:\n   \"Settings screen for a fictional Hebrew RTL mobile app. Dark background\n   with subtle gradient. Inter font throughout. Cards for each setting group: \n   'הגדרות חשבון' (account), 'התראות' (notifications), 'פרטיות' (privacy).\n   Toggle switches with purple active state. Bottom navigation bar visible.\n   Shield icon in header. 12px border radius on all cards. Match the visual style\n   of the existing warning screens.\"\n\n   BAD PROMPT:\n   \"Make a settings page\"\n\n4. generate_screen_from_text(prompt) → Stitch renders the design\n5. get_screen(generatedScreenName) → review screenshot.downloadUrl\n6. If not right: edit_screens with specific corrections, or re-prompt\n7. If exploring options: generate_variants for alternatives\n```\n\n**Prompt engineering tips for the example app:**\n- Always specify \"Hebrew RTL\" and exact hex colors\n- Reference existing screens by name for style consistency\n- Include specific Hebrew text for realistic previews\n- Describe layout in screen positions (\"top\", \"bottom-anchored\"), not DOM order\n- Mention the shield icon, gradient backgrounds, and countdown timers as recurring elements\n\n## Workflow 3: GRILL — Ask About Behavior\n\nStitch shows STATIC designs. The app has DYNAMIC behavior. You MUST ask:\n\n**For every screen, ask these questions:**\n\n```\nFLOW QUESTIONS:\n- \"What happens when the user taps [button]?\"\n- \"Where does this screen appear in the navigation flow?\"\n- \"What screen comes before this? What comes after?\"\n- \"Is there a countdown\u002Ftimer? What happens when it ends?\"\n\nSTATE QUESTIONS:\n- \"What does this screen look like in [other state]?\" (loading, error, empty)\n- \"Can the user go back from here?\"\n- \"What if the user is not premium?\"\n- \"Does this need to work offline?\"\n\nDATA QUESTIONS:\n- \"Where does [this text\u002Fnumber] come from?\" (hardcoded, API, local state)\n- \"Is this text translated or always Hebrew?\"\n- \"Does this update in real-time?\"\n\nEDGE CASES:\n- \"What if the user rotates the phone?\"\n- \"What if the text is longer than expected?\"\n- \"What about accessibility — VoiceOver labels?\"\n```\n\n### Synthetic Example: Confirmation Flow\n\nThe static design shows a confirmation screen. GRILL uncovers behavior the pixels cannot encode:\n- a short countdown before the confirmation button activates\n- a long press to confirm the action\n- dynamic status data from the application state\n- all copy is localized — never hardcode text\n\nThe Stitch design showed NONE of this — just a static screen. The GRILL workflow extracted the flow.\n\n**Ask 2-3 at a time.** Don't dump all questions at once. Drill based on answers.\n\n**Store answers:** `brain_store` the flow decisions with tags `[\"example-app\", \"design-flow\", screenName]`. These persist across sessions — next time someone implements from this screen, the flow answers are already in BrainLayer.\n\n## Workflow 4: IMPLEMENT — Build in React Native\n\nOnce you have the visual (from READ) and the behavior (from GRILL):\n\n```\n1. get_screen(screenName) → HTML\u002FCSS reference\n2. Map HTML structure to React Native:\n   - div → View\n   - p\u002Fspan → Text\n   - img → Image (or Expo Image)\n   - button → Pressable\u002FTouchableOpacity\n   - CSS flexbox → RN flexbox (same API)\n   - CSS colors → theme\u002Fcolors.ts constants\n   - CSS fonts → theme\u002Ftypography.ts\n   - px values → responsive units\n3. RTL handling (CRITICAL for Hebrew):\n   - flexDirection: 'row' is REVERSED in RTL\n   - textAlign: 'right' for Hebrew content\n   - writingDirection: 'rtl' on Text components\n   - Mirror directional icons (arrows, chevrons)\n   - I18nManager.isRTL for conditional logic\n4. Wire behavior from GRILL answers:\n   - Navigation (router.push\u002Freplace\u002Fback)\n   - State management (useState, Convex queries)\n   - Timers (useEffect + cleanup)\n   - Animations (Reanimated or LayoutAnimation)\n5. Screenshot implementation → compare side-by-side with Stitch\n```\n\n### HTML → React Native Cheat Sheet\n\n```\nSTITCH HTML\u002FCSS                     →  REACT NATIVE\n──────────────────────────────────────────────────────\n\u003Cdiv class=\"flex flex-col\">         →  \u003CView style={{ flexDirection: 'column' }}>\nbackground: #8B5CF6                 →  backgroundColor: colors.primary\nfont-family: Inter                  →  fontFamily: typography.heading.fontFamily\nborder-radius: 12px                 →  borderRadius: 12\npadding: 16px                       →  padding: 16\nbox-shadow: ...                     →  elevation: 4 (Android) \u002F shadowColor (iOS)\nbackground: linear-gradient(...)    →  \u003CLinearGradient> (expo-linear-gradient)\nposition: fixed                     →  position: 'absolute' (RN has no fixed)\noverflow: scroll                    →  \u003CScrollView>\n```\n\n## Design Token Mapping\n\n```\nSTITCH DESIGN SYSTEM                →  APP CONSTANTS (constants\u002F)\n──────────────────────────────────────────────────────\ncustomColor: \"#8B5CF6\"              →  colors.primary (#8B5CF6)\ncolorMode: \"DARK\"                   →  colors.background (#0A0A1A)\nheadlineFont: \"INTER\"               →  system default (no custom fonts in RN yet)\nbodyFont: \"INTER\"                   →  system default\nlabelFont: \"DM_SANS\"               →  system default\nroundness: \"ROUND_TWELVE\"          →  borderRadius: 12 (per component)\ncolorVariant: \"EXPRESSIVE\"         →  colors.gradient (#8B5CF6→#6366F1→#4F46E5)\ndesignMd: (our crafted text)        →  THE BRIDGE — describes all of the above to Stitch\n```\n\n**Discrepancy:** Stitch uses Inter\u002FDM Sans but the RN app uses system fonts.\nEither install custom fonts in Expo (`expo-font`) or accept the difference.\n\nWhen a supported screen\u002Fdesign-system read exposes values that differ from the app theme files, flag it:\n\"Stitch shows [X] but app\u002Ftheme\u002Fcolors.ts has [Y]. Should I update the app to match?\"\n\n## Integration Patterns\n\n| Trigger | Action |\n|---------|--------|\n| Teammate sends screenshot | READ workflow → match in Stitch → GRILL about flow → IMPLEMENT |\n| New Stitch screen appears | `list_screens` detects it → notify user → wait for implementation request |\n| Theme change in Stitch | Read screen\u002Fdesign-system data → diff with app theme → flag discrepancies |\n| PR review for UI changes | `get_screen` → compare with implementation screenshot |\n| User says \"does this match?\" | `get_screen` + app screenshot → side-by-side comparison |\n\n## i18n Rule (MANDATORY)\n\n**ALL text is i18n.** Never hardcode Hebrew or English strings in components.\n- Use translation keys: `t('warning.countdown')` not `\"רוצה לחזור אחורה?\"`\n- Stitch designs show Hebrew text — treat it as placeholder for the i18n key\n- Dynamic data comes from the application backend, not the design\n\n## RTL Rules (example app is Hebrew-first)\n\n1. **Flex order is reversed** in RTL — first child → RIGHT side of screen\n2. **Text alignment** — Hebrew = `textAlign: 'right'`, `alignItems: 'flex-end'`\n3. **Icons** — arrows\u002Fchevrons must mirror. Use `I18nManager.isRTL ? 'flip' : undefined`\n4. **Padding\u002Fmargin** — `paddingStart`\u002F`paddingEnd` instead of `paddingLeft`\u002F`paddingRight`\n5. **Stitch designs may show LTR** — Stitch defaults LTR. Mentally mirror the layout for implementation.\n\n## Gap Analysis\n\n### Community wrapper (oogleyskr\u002Fstitch-mcp-server, 36 tools)\nRead-only tools we'd benefit from:\n- `compare_designs` — diff two Stitch screens after a teammate iterates\n- `extract_components` — isolate reusable UI patterns from screens\n- `analyze_accessibility` — WCAG 2.1 check on Stitch designs before implementing\n\n### \u002Fyash candidates (things that don't exist anywhere)\n| Gap | Impact | Fix |\n|-----|--------|-----|\n| `screen_to_react_native` | HIGH — manual HTML→RN every time | Fork oogleyskr's screen_to_react, add RN output |\n| Theme.ts sync | MEDIUM — manual token copy | Build codegen from supported screen\u002Fdesign-system reads → theme.ts |\n| Stitch↔implementation diff | MEDIUM — manual screenshot comparison | Build: overlay Stitch PNG on app screenshot, highlight differences |\n\n## Files\n\n```\n${APP_REPO_ROOT}\u002F\n├── .mcp.json                       # Stitch MCP config (connected)\n├── app\u002Ftheme\u002Fcolors.ts             # App colors (sync target)\n├── app\u002Ftheme\u002Ftypography.ts         # Font definitions (sync target)\n├── app\u002Fcomponents\u002F                 # Existing RN components\n├── docs.local\u002Fstitch-mcp-reference.md  # MCP reference notes\n└── ~\u002FDesktop\u002FStitch screens\u002F       # Local screenshots (5 files, Apr 6)\n```\n","# Stitch Design — Read, Prompt, Grill, Implement\n\n> Claude = **prompt engineer** for Stitch. Stitch = **design generator**.\n> Claude understands the flow, the design system, the user's intent — then writes a detailed prompt that Stitch executes. Claude does NOT design. Stitch does.\n\n## The Flow\n\n```\nSYNC     →  Push app's theme (colors.ts, typography.ts) into Stitch's designMd field\nREAD     →  Pull existing admin designs (get_screen → screenshot URL + htmlCode, list_design_systems)\nPROMPT   →  Craft detailed prompts for Stitch to generate new screens WITHIN the design system\nGRILL    →  Ask user about behavior, flow, states, edge cases (Stitch = static, app = dynamic)\nIMPLEMENT → Build in React Native, matching Stitch visuals + wired behavior\n```\n\n## When This Skill Activates\n\n- Product\u002Fdesign teammates share a new design (screenshot or Stitch URL)\n- User says \"implement this design\" or \"match this screen\"\n- User wants to generate a new screen prototype in Stitch\n- User wants to extract design tokens for app theme sync\n- User asks about a specific Stitch screen's layout\u002Fcolors\u002Ffonts\n\n## Key Constraint\n\n**Always use the existing design system.** The target project has established colors, fonts, and theme tokens. When generating new screens:\n- Read the reference screen with the configured Stitch MCP's supported tools FIRST\n- Manually carry its colors, typography, spacing, and component patterns into `generate_screen_from_text`\n- Never invent new colors, fonts, or styles outside the system\n\n**The `designMd` field is the bridge.** This free-text field in the design system tells Stitch HOW to generate. Claude writes `designMd` from the target codebase (existing colors, fonts, components, and layout patterns) and pushes it to Stitch via `update_design_system`. This makes Stitch generations match the app automatically.\n\n## Example Design Context\n\n- **App:** ExampleApp (fictional React Native\u002FExpo consumer app)\n- **Designers:** Product owner + visual designer\n- **Design tool:** Google Stitch (stitch.withgoogle.com)\n- **Two Stitch projects:**\n  - **Shared:** `$STITCH_SHARED_PROJECT_ID` — source of truth, READ from here\n  - **Ours (remixed):** `$STITCH_REMIX_PROJECT_ID` — experiment\u002Fgenerate here\n  - Project IDs are deployment values and live only in gitignored env; never commit them.\n- **Screens (ours):** 4 — 3x \"Warning Screen Protection Off\" + 1x DNS setup mockup\n- **Color discrepancy:** Shared and app tokens may differ. The SYNC workflow aligns the remix.\n- **Theme:** Dark purple (#8B5CF6 primary, #0A0A1A background), DARK mode, system fonts (Inter\u002FDM Sans in Stitch only), round-12 corners\n- **Language:** Hebrew RTL\n- **Communication:** Teammates share designs via screenshots or Stitch links\n\n## Stitch MCP Config\n\nConfigure Stitch in `${APP_REPO_ROOT}\u002F.mcp.json`. Run `\u002Fmcp` to connect. Tools appear as `mcp__stitch__*`.\n\n## Stitch MCP Tools\n\n### ACTUAL Stitch MCP Tools (verified live April 6)\n\n**READ tools:**\n\n| Tool | What | When |\n|------|------|------|\n| `list_projects` | List all Stitch projects | Boot — find project ID |\n| `get_project` | Get project metadata | Verify project details |\n| `list_screens` | List screens in a project | See what designs exist |\n| `get_screen` | Get screen details + screenshot URL + htmlCode | **THE main read tool** — returns title, dimensions, downloadUrl, htmlCode |\n| `list_design_systems` | Read current design system | Verify theme tokens |\n\n**GENERATE tools (Claude = prompt engineer, Stitch = renderer):**\n\n| Tool | What | When |\n|------|------|------|\n| `generate_screen_from_text` | Generate screen from Claude's prompt | New screens — always use design system context |\n| `edit_screens` | Modify a screen with instructions | Iterate on a generated prototype |\n| `generate_variants` | Produce design variations | Explore options within the design system |\n\n**SYNC tools (bridge code ↔ design):**\n\n| Tool | What | When |\n|------|------|------|\n| `create_design_system` | Create design system with designMd | First-time setup |\n| `update_design_system` | Push updated designMd to Stitch | After app theme changes |\n| `apply_design_system` | Apply design system to screens | Propagate style changes |\n\n**Other:**\n\n| Tool | What | When |\n|------|------|------|\n| `create_project` | Create a new Stitch project | Only if starting from scratch |\n\n### Tools That DON'T Exist (corrected from research)\n\nThese were listed in community wrapper docs but are NOT in Google's official MCP:\n- ~~`get_screen`~~ → use `get_screen` (returns screenshot.downloadUrl)\n- ~~`get_screen_code`~~ → use `get_screen` (returns htmlCode)\n- ~~`extract_design_context`~~ → NOT available upstream. Read colors manually from get_screen htmlCode.\n- ~~`build_site`~~ → NOT in official MCP\n\n---\n\n## Workflow 0: SYNC — Bridge Code to Design System\n\n**Run this FIRST in any new project or after theme changes.** This writes the app's design reality into Stitch's `designMd` field so all generations match the app.\n\n```\n1. Read app theme files:\n   - app\u002Ftheme\u002Fcolors.ts → extract all color constants\n   - app\u002Ftheme\u002Ftypography.ts → extract font families, sizes, weights\n   - Scan components\u002F for common patterns (border radius, spacing, shadows)\n2. Read RTL patterns:\n   - Check I18nManager usage, writingDirection props\n   - Note which components handle RTL explicitly\n3. Craft designMd string from the ACTUAL app theme:\n   \"ExampleApp — fictional Hebrew RTL mobile app. Dark theme.\n   Colors: primary #8B5CF6, secondary #6366F1, accent #A855F7.\n   Backgrounds: #0A0A1A deepSpace (main), #150B2E midnight (secondary), #2A1B4E cosmic (cards).\n   Text: #FFFFFF white, #94A3B8 gray secondary. Gradients: #8B5CF6→#6366F1→#4F46E5.\n   Status: #10B981 green, #EF4444 red, #F59E0B amber. Blue borders #4F46E5.\n   Layout: RTL-first, bottom-anchored CTAs, shield icon for protection states.\n   Typography: sizes 12\u002F14\u002F16\u002F20\u002F28px, weights 400-700. Rank colors: green→blue progression.\"\n4. Push to Stitch:\n   update_design_system(projectId, { designSystem: { theme: { designMd: \"...\" } } })\n5. Verify: list_design_systems → confirm designMd is set\n```\n\n**designMd is the single most important field.** It's free-text that Stitch reads before every generation. A good designMd = every generated screen matches the app without manual adjustment.\n\n## Workflow 1: READ — Understand the Design\n\nWhen a teammate shares a new design or points to a Stitch screen:\n\n**READ from the shared source of truth. GENERATE in the remix project.**\n\n```\n1. list_screens(projectId: \"projects\u002F${STITCH_SHARED_PROJECT_ID}\") → shared designs (source of truth)\n2. get_screen(screenName) → returns:\n   - title, width, height\n   - screenshot.downloadUrl (Google CDN link to PNG)\n   - htmlCode (the design's HTML\u002FCSS)\n3. Download the screenshot URL with WebFetch or save for visual reference\n4. Parse htmlCode for colors, fonts, layout structure\n5. list_design_systems → read current theme tokens (colorMode, fonts, roundness)\n\nOutput: You now know WHAT it looks like. You do NOT know HOW it behaves.\n```\n\n**If a teammate shared a screenshot instead of a Stitch link:**\n1. Save the screenshot locally\n2. `list_screens` → scan screen names for a match\n3. `get_screen` for each candidate → compare title\u002Fdimensions\n4. If no match in Stitch: implement directly from the screenshot\n\n## Workflow 2: PROMPT — Generate New Screens via Stitch\n\nClaude = prompt engineer. Stitch = design generator. Claude crafts detailed, context-rich prompts. Stitch renders them.\n\n```\n1. `get_screen(referenceScreenId)` → inspect screenshot and HTML for existing \"design DNA\"\n2. Understand what the user wants: \"I need a settings screen\" or \"add a premium paywall\"\n3. Craft a detailed prompt for Stitch:\n\n   GOOD PROMPT:\n   \"Settings screen for a fictional Hebrew RTL mobile app. Dark background\n   with subtle gradient. Inter font throughout. Cards for each setting group: \n   'הגדרות חשבון' (account), 'התראות' (notifications), 'פרטיות' (privacy).\n   Toggle switches with purple active state. Bottom navigation bar visible.\n   Shield icon in header. 12px border radius on all cards. Match the visual style\n   of the existing warning screens.\"\n\n   BAD PROMPT:\n   \"Make a settings page\"\n\n4. generate_screen_from_text(prompt) → Stitch renders the design\n5. get_screen(generatedScreenName) → review screenshot.downloadUrl\n6. If not right: edit_screens with specific corrections, or re-prompt\n7. If exploring options: generate_variants for alternatives\n```\n\n**Prompt engineering tips for the example app:**\n- Always specify \"Hebrew RTL\" and exact hex colors\n- Reference existing screens by name for style consistency\n- Include specific Hebrew text for realistic previews\n- Describe layout in screen positions (\"top\", \"bottom-anchored\"), not DOM order\n- Mention the shield icon, gradient backgrounds, and countdown timers as recurring elements\n\n## Workflow 3: GRILL — Ask About Behavior\n\nStitch shows STATIC designs. The app has DYNAMIC behavior. You MUST ask:\n\n**For every screen, ask these questions:**\n\n```\nFLOW QUESTIONS:\n- \"What happens when the user taps [button]?\"\n- \"Where does this screen appear in the navigation flow?\"\n- \"What screen comes before this? What comes after?\"\n- \"Is there a countdown\u002Ftimer? What happens when it ends?\"\n\nSTATE QUESTIONS:\n- \"What does this screen look like in [other state]?\" (loading, error, empty)\n- \"Can the user go back from here?\"\n- \"What if the user is not premium?\"\n- \"Does this need to work offline?\"\n\nDATA QUESTIONS:\n- \"Where does [this text\u002Fnumber] come from?\" (hardcoded, API, local state)\n- \"Is this text translated or always Hebrew?\"\n- \"Does this update in real-time?\"\n\nEDGE CASES:\n- \"What if the user rotates the phone?\"\n- \"What if the text is longer than expected?\"\n- \"What about accessibility — VoiceOver labels?\"\n```\n\n### Synthetic Example: Confirmation Flow\n\nThe static design shows a confirmation screen. GRILL uncovers behavior the pixels cannot encode:\n- a short countdown before the confirmation button activates\n- a long press to confirm the action\n- dynamic status data from the application state\n- all copy is localized — never hardcode text\n\nThe Stitch design showed NONE of this — just a static screen. The GRILL workflow extracted the flow.\n\n**Ask 2-3 at a time.** Don't dump all questions at once. Drill based on answers.\n\n**Store answers:** `brain_store` the flow decisions with tags `[\"example-app\", \"design-flow\", screenName]`. These persist across sessions — next time someone implements from this screen, the flow answers are already in BrainLayer.\n\n## Workflow 4: IMPLEMENT — Build in React Native\n\nOnce you have the visual (from READ) and the behavior (from GRILL):\n\n```\n1. get_screen(screenName) → HTML\u002FCSS reference\n2. Map HTML structure to React Native:\n   - div → View\n   - p\u002Fspan → Text\n   - img → Image (or Expo Image)\n   - button → Pressable\u002FTouchableOpacity\n   - CSS flexbox → RN flexbox (same API)\n   - CSS colors → theme\u002Fcolors.ts constants\n   - CSS fonts → theme\u002Ftypography.ts\n   - px values → responsive units\n3. RTL handling (CRITICAL for Hebrew):\n   - flexDirection: 'row' is REVERSED in RTL\n   - textAlign: 'right' for Hebrew content\n   - writingDirection: 'rtl' on Text components\n   - Mirror directional icons (arrows, chevrons)\n   - I18nManager.isRTL for conditional logic\n4. Wire behavior from GRILL answers:\n   - Navigation (router.push\u002Freplace\u002Fback)\n   - State management (useState, Convex queries)\n   - Timers (useEffect + cleanup)\n   - Animations (Reanimated or LayoutAnimation)\n5. Screenshot implementation → compare side-by-side with Stitch\n```\n\n### HTML → React Native Cheat Sheet\n\n```\nSTITCH HTML\u002FCSS                     →  REACT NATIVE\n──────────────────────────────────────────────────────\n\u003Cdiv class=\"flex flex-col\">         →  \u003CView style={{ flexDirection: 'column' }}>\nbackground: #8B5CF6                 →  backgroundColor: colors.primary\nfont-family: Inter                  →  fontFamily: typography.heading.fontFamily\nborder-radius: 12px                 →  borderRadius: 12\npadding: 16px                       →  padding: 16\nbox-shadow: ...                     →  elevation: 4 (Android) \u002F shadowColor (iOS)\nbackground: linear-gradient(...)    →  \u003CLinearGradient> (expo-linear-gradient)\nposition: fixed                     →  position: 'absolute' (RN has no fixed)\noverflow: scroll                    →  \u003CScrollView>\n```\n\n## Design Token Mapping\n\n```\nSTITCH DESIGN SYSTEM                →  APP CONSTANTS (constants\u002F)\n──────────────────────────────────────────────────────\ncustomColor: \"#8B5CF6\"              →  colors.primary (#8B5CF6)\ncolorMode: \"DARK\"                   →  colors.background (#0A0A1A)\nheadlineFont: \"INTER\"               →  system default (no custom fonts in RN yet)\nbodyFont: \"INTER\"                   →  system default\nlabelFont: \"DM_SANS\"               →  system default\nroundness: \"ROUND_TWELVE\"          →  borderRadius: 12 (per component)\ncolorVariant: \"EXPRESSIVE\"         →  colors.gradient (#8B5CF6→#6366F1→#4F46E5)\ndesignMd: (our crafted text)        →  THE BRIDGE — describes all of the above to Stitch\n```\n\n**Discrepancy:** Stitch uses Inter\u002FDM Sans but the RN app uses system fonts.\nEither install custom fonts in Expo (`expo-font`) or accept the difference.\n\nWhen a supported screen\u002Fdesign-system read exposes values that differ from the app theme files, flag it:\n\"Stitch shows [X] but app\u002Ftheme\u002Fcolors.ts has [Y]. Should I update the app to match?\"\n\n## Integration Patterns\n\n| Trigger | Action |\n|---------|--------|\n| Teammate sends screenshot | READ workflow → match in Stitch → GRILL about flow → IMPLEMENT |\n| New Stitch screen appears | `list_screens` detects it → notify user → wait for implementation request |\n| Theme change in Stitch | Read screen\u002Fdesign-system data → diff with app theme → flag discrepancies |\n| PR review for UI changes | `get_screen` → compare with implementation screenshot |\n| User says \"does this match?\" | `get_screen` + app screenshot → side-by-side comparison |\n\n## i18n Rule (MANDATORY)\n\n**ALL text is i18n.** Never hardcode Hebrew or English strings in components.\n- Use translation keys: `t('warning.countdown')` not `\"רוצה לחזור אחורה?\"`\n- Stitch designs show Hebrew text — treat it as placeholder for the i18n key\n- Dynamic data comes from the application backend, not the design\n\n## RTL Rules (example app is Hebrew-first)\n\n1. **Flex order is reversed** in RTL — first child → RIGHT side of screen\n2. **Text alignment** — Hebrew = `textAlign: 'right'`, `alignItems: 'flex-end'`\n3. **Icons** — arrows\u002Fchevrons must mirror. Use `I18nManager.isRTL ? 'flip' : undefined`\n4. **Padding\u002Fmargin** — `paddingStart`\u002F`paddingEnd` instead of `paddingLeft`\u002F`paddingRight`\n5. **Stitch designs may show LTR** — Stitch defaults LTR. Mentally mirror the layout for implementation.\n\n## Gap Analysis\n\n### Community wrapper (oogleyskr\u002Fstitch-mcp-server, 36 tools)\nRead-only tools we'd benefit from:\n- `compare_designs` — diff two Stitch screens after a teammate iterates\n- `extract_components` — isolate reusable UI patterns from screens\n- `analyze_accessibility` — WCAG 2.1 check on Stitch designs before implementing\n\n### \u002Fyash candidates (things that don't exist anywhere)\n| Gap | Impact | Fix |\n|-----|--------|-----|\n| `screen_to_react_native` | HIGH — manual HTML→RN every time | Fork oogleyskr's screen_to_react, add RN output |\n| Theme.ts sync | MEDIUM — manual token copy | Build codegen from supported screen\u002Fdesign-system reads → theme.ts |\n| Stitch↔implementation diff | MEDIUM — manual screenshot comparison | Build: overlay Stitch PNG on app screenshot, highlight differences |\n\n## Files\n\n```\n${APP_REPO_ROOT}\u002F\n├── .mcp.json                       # Stitch MCP config (connected)\n├── app\u002Ftheme\u002Fcolors.ts             # App colors (sync target)\n├── app\u002Ftheme\u002Ftypography.ts         # Font definitions (sync target)\n├── app\u002Fcomponents\u002F                 # Existing RN components\n├── docs.local\u002Fstitch-mcp-reference.md  # MCP reference notes\n└── ~\u002FDesktop\u002FStitch screens\u002F       # Local screenshots (5 files, Apr 6)\n```\n",{"name":5,"type":24,"version":25,"triggers":26,"description":7},"encoded-preference","0.3.0",[27,28,29,30,31,32,33,34,35,36],"stitch","implement this design","implement the design","match this design","generate a screen","design system","design tokens","the product team's design","warning screen","extract colors from stitch","master","3400bc971628f00ab7bf1063993477e211a5508a","skills\u002Fgolem-powers\u002Fstitch-design","https:\u002F\u002Fgithub.com\u002FEtanHey\u002Fgolems","https:\u002F\u002Fgithub.com\u002FEtanHey","etanheyman.com","2026-11-15 03:05:08",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add EtanHey\u002Fgolems --skill stitch-design",{"tool":50,"command":51},"bunx","bunx skills add EtanHey\u002Fgolems --skill stitch-design",{"tool":53,"command":54},"pnpm","pnpm dlx skills add EtanHey\u002Fgolems --skill stitch-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEtanHey\u002Fgolems\u002Fblob\u002Fmaster\u002Fskills\u002Fgolem-powers\u002Fstitch-design\u002FSKILL.md",true,[],[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7C53JEF6A6SS20Q0D2YJYM8","yash","Push dependency bugs upstream. Triggers: dependency bug, workaround, monkey-patch, fork\u002Ffix. NOT app bugs.","https:\u002F\u002Fgithub.com\u002FEtanHey\u002Fgolems\u002Fblob\u002Fmaster\u002Fskills\u002Fgolem-powers\u002Fyash\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7C53EPMNSZKHK47VY7WQDP0","whats-new","Diff Claude\u002FCodex\u002FCursor\u002FWispr\u002Fagy changelogs vs local setup. Triggers: whats new, changelog, version bump.","https:\u002F\u002Fgithub.com\u002FEtanHey\u002Fgolems\u002Fblob\u002Fmaster\u002Fskills\u002Fgolem-powers\u002Fwhats-new\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7C53C4TVQ9G7AB3X57DACPB","weave","Orchestrator convergence: mine JSONLs, cite findings, route actions. Triggers: weave, run weave.","https:\u002F\u002Fgithub.com\u002FEtanHey\u002Fgolems\u002Fblob\u002Fmaster\u002Fskills\u002Fgolem-powers\u002Fweave\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7C5342EDDN7YH53KKW511V2","unslop","Cut AI tells while keeping every receipt, number, path, and hedge intact. Triggers: unslop, cut the slop, wall of text, too verbose, rambly, make this readable. NOT for delivery cadence (see i-have-adhd), channel choice, or artifact length governance.","https:\u002F\u002Fgithub.com\u002FEtanHey\u002Fgolems\u002Fblob\u002Fmaster\u002Fskills\u002Fgolem-powers\u002Funslop\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7C52M0CTDW5DDP4452FJV0G","tmp-block","Guard denying durable writes to \u002Ftmp, \u002Fprivate\u002Ftmp, \u002Fvar\u002Ffolders, $TMPDIR; enforces \u003Crepo>\u002F.worktrees\u002F\u003Cname>. Triggers: tmp guard, TMP-BLOCK deny, WORKTREE-CONVENTION deny, bypass ledger. NOT for storage policy.","https:\u002F\u002Fgithub.com\u002FEtanHey\u002Fgolems\u002Fblob\u002Fmaster\u002Fskills\u002Fgolem-powers\u002Ftmp-block\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7C52HN4Q9E1Z74Z11K23E2H","t3-visuals","Show\u002Fvisualize\u002Fchart\u002Fdiagram\u002Fcompare\u002Fstatus board in T3 with compact interactive HTML. Not standalone dashboards.","https:\u002F\u002Fgithub.com\u002FEtanHey\u002Fgolems\u002Fblob\u002Fmaster\u002Fskills\u002Fgolem-powers\u002Ft3-visuals\u002FSKILL.md",[],[]]