What problem does it solve? Building transactional emails that render correctly across mail clients like Gmail and Outlook is error-prone: inline SVG logos break, links point to the wrong host, nullable user names produce broken greetings, and queued notifications silently never send. This Skill encodes the Toollab project's proven conventions for its six Blade email templates so new or modified emails work the first time. ## Core Features & Use Cases - Template conventions: Enforces the required HTML structure (600px width, <style> in head, #343C6A button, inline color: white), the hosted PNG logo partial (never SVG), and French-language content rules. - Link and variable handling: Distinguishes app.url (API, for images) from app.frontend_url (clickable links), mandates urlencode() on emails, and handles nullable first_name/last_name. - Testing workflow: Guides verification in Maildev, including running queue:work since 5 of 6 notifications implement ShouldQueue. - Use Case: When adding a new transactional notification (e.g., an enrollment confirmation), follow the checklist to copy the staff-invitation structure, wire the logo partial, build front URLs correctly, and verify rendering in Maildev. ## Quick Start Create a new transactional email template for the payment reminder notification following the emails-templates conventions and verify it in Maildev.
