agentsclimarketplace

Email template rendering

Skill javicasper/memory-forge/examples/monorepo/apps/notifications/.claude/skills/email-template-rendering

CLI-agnostic continuous learning for AI coding agents. Supports Claude Code, OpenCode, Codex, Cursor. Monorepo-ready with distributed docs and skills.

Install
npx -y skills add javicasper/memory-forge --skill email-template-rendering

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Fix for Handlebars email template rendering issues in the notifications app. Use when: "Missing helper", template variables not rendering, partials not found, HTML escaping issues in emails. Only loads when working in apps/notifications/.

SKILL.md

2.8 KB, as published. Nobody here has run it

Email Template Rendering Fixes

Problem

Handlebars templates for email notifications fail to render correctly, showing raw variables, missing helpers, or escaped HTML.

Trigger Conditions

  • Error: Missing helper: "formatDate"
  • Variables showing as {{variable}} in sent emails
  • Error: The partial X could not be found
  • HTML appearing escaped (&lt;div&gt; instead of <div>)
  • Working in apps/notifications/ directory

Solution

Issue 1: Missing Helpers

Register custom helpers before compiling templates:

import Handlebars from 'handlebars';

// Register helpers BEFORE compiling templates
Handlebars.registerHelper('formatDate', (date: Date, format: string) => {
  return dayjs(date).format(format);
});

Handlebars.registerHelper('formatCurrency', (amount: number, currency: string) => {
  return new Intl.NumberFormat('en-US', {
    style: 'currency',
    currency: currency || 'USD',
  }).format(amount);
});

// Now compile
const template = Handlebars.compile(templateSource);

Issue 2: HTML Escaping

Use triple braces for unescaped HTML:

{{! WRONG - HTML will be escaped }}
<div>{{htmlContent}}</div>

{{! CORRECT - HTML renders as-is }}
<div>{{{htmlContent}}}</div>

Or use SafeString in helpers:

Handlebars.registerHelper('renderHtml', (html: string) => {
  return new Handlebars.SafeString(html);
});

Issue 3: Partials Not Found

Register partials before use:

// Register partial
Handlebars.registerPartial('header', headerTemplateSource);
Handlebars.registerPartial('footer', footerTemplateSource);

// Use in template
// {{> header}}
// ... content ...
// {{> footer}}

Issue 4: Async Data in Templates

Handlebars is synchronous. Resolve all data before rendering:

// WRONG
const template = Handlebars.compile(source);
const html = template({ user: await getUser() }); // ❌ Promise in template

// CORRECT
const user = await getUser();
const orders = await getOrders(user.id);
const template = Handlebars.compile(source);
const html = template({ user, orders }); // ✅ Resolved data

Verification

  1. Compile template without errors
  2. Render with sample data
  3. Check output HTML is correct
  4. Send test email and verify in email client

Notes

  • This skill only loads when working in apps/notifications/
  • Always precompile templates in production for performance
  • Test emails in multiple clients (Gmail, Outlook, Apple Mail)
  • Use inline CSS for email compatibility

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.