go-cms-mail

What problem does it solve? Building a mail feature into a modular Go CMS requires coordinating templating, site-scoped data, asynchronous job queues, SMTP transports, attachment authorization, and delivery history without leaking feature logic into the core kernel. This Skill provides the architectural rules and boundaries to implement that mail module correctly. ## Core Features & Use Cases - Site-scoped mail templates: Define templates with stable codes, typed data.* variables, backend-authoritative site.* variables, and per-site uniqueness so multiple sites reuse codes independently. - Immutable queued messages with jobs/outbox: Render once at queue time, persist an immutable Message plus durable outbox atomically, and let workers deliver with bounded retry and terminal-failure classification. - Attachment and permission model: Distinguish static, manual, site-field, automatic persistent, and transient spool attachments with correct authorization semantics for each source class. - Use Case: When adding a feedback-notification email to a CMS site, use this Skill to design the template CRUD, preview/send flow, SMTP transport alias configuration, delivery attempt history, and runtime-drain lifecycle so profile changes never corrupt in-flight mail. ## Quick Start Ask the AI to design the Go CMS mail module with site-scoped templates, an asynchronous send job, and transient attachment spooling following this Skill's rules.