[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EX2EGA5RG5PJ1EBD5AKSC7":3,"skill-same:01M6EX2EGA5RG5PJ1EBD5AKSC7":107},{"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":26,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6EX2EGA5RG5PJ1EBD5AKSC7","react-email",null,"Use when creating HTML email templates with React components - welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fresend\u002Freact-email\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"react","email","react email","components","react components","welcome","notifications","templates","password","use","html","resend","emails","transactional emails","with","2026-11-10 10:12:30",false,"---\nname: react-email\ndescription: Use when creating HTML email templates with React components - welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails.\nlicense: MIT\nmetadata:\n  author: Resend\n  version: \"1.1.0\"\n---\n\n# 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\nYou need to scaffold a new React Email project using the create-email CLI. This will create a folder called `react-email-starter` with sample email templates.\n\nUsing npm:\n```sh\nnpx create-email@latest\n```\n\nUsing yarn:\n```sh\nyarn create email\n```\n\nUsing pnpm:\n```sh\npnpm create email\n```\n\nUsing bun:\n```sh\nbun create email\n```\n\n## Navigate to Project Directory\n\nYou must change into the newly created project folder:\n\n```sh\ncd react-email-starter\n```\n\n## Install Dependencies\n\nYou need to install all project dependencies before running the development server.\n\nUsing npm:\n```sh\nnpm install\n```\n\nUsing yarn:\n```sh\nyarn\n```\n\nUsing pnpm:\n```sh\npnpm install\n```\n\nUsing bun:\n```sh\nbun install\n```\n\n## Start the Development Server\n\nYour task is to start the local preview server to view and edit email templates.\n\nUsing npm:\n```sh\nnpm run dev\n```\n\nUsing yarn:\n```sh\nyarn dev\n```\n\nUsing pnpm:\n```sh\npnpm dev\n```\n\nUsing bun:\n```sh\nbun dev\n```\n\n## Verify Installation\n\nConfirm the development server is running by checking that localhost:3000 is accessible. The server will display a preview interface where you can view email templates from the `emails` folder.\n\n### Notes on installation\nAssuming React Email is installed in an existing project, update the top-level package.json file with a script to run the React Email preview server.\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.\n\n\n### tsconfig.json updating or creation\n\nEnsure the tsconfig.json includes proper support for jsx.\n\n## Basic Email Template\n\nReplace the sample email templates. Here is how to create a new 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\u002Fcomponents';\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 \u002F>\n        \u003CPreview>Welcome - Verify your email\u003C\u002FPreview>\n        \u003CBody className=\"bg-gray-100 font-sans\">\n          \u003CContainer className=\"max-w-xl mx-auto p-5\">\n            \u003CHeading className=\"text-2xl text-gray-800\">\n              Welcome!\n            \u003C\u002FHeading>\n            \u003CText className=\"text-base text-gray-800\">\n              Hi {name}, thanks for signing up!\n            \u003C\u002FText>\n            \u003CButton\n              href={verificationUrl}\n              className=\"bg-brand text-white px-5 py-3 rounded block text-center no-underline\"\n            >\n              Verify Email\n            \u003C\u002FButton>\n          \u003C\u002FContainer>\n        \u003C\u002FBody>\n      \u003C\u002FTailwind>\n    \u003C\u002FHtml>\n  );\n}\n\n\u002F\u002F Preview props for testing\nWelcomeEmail.PreviewProps = {\n  name: 'John Doe',\n  verificationUrl: 'https:\u002F\u002Fexample.com\u002Fverify\u002Fabc123'\n} satisfies WelcomeEmailProps;\n\nexport { WelcomeEmail };\n```\n\n## Essential Components\n\nSee [references\u002FCOMPONENTS.md](references\u002FCOMPONENTS.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` - Centers content (max-width layout)\n- `Section` - Layout sections\n- `Row` & `Column` - Multi-column layouts\n- `Tailwind` - Enables Tailwind CSS utility classes\n\n**Content:**\n- `Preview` - Inbox preview text, always first in `Body`\n- `Heading` - h1-h6 headings\n- `Text` - Paragraphs\n- `Button` - Styled link buttons\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\u002FJPG only - warn if SVG\u002FWEBP)\n3. **Style preference** - Professional, casual, or minimal tone\n4. **Production URL** - Where will static assets be hosted in production?\n\nExample response to vague request:\n> Before I create your email template, I have a few questions:\n> 1. What is your primary brand color? (hex code)\n> 2. Do you have a logo file? (PNG or JPG - note: SVG and WEBP don't work reliably in email clients)\n> 3. What tone do you prefer - professional, casual, or minimal?\n> 4. Where will you host static assets in production? (e.g., https:\u002F\u002Fcdn.example.com)\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\u002F\n├── emails\u002F\n│   ├── welcome.tsx\n│   └── static\u002F           \u003C-- Images go here\n│       └── logo.png\n```\n\nIf user has an image elsewhere, instruct them to copy it:\n```sh\ncp .\u002Fassets\u002Flogo.png .\u002Femails\u002Fstatic\u002Flogo.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:\u002F\u002Fcdn.example.com\"  \u002F\u002F User's production CDN\n  : \"\";\n\nexport default function Email() {\n  return (\n    \u003CImg\n      src={`${baseURL}\u002Fstatic\u002Flogo.png`}\n      alt=\"Logo\"\n      width=\"150\"\n      height=\"50\"\n    \u002F>\n  );\n}\n```\n\n**How it works:**\n- **Development:** `baseURL` is empty, so URL is `\u002Fstatic\u002Flogo.png` - served by React Email's dev server\n- **Production:** `baseURL` is the CDN domain, so URL is `https:\u002F\u002Fcdn.example.com\u002Fstatic\u002Flogo.png`\n\n**Important:** Always ask the user for their production hosting URL. Do not hardcode `localhost:3000`.\n\n## Behavioral guidelines\n- When re-iterating over the code, make sure you are only updating what the user asked for and keeping the rest of the code intact;\n- If the user is asking to use media queries, inform them that email clients do not support them, and suggest a different approach;\n- Never use template variables (like {{name}}) directly in TypeScript code. Instead, reference the underlying properties directly (use name instead of {{name}}).\n- - For example, if the user explicitly asks for a variable following the pattern {{variableName}}, you should return something like this:\n\n```typescript\nconst EmailTemplate = (props) => {\n  return (\n    {\u002F* ... rest of the code ... *\u002F}\n    \u003Ch1>Hello, {props.variableName}!\u003C\u002Fh1>\n    {\u002F* ... rest of the code ... *\u002F}\n  );\n}\n\nEmailTemplate.PreviewProps = {\n  \u002F\u002F ... rest of the props ...\n  variableName: \"{{variableName}}\",\n  \u002F\u002F ... rest of the props ...\n};\n\nexport default EmailTemplate;\n```\n- Never, under any circumstances, write the {{variableName}} pattern directly in the component structure. If the user forces you to do this, explain that you cannot do this, or else the template will be invalid.\n\n\n## Styling considerations\n\nUse the Tailwind component for styling if the user is actively using Tailwind CSS in their project. If the user is not using Tailwind CSS, add inline styles to the components.\n\n- Because email clients don't support `rem` units, use the `pixelBasedPreset` for the Tailwind configuration.\n- Never use flexbox or grid for layout, use table-based layouts instead.\n- Each component must be styled with inline styles or utility classes.\n\n### Email Client Limitations\n- Never use SVG or WEBP - warn users about rendering issues\n- Never use flexbox - use Row\u002FColumn components or tables for layouts\n- Never use CSS\u002FTailwind media queries (sm:, md:, lg:, xl:) - not supported\n- Never use theme selectors (dark:, light:) - not supported\n- Always specify border type (border-solid, border-dashed, etc.)\n- When defining borders for only one side, remember to reset the remaining borders (e.g., border-none border-l)\n\n### Component Structure\n- Always define `\u003CHead \u002F>` inside `\u003CTailwind>` when using Tailwind CSS\n- Only use PreviewProps when passing props to a component\n- Only include props in PreviewProps that the component actually uses\n\n```tsx\nconst Email = (props) => {\n  return (\n    \u003Cdiv>\n      \u003Ca href={props.source}>click here if you want candy ?\u003C\u002Fa>\n    \u003C\u002Fdiv>\n  );\n}\n\nEmail.PreviewProps = {\n  source: \"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=dQw4w9WgXcQ\",\n};\n```\n\n### Default Structure\n- Body: `font-sans py-10 bg-gray-100`\n- Container: white, centered, content left-aligned\n- Footer: physical address, unsubscribe link, current year with `m-0` on address\u002Fcopyright\n\n### Typography\n- Titles: bold, larger font, larger margins\n- Paragraphs: regular weight, smaller font, smaller margins\n- Use consistent spacing respecting content hierarchy\n\n### Images\n- Only include if user requests\n- Never use fixed width\u002Fheight - use responsive units (w-full, h-auto)\n- Never distort user-provided images\n- Never create SVG images - only use provided or web images\n\n### Buttons\n- Always use `box-border` to prevent padding overflow\n\n### Layout\n- Always mobile-friendly by default\n- Use stacked layouts that work on all screen sizes\n- Remove default spacing\u002Fmargins\u002Fpadding between list items\n\n### Dark Mode\nWhen requested: container black (#000), background dark gray (#151516)\n\n### Best Practices\n- Choose colors, layout, and copy based on user's request\n- Make templates unique, not generic\n- Use keywords in email body to increase conversion\n\n## Rendering\n\n### Convert to HTML\n\n```tsx\nimport { render } from '@react-email\u002Fcomponents';\nimport { WelcomeEmail } from '.\u002Femails\u002Fwelcome';\n\nconst html = await render(\n  \u003CWelcomeEmail name=\"John\" verificationUrl=\"https:\u002F\u002Fexample.com\u002Fverify\" \u002F>\n);\n```\n\n### Convert to Plain Text\n\n```tsx\nimport { render } from '@react-email\u002Fcomponents';\nimport { WelcomeEmail } from '.\u002Femails\u002Fwelcome';\n\nconst text = await render(\u003CWelcomeEmail name=\"John\" verificationUrl=\"https:\u002F\u002Fexample.com\u002Fverify\" \u002F>, { plainText: true });\n```\n\n## Sending\n\nReact Email supports sending with any email service provider. If the user wants to know how to send, view the [Sending guidelines](references\u002FSENDING.md).\n\nQuick example using the Resend SDK for Node.js:\n\n```tsx\nimport { Resend } from 'resend';\nimport { WelcomeEmail } from '.\u002Femails\u002Fwelcome';\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:\u002F\u002Fexample.com\u002Fverify\" \u002F>\n});\n\nif (error) {\n  console.error('Failed to send:', error);\n}\n```\n\nThe Node SDK automatically handles the plain-text rendering and HTML rendering for you.\n\n## Internationalization\n\nSee [references\u002FI18N.md](references\u002FI18N.md) for complete i18n documentation.\n\nReact Email supports three i18n libraries: next-intl, react-i18next, and react-intl.\n\n### Quick Example (next-intl)\n\n```tsx\nimport { createTranslator } from 'next-intl';\nimport {\n  Html,\n  Body,\n  Container,\n  Text,\n  Button,\n  Tailwind,\n  pixelBasedPreset\n} from '@react-email\u002Fcomponents';\n\ninterface EmailProps {\n  name: string;\n  locale: string;\n}\n\nexport default async function WelcomeEmail({ name, locale }: EmailProps) {\n  const t = createTranslator({\n    messages: await import(\\`..\u002Fmessages\u002F\\${locale}.json\\`),\n    namespace: 'welcome-email',\n    locale\n  });\n\n  return (\n    \u003CHtml lang={locale}>\n      \u003CTailwind config={{ presets: [pixelBasedPreset] }}>\n        \u003CBody className=\"bg-gray-100 font-sans\">\n          \u003CContainer className=\"max-w-xl mx-auto p-5\">\n            \u003CText className=\"text-base text-gray-800\">{t('greeting')} {name},\u003C\u002FText>\n            \u003CText className=\"text-base text-gray-800\">{t('body')}\u003C\u002FText>\n            \u003CButton href=\"https:\u002F\u002Fexample.com\" className=\"bg-blue-600 text-white px-5 py-3 rounded\">\n              {t('cta')}\n            \u003C\u002FButton>\n          \u003C\u002FContainer>\n        \u003C\u002FBody>\n      \u003C\u002FTailwind>\n    \u003C\u002FHtml>\n  );\n}\n```\n\nMessage files (\\`messages\u002Fen.json\\`, \\`messages\u002Fes.json\\`, etc.):\n\n```json\n{\n  \"welcome-email\": {\n    \"greeting\": \"Hi\",\n    \"body\": \"Thanks for signing up!\",\n    \"cta\": \"Get Started\"\n  }\n}\n```\n\n## Email Best Practices\n\n1. **Test across email clients** - Test in Gmail, Outlook, Apple Mail, Yahoo Mail. Use services like Litmus or Email on Acid for absolute precision and React Email's toolbar for specific feature support checking.\n\n2. **Keep it responsive** - Max-width around 600px, test on mobile devices.\n\n3. **Use absolute image URLs** - Host on reliable CDN, always include \\`alt\\` text.\n\n4. **Provide plain text version** - Required for accessibility and some email clients.\n\n5. **Keep file size under 102KB** - Gmail clips larger emails.\n\n6. **Add proper TypeScript types** - Define interfaces for all email props.\n\n7. **Include preview props** - Add \\`.PreviewProps\\` to components for development testing.\n\n8. **Handle errors** - Always check for errors when sending emails.\n\n9.  **Use verified domains** - For production, use verified domains in \\`from\\` addresses.\n\n## Common Patterns\n\nSee [references\u002FPATTERNS.md](references\u002FPATTERNS.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- Email templates with custom fonts\n\n## Additional Resources\n\n- [React Email Documentation](https:\u002F\u002Freact.email\u002Fdocs\u002Fllms.txt)\n- [React Email GitHub](https:\u002F\u002Fgithub.com\u002Fresend\u002Freact-email)\n- [Resend Documentation](https:\u002F\u002Fresend.com\u002Fdocs\u002Fllms.txt)\n- [Email Client CSS Support](https:\u002F\u002Fwww.caniemail.com)\n- Component Reference: [references\u002FCOMPONENTS.md](references\u002FCOMPONENTS.md)\n- Internationalization Guide: [references\u002FI18N.md](references\u002FI18N.md)\n- Common Patterns: [references\u002FPATTERNS.md](references\u002FPATTERNS.md)\n","# 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\nYou need to scaffold a new React Email project using the create-email CLI. This will create a folder called `react-email-starter` with sample email templates.\n\nUsing npm:\n```sh\nnpx create-email@latest\n```\n\nUsing yarn:\n```sh\nyarn create email\n```\n\nUsing pnpm:\n```sh\npnpm create email\n```\n\nUsing bun:\n```sh\nbun create email\n```\n\n## Navigate to Project Directory\n\nYou must change into the newly created project folder:\n\n```sh\ncd react-email-starter\n```\n\n## Install Dependencies\n\nYou need to install all project dependencies before running the development server.\n\nUsing npm:\n```sh\nnpm install\n```\n\nUsing yarn:\n```sh\nyarn\n```\n\nUsing pnpm:\n```sh\npnpm install\n```\n\nUsing bun:\n```sh\nbun install\n```\n\n## Start the Development Server\n\nYour task is to start the local preview server to view and edit email templates.\n\nUsing npm:\n```sh\nnpm run dev\n```\n\nUsing yarn:\n```sh\nyarn dev\n```\n\nUsing pnpm:\n```sh\npnpm dev\n```\n\nUsing bun:\n```sh\nbun dev\n```\n\n## Verify Installation\n\nConfirm the development server is running by checking that localhost:3000 is accessible. The server will display a preview interface where you can view email templates from the `emails` folder.\n\n### Notes on installation\nAssuming React Email is installed in an existing project, update the top-level package.json file with a script to run the React Email preview server.\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.\n\n\n### tsconfig.json updating or creation\n\nEnsure the tsconfig.json includes proper support for jsx.\n\n## Basic Email Template\n\nReplace the sample email templates. Here is how to create a new 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\u002Fcomponents';\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 \u002F>\n        \u003CPreview>Welcome - Verify your email\u003C\u002FPreview>\n        \u003CBody className=\"bg-gray-100 font-sans\">\n          \u003CContainer className=\"max-w-xl mx-auto p-5\">\n            \u003CHeading className=\"text-2xl text-gray-800\">\n              Welcome!\n            \u003C\u002FHeading>\n            \u003CText className=\"text-base text-gray-800\">\n              Hi {name}, thanks for signing up!\n            \u003C\u002FText>\n            \u003CButton\n              href={verificationUrl}\n              className=\"bg-brand text-white px-5 py-3 rounded block text-center no-underline\"\n            >\n              Verify Email\n            \u003C\u002FButton>\n          \u003C\u002FContainer>\n        \u003C\u002FBody>\n      \u003C\u002FTailwind>\n    \u003C\u002FHtml>\n  );\n}\n\n\u002F\u002F Preview props for testing\nWelcomeEmail.PreviewProps = {\n  name: 'John Doe',\n  verificationUrl: 'https:\u002F\u002Fexample.com\u002Fverify\u002Fabc123'\n} satisfies WelcomeEmailProps;\n\nexport { WelcomeEmail };\n```\n\n## Essential Components\n\nSee [references\u002FCOMPONENTS.md](references\u002FCOMPONENTS.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` - Centers content (max-width layout)\n- `Section` - Layout sections\n- `Row` & `Column` - Multi-column layouts\n- `Tailwind` - Enables Tailwind CSS utility classes\n\n**Content:**\n- `Preview` - Inbox preview text, always first in `Body`\n- `Heading` - h1-h6 headings\n- `Text` - Paragraphs\n- `Button` - Styled link buttons\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\u002FJPG only - warn if SVG\u002FWEBP)\n3. **Style preference** - Professional, casual, or minimal tone\n4. **Production URL** - Where will static assets be hosted in production?\n\nExample response to vague request:\n> Before I create your email template, I have a few questions:\n> 1. What is your primary brand color? (hex code)\n> 2. Do you have a logo file? (PNG or JPG - note: SVG and WEBP don't work reliably in email clients)\n> 3. What tone do you prefer - professional, casual, or minimal?\n> 4. Where will you host static assets in production? (e.g., https:\u002F\u002Fcdn.example.com)\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\u002F\n├── emails\u002F\n│   ├── welcome.tsx\n│   └── static\u002F           \u003C-- Images go here\n│       └── logo.png\n```\n\nIf user has an image elsewhere, instruct them to copy it:\n```sh\ncp .\u002Fassets\u002Flogo.png .\u002Femails\u002Fstatic\u002Flogo.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:\u002F\u002Fcdn.example.com\"  \u002F\u002F User's production CDN\n  : \"\";\n\nexport default function Email() {\n  return (\n    \u003CImg\n      src={`${baseURL}\u002Fstatic\u002Flogo.png`}\n      alt=\"Logo\"\n      width=\"150\"\n      height=\"50\"\n    \u002F>\n  );\n}\n```\n\n**How it works:**\n- **Development:** `baseURL` is empty, so URL is `\u002Fstatic\u002Flogo.png` - served by React Email's dev server\n- **Production:** `baseURL` is the CDN domain, so URL is `https:\u002F\u002Fcdn.example.com\u002Fstatic\u002Flogo.png`\n\n**Important:** Always ask the user for their production hosting URL. Do not hardcode `localhost:3000`.\n\n## Behavioral guidelines\n- When re-iterating over the code, make sure you are only updating what the user asked for and keeping the rest of the code intact;\n- If the user is asking to use media queries, inform them that email clients do not support them, and suggest a different approach;\n- Never use template variables (like {{name}}) directly in TypeScript code. Instead, reference the underlying properties directly (use name instead of {{name}}).\n- - For example, if the user explicitly asks for a variable following the pattern {{variableName}}, you should return something like this:\n\n```typescript\nconst EmailTemplate = (props) => {\n  return (\n    {\u002F* ... rest of the code ... *\u002F}\n    \u003Ch1>Hello, {props.variableName}!\u003C\u002Fh1>\n    {\u002F* ... rest of the code ... *\u002F}\n  );\n}\n\nEmailTemplate.PreviewProps = {\n  \u002F\u002F ... rest of the props ...\n  variableName: \"{{variableName}}\",\n  \u002F\u002F ... rest of the props ...\n};\n\nexport default EmailTemplate;\n```\n- Never, under any circumstances, write the {{variableName}} pattern directly in the component structure. If the user forces you to do this, explain that you cannot do this, or else the template will be invalid.\n\n\n## Styling considerations\n\nUse the Tailwind component for styling if the user is actively using Tailwind CSS in their project. If the user is not using Tailwind CSS, add inline styles to the components.\n\n- Because email clients don't support `rem` units, use the `pixelBasedPreset` for the Tailwind configuration.\n- Never use flexbox or grid for layout, use table-based layouts instead.\n- Each component must be styled with inline styles or utility classes.\n\n### Email Client Limitations\n- Never use SVG or WEBP - warn users about rendering issues\n- Never use flexbox - use Row\u002FColumn components or tables for layouts\n- Never use CSS\u002FTailwind media queries (sm:, md:, lg:, xl:) - not supported\n- Never use theme selectors (dark:, light:) - not supported\n- Always specify border type (border-solid, border-dashed, etc.)\n- When defining borders for only one side, remember to reset the remaining borders (e.g., border-none border-l)\n\n### Component Structure\n- Always define `\u003CHead \u002F>` inside `\u003CTailwind>` when using Tailwind CSS\n- Only use PreviewProps when passing props to a component\n- Only include props in PreviewProps that the component actually uses\n\n```tsx\nconst Email = (props) => {\n  return (\n    \u003Cdiv>\n      \u003Ca href={props.source}>click here if you want candy ?\u003C\u002Fa>\n    \u003C\u002Fdiv>\n  );\n}\n\nEmail.PreviewProps = {\n  source: \"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=dQw4w9WgXcQ\",\n};\n```\n\n### Default Structure\n- Body: `font-sans py-10 bg-gray-100`\n- Container: white, centered, content left-aligned\n- Footer: physical address, unsubscribe link, current year with `m-0` on address\u002Fcopyright\n\n### Typography\n- Titles: bold, larger font, larger margins\n- Paragraphs: regular weight, smaller font, smaller margins\n- Use consistent spacing respecting content hierarchy\n\n### Images\n- Only include if user requests\n- Never use fixed width\u002Fheight - use responsive units (w-full, h-auto)\n- Never distort user-provided images\n- Never create SVG images - only use provided or web images\n\n### Buttons\n- Always use `box-border` to prevent padding overflow\n\n### Layout\n- Always mobile-friendly by default\n- Use stacked layouts that work on all screen sizes\n- Remove default spacing\u002Fmargins\u002Fpadding between list items\n\n### Dark Mode\nWhen requested: container black (#000), background dark gray (#151516)\n\n### Best Practices\n- Choose colors, layout, and copy based on user's request\n- Make templates unique, not generic\n- Use keywords in email body to increase conversion\n\n## Rendering\n\n### Convert to HTML\n\n```tsx\nimport { render } from '@react-email\u002Fcomponents';\nimport { WelcomeEmail } from '.\u002Femails\u002Fwelcome';\n\nconst html = await render(\n  \u003CWelcomeEmail name=\"John\" verificationUrl=\"https:\u002F\u002Fexample.com\u002Fverify\" \u002F>\n);\n```\n\n### Convert to Plain Text\n\n```tsx\nimport { render } from '@react-email\u002Fcomponents';\nimport { WelcomeEmail } from '.\u002Femails\u002Fwelcome';\n\nconst text = await render(\u003CWelcomeEmail name=\"John\" verificationUrl=\"https:\u002F\u002Fexample.com\u002Fverify\" \u002F>, { plainText: true });\n```\n\n## Sending\n\nReact Email supports sending with any email service provider. If the user wants to know how to send, view the [Sending guidelines](references\u002FSENDING.md).\n\nQuick example using the Resend SDK for Node.js:\n\n```tsx\nimport { Resend } from 'resend';\nimport { WelcomeEmail } from '.\u002Femails\u002Fwelcome';\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:\u002F\u002Fexample.com\u002Fverify\" \u002F>\n});\n\nif (error) {\n  console.error('Failed to send:', error);\n}\n```\n\nThe Node SDK automatically handles the plain-text rendering and HTML rendering for you.\n\n## Internationalization\n\nSee [references\u002FI18N.md](references\u002FI18N.md) for complete i18n documentation.\n\nReact Email supports three i18n libraries: next-intl, react-i18next, and react-intl.\n\n### Quick Example (next-intl)\n\n```tsx\nimport { createTranslator } from 'next-intl';\nimport {\n  Html,\n  Body,\n  Container,\n  Text,\n  Button,\n  Tailwind,\n  pixelBasedPreset\n} from '@react-email\u002Fcomponents';\n\ninterface EmailProps {\n  name: string;\n  locale: string;\n}\n\nexport default async function WelcomeEmail({ name, locale }: EmailProps) {\n  const t = createTranslator({\n    messages: await import(\\`..\u002Fmessages\u002F\\${locale}.json\\`),\n    namespace: 'welcome-email',\n    locale\n  });\n\n  return (\n    \u003CHtml lang={locale}>\n      \u003CTailwind config={{ presets: [pixelBasedPreset] }}>\n        \u003CBody className=\"bg-gray-100 font-sans\">\n          \u003CContainer className=\"max-w-xl mx-auto p-5\">\n            \u003CText className=\"text-base text-gray-800\">{t('greeting')} {name},\u003C\u002FText>\n            \u003CText className=\"text-base text-gray-800\">{t('body')}\u003C\u002FText>\n            \u003CButton href=\"https:\u002F\u002Fexample.com\" className=\"bg-blue-600 text-white px-5 py-3 rounded\">\n              {t('cta')}\n            \u003C\u002FButton>\n          \u003C\u002FContainer>\n        \u003C\u002FBody>\n      \u003C\u002FTailwind>\n    \u003C\u002FHtml>\n  );\n}\n```\n\nMessage files (\\`messages\u002Fen.json\\`, \\`messages\u002Fes.json\\`, etc.):\n\n```json\n{\n  \"welcome-email\": {\n    \"greeting\": \"Hi\",\n    \"body\": \"Thanks for signing up!\",\n    \"cta\": \"Get Started\"\n  }\n}\n```\n\n## Email Best Practices\n\n1. **Test across email clients** - Test in Gmail, Outlook, Apple Mail, Yahoo Mail. Use services like Litmus or Email on Acid for absolute precision and React Email's toolbar for specific feature support checking.\n\n2. **Keep it responsive** - Max-width around 600px, test on mobile devices.\n\n3. **Use absolute image URLs** - Host on reliable CDN, always include \\`alt\\` text.\n\n4. **Provide plain text version** - Required for accessibility and some email clients.\n\n5. **Keep file size under 102KB** - Gmail clips larger emails.\n\n6. **Add proper TypeScript types** - Define interfaces for all email props.\n\n7. **Include preview props** - Add \\`.PreviewProps\\` to components for development testing.\n\n8. **Handle errors** - Always check for errors when sending emails.\n\n9.  **Use verified domains** - For production, use verified domains in \\`from\\` addresses.\n\n## Common Patterns\n\nSee [references\u002FPATTERNS.md](references\u002FPATTERNS.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- Email templates with custom fonts\n\n## Additional Resources\n\n- [React Email Documentation](https:\u002F\u002Freact.email\u002Fdocs\u002Fllms.txt)\n- [React Email GitHub](https:\u002F\u002Fgithub.com\u002Fresend\u002Freact-email)\n- [Resend Documentation](https:\u002F\u002Fresend.com\u002Fdocs\u002Fllms.txt)\n- [Email Client CSS Support](https:\u002F\u002Fwww.caniemail.com)\n- Component Reference: [references\u002FCOMPONENTS.md](references\u002FCOMPONENTS.md)\n- Internationalization Guide: [references\u002FI18N.md](references\u002FI18N.md)\n- Common Patterns: [references\u002FPATTERNS.md](references\u002FPATTERNS.md)\n",{"name":5,"license":15,"metadata":47,"description":7},{"author":48,"version":49},"Resend","1.1.0","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fresend\u002Freact-email",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill react-email",{"tool":65,"command":66},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill react-email",{"tool":68,"command":69},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill react-email","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fresend\u002Freact-email\u002FSKILL.md",true,[73,79,83,87,91,95,99,103],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"README.md","REFERENCE","参考文档",1784,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fresend\u002Freact-email\u002FREADME.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002FCOMPONENTS.md",11331,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fresend\u002Freact-email\u002Freferences\u002FCOMPONENTS.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002FI18N.md",14368,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fresend\u002Freact-email\u002Freferences\u002FI18N.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002FPATTERNS.md",22142,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fresend\u002Freact-email\u002Freferences\u002FPATTERNS.md",{"path":92,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002FSENDING.md",3262,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fresend\u002Freact-email\u002Freferences\u002FSENDING.md",{"path":96,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002FSTYLING.md",7481,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fresend\u002Freact-email\u002Freferences\u002FSTYLING.md",{"path":100,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":101,"sourceHtmlUrl":102},"skill-report.json",12082,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fresend\u002Freact-email\u002Fskill-report.json",{"path":104,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":105,"sourceHtmlUrl":106},"TESTS.md",21484,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fresend\u002Freact-email\u002FTESTS.md",[108,120,130,139,145,152],{"skillNo":109,"name":110,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":116,"publishedAt":42},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[117,118,119],"model","model hierarchy","model hierarchy skill",{"skillNo":121,"name":122,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":42},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[125],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},[127,128,129],"MCP","zoom","zoom mcp",{"skillNo":131,"name":132,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":42},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[136,137,138,128],"sdk","zoom apps sdk","apps",{"skillNo":140,"name":141,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":42},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[141],{"skillNo":146,"name":147,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":42},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[150],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},[147],{"skillNo":153,"name":154,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":42},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[154]]