[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fRRMT1ex2l09DTZlVrMLPF7CHWTAwH9XrqZmobgXA_UI":3},{"id":4,"publisher_id":5,"github_owner":6,"github_repo":7,"full_name":8,"description":9,"skill_count":10,"total_installs":11,"created_at":12,"stars":13,"external_total_installs":14,"external_total_installs_24h":15,"external_total_installs_updated_at":16,"publisher":17,"skills":24,"all_tags":62},"7c347058-952a-4e58-9045-e8403bf721e6","3ca65e7c-5b39-4751-87ac-e139b3694b8a","resend","react-email","resend/react-email","Use when creating email templates with React - welcome emails, password resets, notifications, order confirmations, or transactional emails that need to render across email clients.",1,0,"2026-02-10T20:50:20.34321+00:00",19048,7395,14,"2026-07-28T06:02:42.164+00:00",{"id":5,"bio":18,"name":19,"slug":6,"claimed":20,"verified":20,"avatar_url":21,"created_at":22,"github_type":23,"website_url":18,"github_login":6},null,"Resend",false,"https://avatars.githubusercontent.com/u/109384852?v=4","2026-02-10T20:50:20.178212+00:00","Organization",[25],{"id":26,"repo_id":4,"name":7,"description":27,"skill_id":7,"category_id":28,"content_md":29,"install_count":11,"install_count_24h":11,"verified":20,"created_at":30,"updated_at":31,"enabled":32,"last_resynced_at":31,"skill_md_path":33,"content_refreshed_at":34,"external_install_count":14,"external_install_count_24h":15,"external_install_count_updated_at":35,"content_hash":36,"search_summary":37,"trust_score":38,"risk_reason":18,"validated_at":39,"repo":40,"category":42,"tags":49,"publisher":60,"tools":61},"3c2c4477-3b0f-4c8b-9695-8e8f91677d8a","Use when building HTML email templates with React components, adding a visual email editor to an application using the React Email visual editor, rendering emails to HTML, or sending emails with Resend. Covers welcome emails, password resets, notifications, order confirmations, newsletters, transactional emails, and the embeddable email editor component.","3981aa87-8e15-4262-a671-2ade6cfc7ce8","# React Email\n\nBuild and send HTML emails using React components. A modern, component-based approach to email development that works across all major email clients.\n\n## Installation\n\n```sh\nnpm i react-email\n```\n\nOr scaffold a new project:\n\n```sh\nnpx create-email@latest\ncd react-email-starter\nnpm install\nnpm run dev\n```\n\nThis works with any package manager (npm, yarn, pnpm, bun) — substitute accordingly.\n\nThe dev server runs at localhost:3000 with a preview interface for templates in the `emails` folder.\n\n### Adding to an Existing Project\n\nInstall the packages and add a script to your `package.json`:\n\n```json\n{\n  \"scripts\": {\n    \"email\": \"email dev --dir emails --port 3000\"\n  }\n}\n```\n\nMake sure the path to the emails folder is relative to the base project directory. Ensure `tsconfig.json` includes proper support for JSX.\n\n## Basic Email Template\n\nCreate an email component with proper structure using the Tailwind component for styling:\n\n```tsx\nimport {\n  Html,\n  Head,\n  Preview,\n  Body,\n  Container,\n  Heading,\n  Text,\n  Button,\n  Tailwind,\n  pixelBasedPreset\n} from 'react-email';\n\ninterface WelcomeEmailProps {\n  name: string;\n  verificationUrl: string;\n}\n\nexport default function WelcomeEmail({ name, verificationUrl }: WelcomeEmailProps) {\n  return (\n    \u003CHtml lang=\"en\">\n      \u003CTailwind\n        config={{\n          presets: [pixelBasedPreset],\n          theme: {\n            extend: {\n              colors: {\n                brand: '#007bff',\n              },\n            },\n          },\n        }}\n      >\n        \u003CHead />\n        \u003CBody className=\"bg-gray-100 font-sans\">\n          \u003CPreview>Welcome - Verify your email\u003C/Preview>\n          \u003CContainer className=\"max-w-xl mx-auto p-5\">\n            \u003CHeading className=\"text-2xl text-gray-800\">\n              Welcome!\n            \u003C/Heading>\n            \u003CText className=\"text-base text-gray-800\">\n              Hi {name}, thanks for signing up!\n            \u003C/Text>\n            \u003CButton\n              href={verificationUrl}\n              className=\"bg-brand text-white px-5 py-3 rounded block text-center no-underline box-border\"\n            >\n              Verify Email\n            \u003C/Button>\n          \u003C/Container>\n        \u003C/Body>\n      \u003C/Tailwind>\n    \u003C/Html>\n  );\n}\n\n// Preview props for testing\nWelcomeEmail.PreviewProps = {\n  name: 'John Doe',\n  verificationUrl: 'https://example.com/verify/abc123'\n} satisfies WelcomeEmailProps;\n\nexport { WelcomeEmail };\n```\n\n## Behavioral Guidelines\n\n- When iterating over the code, only update what the user asked for. Keep the rest intact.\n- If the user asks to use media queries, inform them that most email clients don't support them and suggest a different approach.\n- Never use template variables (like `{{name}}`) directly in TypeScript code. Instead, reference the underlying properties directly. If the user explicitly asks for `{{variableName}}`, place the mustache string only in PreviewProps, never in the component JSX:\n\n```typescript\nconst EmailTemplate = (props) => {\n  return (\n    \u003Ch1>Hello, {props.variableName}!\u003C/h1>\n  );\n}\n\nEmailTemplate.PreviewProps = {\n  variableName: \"{{variableName}}\",\n};\n\nexport default EmailTemplate;\n```\n\n- Never write the `{{variableName}}` pattern directly in the component structure. If the user insists, explain that this would make the template invalid.\n\n## Essential Components\n\nSee [references/COMPONENTS.md](references/COMPONENTS.md) for complete component documentation.\n\n**Core Structure:**\n- `Html` - Root wrapper with `lang` attribute\n- `Head` - Meta elements, styles, fonts\n- `Body` - Main content wrapper\n- `Container` - Outermost centering wrapper (has built-in `max-width: 37.5em`). Use only once per email.\n- `Section` - Interior content blocks (no built-in max-width). Use for grouping content inside `Container`.\n- `Row` & `Column` - Multi-column layouts\n- `Tailwind` - Enables Tailwind CSS utility classes\n\n**Content:**\n- `Preview` - Inbox preview text, always first inside `\u003CBody>`\n- `Heading` - h1-h6 headings\n- `Text` - Paragraphs\n- `Button` - Styled link buttons (always include `box-border`)\n- `Link` - Hyperlinks\n- `Img` - Images (see Static Files section below)\n- `Hr` - Horizontal dividers\n\n**Specialized:**\n- `CodeBlock` - Syntax-highlighted code\n- `CodeInline` - Inline code\n- `Markdown` - Render markdown\n- `Font` - Custom web fonts\n\n## Before Writing Code\n\nWhen a user requests an email template, ask clarifying questions FIRST if they haven't provided:\n\n1. **Brand colors** - Ask for primary brand color (hex code like #007bff)\n2. **Logo** - Ask if they have a logo file and its format (PNG/JPG only - warn if SVG/WEBP)\n3. **Style preference** - Professional, casual, or minimal tone\n4. **Production URL** - Where will static assets be hosted in production?\n\n## Static Files and Images\n\n### Directory Structure\n\nLocal images must be placed in the `static` folder inside your emails directory:\n\n```\nproject/\n├── emails/\n│   ├── welcome.tsx\n│   └── static/           \u003C-- Images go here\n│       └── logo.png\n```\n\n### Dev vs Production URLs\n\nUse this pattern for images that work in both dev preview and production:\n\n```tsx\nconst baseURL = process.env.NODE_ENV === \"production\"\n  ? \"https://cdn.example.com\"  // User's production CDN\n  : \"\";\n\nexport default function Email() {\n  return (\n    \u003CImg\n      src={`${baseURL}/static/logo.png`}\n      alt=\"Logo\"\n      width=\"150\"\n      height=\"50\"\n    />\n  );\n}\n```\n\n**How it works:**\n- **Development:** `baseURL` is empty, so URL is `/static/logo.png` - served by React Email's dev server\n- **Production:** `baseURL` is the CDN domain, so URL is `https://cdn.example.com/static/logo.png`\n\n**Important:** Always ask the user for their production hosting URL. Do not hardcode `localhost:3000`.\n\n## Styling\n\nSee [references/STYLING.md](references/STYLING.md) for comprehensive styling documentation including typography, layout patterns, dark mode, and brand consistency.\n\n### Key Rules\n\n- Use `Tailwind` with `pixelBasedPreset` (email clients don't support `rem`). Import `pixelBasedPreset` from `react-email`.\n- Never use flexbox or grid — use `Row`/`Column` components or tables for layouts.\n- Avoid CSS/Tailwind media queries (`sm:`, `md:`, `lg:`, `xl:`) — limited email client support.\n- Never use theme selectors (`dark:`, `light:`) — not supported.\n- Never use SVG or WEBP images — warn users about rendering issues.\n- Always specify border type (`border-solid`, `border-dashed`, etc.) — email clients don't inherit it.\n- For single-side borders, reset others first (`border-none border-l border-solid`).\n\n### Required Classes\n\n| Component | Required Class | Why |\n|-----------|---------------|-----|\n| `Button` | `box-border` | Prevents padding from overflowing the button width |\n| `Hr` / any border | `border-solid` (or `border-dashed`, etc.) | Email clients don't inherit border type |\n| Single-side borders | `border-none` + the side | Resets default borders on other sides |\n\n### Structure Notes\n- Always define `\u003CHead />` inside `\u003CTailwind>` when using Tailwind CSS\n- `\u003CPreview>` should always be the first element inside `\u003CBody>`\n- Only include props in `PreviewProps` that the component actually uses\n- Use fixed width/height for known-size elements (logos, icons); responsive sizing (`w-full`, `h-auto`) for content images\n\n## Rendering\n\n### Convert to HTML\n\n```tsx\nimport { render } from 'react-email';\nimport { WelcomeEmail } from './emails/welcome';\n\nconst html = await render(\n  \u003CWelcomeEmail name=\"John\" verificationUrl=\"https://example.com/verify\" />\n);\n```\n\n### Convert to Plain Text\n\n```tsx\nconst text = await render(\u003CWelcomeEmail name=\"John\" verificationUrl=\"https://example.com/verify\" />, { plainText: true });\n```\n\n## Sending\n\nReact Email supports sending with any email service provider. See [references/SENDING.md](references/SENDING.md) for complete sending documentation including Resend, Nodemailer, and SendGrid examples.\n\nQuick example using the Resend SDK:\n\n```tsx\nimport { Resend } from 'resend';\nimport { WelcomeEmail } from './emails/welcome';\n\nconst resend = new Resend(process.env.RESEND_API_KEY);\n\nconst { data, error } = await resend.emails.send({\n  from: 'Acme \u003Conboarding@resend.dev>',\n  to: ['user@example.com'],\n  subject: 'Welcome to Acme',\n  react: \u003CWelcomeEmail name=\"John\" verificationUrl=\"https://example.com/verify\" />\n});\n```\n\nThe Resend Node SDK automatically handles both HTML and plain-text rendering.\n\n## CLI Commands\n\nThe `react-email` package provides a CLI accessible via the `email` command:\n\n| Command | Description |\n|---------|-------------|\n| `email dev --dir \u003Cpath> --port \u003Cport>` | Start the preview development server (default: `./emails`, port 3000) |\n| `email build --dir \u003Cpath>` | Build the preview app for production deployment |\n| `email start` | Run the built preview app |\n| `email export --outDir \u003Cpath> --pretty --plainText --dir \u003Cpath>` | Export templates to static HTML files |\n| `email resend setup` | Connect the CLI to your Resend account via API key |\n| `email resend reset` | Remove the stored Resend API key |\n\n## Internationalization\n\nSee [references/I18N.md](references/I18N.md) for complete i18n documentation. React Email supports three libraries: next-intl, react-i18next, and react-intl.\n\n## Email Editor\n\nReact Email includes a visual editor (`@react-email/editor`) that can be embedded in your app. It's built on TipTap/ProseMirror and produces email-ready HTML.\n\nSee [references/EDITOR.md](references/EDITOR.md) for complete documentation including:\n- `EmailEditor` — batteries-included component with bubble menus, slash commands, and theming\n- `StarterKit` — 35+ email-aware extensions (headings, lists, tables, columns, buttons, etc.)\n- `Inspector` — contextual sidebar for editing styles\n- `EmailTheming` — built-in themes (`basic`, `minimal`) with customizable CSS properties\n- `composeReactEmail` — export editor content to email-ready HTML and plain text\n- Custom extensions via `EmailNode` and `EmailMark`\n\nQuick example:\n\n```tsx\nimport { EmailEditor, type EmailEditorRef } from '@react-email/editor';\nimport '@react-email/editor/themes/default.css';\nimport { useRef } from 'react';\n\nexport function MyEditor() {\n  const ref = useRef\u003CEmailEditorRef>(null);\n\n  return (\n    \u003CEmailEditor\n      ref={ref}\n      content=\"\u003Cp>Start typing...\u003C/p>\"\n      theme=\"basic\"\n    />\n  );\n}\n```\n\n## Common Patterns\n\nSee [references/PATTERNS.md](references/PATTERNS.md) for complete examples including:\n- Password reset emails\n- Order confirmations with product lists\n- Notification emails with code blocks\n- Multi-column layouts\n- Team invitation emails\n\n## Email Best Practices\n\n1. **Test across email clients** - Gmail, Outlook, Apple Mail, Yahoo Mail\n2. **Keep it responsive** - Max-width around 600px, test on mobile\n3. **Use absolute image URLs** - Host on reliable CDN\n4. **Write meaningful alt text** - Describe purpose and details for content images; use `alt=\"\"` for decorative images (spacers, dividers, background flourishes). React Email's `\u003CImg>` defaults to `alt=\"\"`.\n5. **Provide plain text version** - Required for accessibility\n6. **Keep file size under 102KB** - Gmail clips larger emails\n7. **Add proper TypeScript types** - Define interfaces for all email props\n8. **Include preview props** - Add `.PreviewProps` for development testing\n9. **Use verified domains** - For production `from` addresses\n\n### Accessibility\n\nReact Email handles the structural defaults; the rest is content.\n\n**What React Email gives you for free:**\n- `\u003CHtml>` sets `lang` and `dir` (defaults: `lang=\"en\" dir=\"ltr\"` — override per locale)\n- `\u003CImg>` defaults to `alt=\"\"` so decorative images are skipped by screen readers\n- `\u003CMarkdown>` renders layout tables with `role=\"presentation\"`\n- `\u003CPreview>` also emits a `\u003Ctitle>` tag\n\nUpgrade with `npm install react-email@latest` to get these defaults.\n\n**What you still have to do (content choices):**\n- Open with a single `\u003CHeading as=\"h1\">`, nest subheadings in order, never skip levels (very short SMS-style emails may skip the heading entirely)\n- Set descriptive `alt` on meaningful images; pass an explicit `alt=\"\"` on decorative images — never omit the attribute\n- **Linked images are never decorative.** When an `\u003CImg>` is inside a `\u003CLink>` or `\u003CButton>`, the `alt` must describe where the link goes — `alt=\"\"` on a linked image leaves the link with no accessible name\n- Write link text that describes the destination (`\u003CButton>Read the report\u003C/Button>`, not `click here`)\n- Hit 4.5:1 text contrast (WCAG AA); preview in dark mode\n- For layout tables you build by hand (outside `\u003CMarkdown>`), add `role=\"presentation\"`\n- For non-English emails, pass the locale: `\u003CHtml lang={locale} dir={isRTL ? 'rtl' : 'ltr'}>` (see [I18N.md](references/I18N.md))\n\nFor the full rule set, severity ranking, and authoring checklist, see the [accessibility reference](https://github.com/resend/email-best-practices/blob/main/references/accessibility.md) in the `email-best-practices` skill.\n\n## Additional Resources\n\n- [React Email Documentation](https://react.email/docs/llms.txt)\n- [React Email GitHub](https://github.com/resend/react-email)\n- [Resend Documentation](https://resend.com/docs/llms.txt)\n- [Email Client CSS Support](https://www.caniemail.com)\n- Component Reference: [references/COMPONENTS.md](references/COMPONENTS.md)\n- Styling Guide: [references/STYLING.md](references/STYLING.md)\n- Email Editor: [references/EDITOR.md](references/EDITOR.md)\n- Sending Guide: [references/SENDING.md](references/SENDING.md)\n- Internationalization Guide: [references/I18N.md](references/I18N.md)\n- Common Patterns: [references/PATTERNS.md](references/PATTERNS.md)","2026-02-10T20:50:20.543406+00:00","2026-07-15T05:03:38.789+00:00",true,"skills/react-email/SKILL.md","2026-07-26T04:07:38.64+00:00","2026-07-28T06:02:24.267+00:00","e04c977e4dcbc58a60834f8eb0befd1b407ae3394c04bb1af155f9ad9d858e5e","Enables developers to build responsive HTML email templates using React components and Tailwind CSS, supporting major email clients. Includes tools for rendering emails to HTML, embedding a visual email editor, and sending transactional emails such as welcome messages, password resets, notifications, order confirmations, and newsletters using Resend. Suitable for integrating email design and sending workflows into React applications with component-based, styled email templates.",100,"2026-05-29T04:06:42.801+00:00",{"id":4,"stars":13,"full_name":8,"publisher":41,"created_at":12,"description":9,"github_repo":7,"skill_count":10,"github_owner":6,"publisher_id":5,"total_installs":11,"external_total_installs":14,"external_total_installs_24h":15,"external_total_installs_updated_at":16},{"id":5,"bio":18,"name":19,"slug":6,"claimed":20,"verified":20,"avatar_url":21,"created_at":22,"github_type":23,"website_url":18,"github_login":6},{"id":28,"icon":43,"name":44,"slug":45,"intent":46,"reason":47,"sort_order":10,"description":48},"🎨","Design & Theme Your Store","design-theme-your-store","I want my store to look great","Place a skill here when it is primarily about VISUAL OUTPUT — the appearance and presentation layer of a storefront. This includes: theme development and customization (Shopify Liquid themes, Hyvä/Luma for Magento, Dawn forks), UI component libraries used for building store interfaces (Polaris, shadcn/ui, Radix, Headless UI, Reka UI), CSS frameworks and utility-first styling (Tailwind CSS components, UnoCSS), design system creation and token management, Figma-to-code implementation workflows, transactional email design and templating (React Email, Magento email themes), visual design methodology and aesthetics (typography, color, layout, responsive design). KEY DISTINCTION: If the skill is about how something LOOKS (colors, layout, components, themes) → here. If it's about how something BEHAVES (state, routing, data fetching) → 'Build Storefront Features'. If it teaches design principles without hands-on building → 'Learn & Follow Best Practices'.","Themes, UI components, CSS frameworks, design systems, and email templates — everything that shapes how your store looks and feels.",[50,55],{"id":51,"name":52,"slug":52,"color":53,"enabled":32,"created_at":54,"is_keyword":20,"claimed":20},"82b5382f-0c99-4515-b952-848ee9ac03c1","react","#22c55e","2026-02-04T19:32:18.578582+00:00",{"id":56,"name":57,"slug":57,"color":58,"enabled":32,"created_at":59,"is_keyword":32,"claimed":20},"d72b6e61-fca8-47fe-87d3-c4d2865e019e","tailwind-css","#6366f1","2026-02-07T11:50:56.159915+00:00",{"id":5,"bio":18,"name":19,"slug":6,"claimed":20,"verified":20,"avatar_url":21,"created_at":22,"github_type":23,"website_url":18,"github_login":6},[],[63,64],{"id":51,"name":52,"slug":52,"color":53,"enabled":32,"created_at":54,"is_keyword":20,"claimed":20},{"id":56,"name":57,"slug":57,"color":58,"enabled":32,"created_at":59,"is_keyword":32,"claimed":20}]