SKILL-027 Emails and notifications Locked skill

Email template system

Every email shares one base layout; templates only render a body and declare the variables they need — preview them in dev before they ever ship.

01

What this skill helps you build

A reusable base layout, per-email templates with typed variables, a dev preview, plain-text alternatives, and localization.

The production takeaway

Every email shares one base layout; templates only render a body and declare the variables they need — preview them in dev before they ever ship.

02

Inside this skill

The full skill expands these implementation areas with decisions, edge cases, prompts, tests, and framework-specific code.

Emails and notifications
What this helps you build

A consistent email template system : one shared layout header, footer, brand styling, unsubscribe link that wraps every message, plus small per email templates that render only the

🔒
Emails and notifications
When to use this

Reach for this the moment you send more than one or two kinds of email and want them to look and behave consistently. Concretely: You have several transactional emails welcome, pas

🔒
Emails and notifications
The core idea

There is one base layout and many small body templates . The layout owns everything shared — the <head , inlined CSS, header, footer, and unsubscribe link — and exposes a single sl

🔒
03

Unlock the full implementation

Paid access includes the complete skill body, implementation prompt, common mistakes, production checklist, and code examples where this skill includes them.