Menu
Write or update transactional emails rendered from Markdown via the EmailService. Use when adding templates, wiring new sends, or adjusting email metadata.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run, write, and troubleshoot Japa browser tests that use Playwright; use when you add or change frontend functionality that should be covered by tests
Writing documentation. Use when key functionality is added or changed
Caching with @adonisjs/cache (keys, tags, invalidation). Use when adding or debugging cache behavior.
Lucid models/migrations conventions and safe workflows. Use when changing schema or models.
Frontend rules and React Router conventions. Use when working with frontend-related tasks.
Background job conventions (BullMQ via @rlanz/bull-queue). Use when adding or editing jobs.
| name | transactional-emails |
| description | Write or update transactional emails rendered from Markdown via the EmailService. Use when adding templates, wiring new sends, or adjusting email metadata. |
app/services/email_service/email_service.ts turns resources/views/emails/*.edge Markdown into HTML with Dimer, injects it into resources/views/emails/base.edge, and queues delivery through mail.sendLater + BullMQ (app/jobs/send_mail_job.ts). The first line must be a # heading; it becomes the subject and is stripped from the body.app/services/email_service/email_specs.ts with from (env-backed) and optional dummyData. The key must match the Edge filename. Missing spec entries or views log errors at boot.resources/views/emails/<key>.edge as Markdown. Variables come from the state passed to EmailService.send. Static templates (no state) are cached in production; include a leading # Title to avoid runtime errors.EmailService and call emailService.send('<key>', { to, state?, bcc? }). bcc: true adds EMAIL_OWNER. state is optional; omit it for static emails..react-router files. Keep templates minimal—no duplicate logic; rely on services instead of inline data fetching.