react-email
Build responsive HTML emails with React Email components. Covers email structure (Html, Head, Body, Container), content components (Text, Heading, Button, Link, Img), layout (Section, Row, Column), styling with inline CSS and Tailwind, custom fonts, preview text, and rendering to HTML. Use when creating transactional emails, marketing templates, or email design systems. Use for email rendering, preview, Tailwind email styling, and provider integration with Resend, Nodemailer, or SendGrid.
What this skill does
# React Email
## Overview
React Email is a library for building responsive HTML emails using React components. It provides a set of unstyled, accessible components that render to email-client-compatible HTML. Supports inline styles, Tailwind CSS via a wrapper component, custom web fonts, and rendering to both HTML and plain text.
**When to use:** Transactional emails (welcome, password reset, receipts), marketing templates, email design systems, any project that renders emails server-side.
**When NOT to use:** Static HTML email templates with no dynamic content, projects that already use a dedicated email builder (MJML, Maizzle), or when you only need plain-text emails.
## Quick Reference
| Pattern | API | Key Points |
| ------------------ | ---------------------------------------- | ----------------------------------------------------------- |
| Document structure | `Html`, `Head`, `Body` | `Html` wraps everything, `Head` loads fonts/meta |
| Content container | `Container` | Centers content, sets `max-width` |
| Layout grid | `Section`, `Row`, `Column` | Table-based layout for email clients |
| Text content | `Text`, `Heading` | `Heading` accepts `as` prop for h1-h6 |
| Links | `Link` | Standard anchor, `href` required |
| Call-to-action | `Button` | Renders as link styled as button, `href` required |
| Images | `Img` | Always set `width`, `height`, `alt` |
| Divider | `Hr` | Horizontal rule between sections |
| Inbox preview | `Preview` | Sets preview text shown in inbox list |
| Custom fonts | `Font` | Place inside `Head`, set `webFont` and `fallbackFontFamily` |
| Tailwind styling | `Tailwind` | Wraps email, inlines Tailwind classes at render |
| Render to HTML | `render(<Email />)` | Async, returns HTML string |
| Render plain text | `render(<Email />, { plainText: true })` | Strips HTML, returns text |
| Pretty output | `render(<Email />, { pretty: true })` | Formatted HTML for debugging |
| Preview server | `email dev` | Local dev server with hot reload |
| Markdown content | `Markdown` | Renders Markdown as email-compatible HTML |
| Code blocks | `CodeBlock` | Syntax-highlighted code with theme support |
| Inline code | `CodeInline` | Monospace inline code spans |
## Common Mistakes
| Mistake | Correct Pattern |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------- |
| Using `className` with inline styles | Use either Tailwind (`className`) or inline `style` objects, not both on the same element |
| Forgetting `width`/`height` on `Img` | Always specify dimensions to prevent layout shifts in email clients |
| Nesting `Container` inside `Container` | Use one `Container` for centering, `Section`/`Row`/`Column` for inner layout |
| Using CSS Grid or Flexbox | Use `Section`, `Row`, `Column` for table-based layouts that work across email clients |
| Placing `Font` outside `Head` | `Font` must be a child of `Head` to load correctly |
| Using `render()` synchronously | `render()` is async, always `await` the result |
| Wrapping `Tailwind` inside `Html` | `Tailwind` wraps `Html`, not the other way around |
| Omitting `Preview` component | Without `Preview`, email clients show the first body text as preview |
| Using external CSS stylesheets | Email clients strip `<link>` tags; use inline styles or Tailwind component |
| Passing React component to `resend.emails.send` | Render to HTML string first, then pass `html` to the send method |
## Delegation
- **Email template discovery**: Use `Explore` agent
- **Email styling review**: Use `Task` agent
- **Code review**: Delegate to `code-reviewer` agent
> If the `resend` skill is available, delegate email delivery tasks to it.
> Otherwise, recommend: `npx skills add oakoss/agent-skills --skill resend`
## References
- [Built-in components: structure, content, and layout](references/components.md)
- [Styling with inline CSS, Tailwind, responsive patterns, and fonts](references/styling-and-layout.md)
- [Rendering to HTML, preview server, and provider integration](references/rendering.md)
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.