37signals-mailer

Generate minimal Action Mailer classes for transactional emails with templates and previews.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/joshyorko/agent-skills --skill 37signals-mailer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 37signals-mailer
Source: https://github.com/joshyorko/agent-skills/tree/main/plugins/rails-37signals-patterns/skills/37signals-mailer
Command: npx skills add https://github.com/joshyorko/agent-skills --skill 37signals-mailer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates minimal, focused Action Mailer classes that standardize transactional emails and reduce inbox noise by bundling notifications for users across accounts.

Core Features & Use Cases

  • Minimal mailers for transactional emails (mentions, comments, invitations) with both text and HTML templates.
  • Account-aware from and reply-to contexts, plus development previews for easy verification.
  • Digest-style or bundled notifications to minimize message fatigue while preserving essential information.
  • End-to-end patterns including simple mailers, templating, previews, and background delivery using deliver_later.

Quick Start

Generate a CommentMailer and a DigestMailer and wire them to deliver_later in your Rails app.

Frequently Asked Questions about 37signals-mailer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bundle Rails notifications into a digest email to reduce inbox noise?

Bundled digest emails in Rails consolidate multiple notifications—like mentions, comments, and assignments—into a single message to reduce message fatigue. You create minimal Action Mailer classes that group these transactional events for users across accounts.

How do I set up account-aware from and reply-to contexts in Action Mailer?

Account-aware from and reply-to contexts are set by configuring the Action Mailer class to dynamically pass the specific account's sender and reply addresses. This ensures transactional emails are properly routed and scoped to the correct account context.

What's the best way to structure minimal Action Mailer classes for transactional emails?

The best way to structure minimal Action Mailers is generating focused classes for specific events like invitations or comments, paired with both text and HTML templates. This composable pattern keeps mailers lean while standardizing transactional email delivery.

Can I use Action Mailer previews to verify transactional email templates in development?

Yes, Action Mailer previews allow you to verify transactional email templates in development. The pattern includes setting up development previews to easily inspect both text and HTML templates before sending actual notifications.

Does this Rails mailer pattern support background delivery and unsubscribe handling?

Yes, the pattern supports background delivery using deliver_later and includes unsubscribe support. These end-to-end features handle the complete lifecycle of transactional emails, from queuing the delivery job to managing user opt-outs.

When should I use bundled digest notifications instead of individual transactional emails?

Use bundled digest notifications when users receive frequent mentions, comments, or assignments across accounts, causing message fatigue. Digests preserve essential information while minimizing inbox noise, whereas individual emails are better for urgent, standalone alerts.