원클릭으로
email-best-practices
Send transactional email through Resend with exactly-once delivery, deliverability, and accessible HTML.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Send transactional email through Resend with exactly-once delivery, deliverability, and accessible HTML.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Build Remotion videos with remocn — a shadcn registry of copy-paste animation components and timeline-driven UI primitives. Use when composing video scenes, adding text animations, transitions, backgrounds, UI blocks, brand/social cards, or full compositions in a Remotion project. Triggers include "remocn", "video component", "add animation", "text reveal", "scene transition", "product demo video", "remotion component", "typewriter", "terminal simulator", "glass code block", and the UI-primitive tier: "video dialog", "video button", "command menu", "video select", "video tooltip". Even if the user doesn't mention remocn, activate when they need polished video primitives for Remotion.
Use when creating, modifying, or reviewing an installable Eve agent under registry/<slug> in the evex repository.
Deliver Eve agents end to end. Use when creating, modifying, testing, or deploying an Eve agent.
Scope and ship a brand-aligned pack of SVG assets for SaaS products. Use when the user wants a visual pack, feature launch assets, icons, empty states, hero illustrations, badges, feature graphics, onboarding visuals, changelog art, or dashboard/modal graphics.
Make page content citable by AI search — extractable structure, authority signals, and machine-readable files. Use when writing page body copy for AI visibility.
Apply on-page SEO checks when building a single branded HTML page — metadata, headings, schema, links, and images.
SOC 직업 분류 기준
| name | email-best-practices |
| description | Send transactional email through Resend with exactly-once delivery, deliverability, and accessible HTML. |
Guidance for building deliverable, accessible, exactly-once transactional emails sent through an email API such as Resend. Apply the rules below whenever an email is being drafted or sent.
Network issues, timeouts, and server errors can leave a send's outcome uncertain. Retrying without protection duplicates the email. Use an idempotency key: a stable value derived from the business event, sent with the request, so a retried send with the same key returns the original outcome instead of issuing a second email.
See sending-reliability for the idempotency and
retry model, including key derivation, provider cache windows, and Resend { data, error }
handling.
The sender domain must be authenticated (SPF/DKIM/DMARC) and the sender address verified by the provider. Unverified senders are the most common cause of bounces and spam filtering — Gmail and Yahoo reject unauthenticated email outright.
Email must be readable by screen readers, dark-mode clients, translation tools, and AI clients, not just sighted readers on a default inbox.
lang and dir on <html> and on <body>'s direct children (some clients strip
them from <html>).<title> that names the specific email, not just the brand.<h1> and nest <h2>/<h3> in order. Never skip levels or fake headings with
bold text.role="presentation".alt; decorative images need an explicit alt="".See accessibility for the full checklist and priority order.