Run any Skill in Manus with one click

update-email-templates

Stars1,890

Forks123

UpdatedMay 26, 2026 at 22:06

Update Authgear email templates using the correct source files, translation files, and commit order. Use when editing email wording, email structure, or subject lines.

Installation

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.

Run Skill in Manus

Source

authgear

authgear/authgear-server

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	update-email-templates
description	Update Authgear email templates using the correct source files, translation files, and commit order. Use when editing email wording, email structure, or subject lines.

Update Email Templates

Follow this workflow whenever updating email templates.

Scope Rules

Only edit source template files:
- resources/authgear/templates/en/messages/*.txt.gotemplate
- resources/authgear/templates/en/messages/*.mjml.gotemplate
Do not edit generated template files directly:
- resources/authgear/templates/en/messages/*.txt
- resources/authgear/templates/en/messages/*.mjml
In *.txt.gotemplate and *.mjml.gotemplate, use translations from:
- resources/authgear/templates/en/messages/translation.json
Always edit English templates only at source stage.
- Do not manually update non-en locales in source-edit commits.
Email subject translations are defined in:
- resources/authgear/templates/en/translation.json

Workflow

Edit source templates first:
- resources/authgear/templates/en/messages/*.txt.gotemplate
- resources/authgear/templates/en/messages/*.mjml.gotemplate
- resources/authgear/templates/en/messages/translation.json (body/content translations)
- resources/authgear/templates/en/translation.json (subject translations)
Generate .mjml from .mjml.gotemplate:
- go run ./scripts/generatemjml/main.go -i resources/authgear/templates
Commit source edits and generated .mjml in one commit.
Before regenerating non-English translations, delete the changed keys from all non-en locale files so the generator knows to recreate them:
- For en/messages/translation.json changes, delete the top-level key (e.g. UsageAlert, not UsageAlert.Alert.Title) from all non-en messages/translation.json files:
  - make templates-translation-json-del-key KEY=<TopLevelKey>
- For en/translation.json subject changes, delete the changed key from all non-en translation.json files:
  - make translation-json-del-key KEY=<key>
- Run once per changed top-level key.
In a separate commit, generate non-English translations:
- make -C scripts/python generate-translations
- Requires being logged in to Claude: claude login
- If not logged in, stop and ask the user to run claude login first.
Finally, generate HTML emails:
- make html-email

Commit Boundaries (Required)

Commit 1:
- Source edits (*.gotemplate, en/messages/translation.json, optional en/translation.json)
- Generated .mjml
Commit 2:
- Generated non-English translations (make -C scripts/python generate-translations)
Commit 3:
- Generated email HTML artifacts (make html-email)

Do not combine generated artifacts (.html, .txt, non-en translations) in the same commit as source *.gotemplate edits.

More from this repository

same repository

bootstrap-local-dev

authgear/authgear-server

Set up a fresh authgear-server development environment from scratch. Use when onboarding a new contributor, setting up a new machine, or when the user says "set up local dev from scratch" / "first-time setup". Covers the asdf + Homebrew install path on macOS; Nix users should follow CONTRIBUTING.md directly.

2026-06-231.9k

dep-audit

authgear/authgear-server

Audit and fix dependency vulnerabilities in Go and Node.js packages. Runs govulncheck for Go and npm audit for each package.json directory. Commits fixes directory by directory.

2026-06-221.9k

add-go-test

authgear/authgear-server

Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.

2026-05-131.9k

write-implementation-plan

authgear/authgear-server

Draft or update detailed implementation plans for authgear-server specs, design changes, and docs/plans files. Use when Codex needs to turn a spec or outdated plan into a concrete implementation plan with exact files, exact methods, runtime call flow, compatibility requirements, test coverage, and atomic commit steps.

2026-05-131.9k

write-e2e-test

authgear/authgear-server

Write end-to-end (e2e) tests for authgear-server. Use when the user asks to write, add, or create e2e tests. The tests live in e2e/tests/ and are YAML-driven.

2026-05-131.9k

new-siteadmin-api

authgear/authgear-server

Full pipeline for adding a new Site Admin API feature — from OpenAPI spec through implementation plan to working service. Use when adding a new endpoint or filling in real data for an existing stub.

2026-04-271.9k

name	update-email-templates
description	Update Authgear email templates using the correct source files, translation files, and commit order. Use when editing email wording, email structure, or subject lines.

Update Email Templates

Follow this workflow whenever updating email templates.

Scope Rules

Only edit source template files:
- resources/authgear/templates/en/messages/*.txt.gotemplate
- resources/authgear/templates/en/messages/*.mjml.gotemplate
Do not edit generated template files directly:
- resources/authgear/templates/en/messages/*.txt
- resources/authgear/templates/en/messages/*.mjml
In *.txt.gotemplate and *.mjml.gotemplate, use translations from:
- resources/authgear/templates/en/messages/translation.json
Always edit English templates only at source stage.
- Do not manually update non-en locales in source-edit commits.
Email subject translations are defined in:
- resources/authgear/templates/en/translation.json

Workflow

Edit source templates first:
- resources/authgear/templates/en/messages/*.txt.gotemplate
- resources/authgear/templates/en/messages/*.mjml.gotemplate
- resources/authgear/templates/en/messages/translation.json (body/content translations)
- resources/authgear/templates/en/translation.json (subject translations)
Generate .mjml from .mjml.gotemplate:
- go run ./scripts/generatemjml/main.go -i resources/authgear/templates
Commit source edits and generated .mjml in one commit.
Before regenerating non-English translations, delete the changed keys from all non-en locale files so the generator knows to recreate them:
- For en/messages/translation.json changes, delete the top-level key (e.g. UsageAlert, not UsageAlert.Alert.Title) from all non-en messages/translation.json files:
  - make templates-translation-json-del-key KEY=<TopLevelKey>
- For en/translation.json subject changes, delete the changed key from all non-en translation.json files:
  - make translation-json-del-key KEY=<key>
- Run once per changed top-level key.
In a separate commit, generate non-English translations:
- make -C scripts/python generate-translations
- Requires being logged in to Claude: claude login
- If not logged in, stop and ask the user to run claude login first.
Finally, generate HTML emails:
- make html-email

Commit Boundaries (Required)

Commit 1:
- Source edits (*.gotemplate, en/messages/translation.json, optional en/translation.json)
- Generated .mjml
Commit 2:
- Generated non-English translations (make -C scripts/python generate-translations)
Commit 3:
- Generated email HTML artifacts (make html-email)

Do not combine generated artifacts (.html, .txt, non-en translations) in the same commit as source *.gotemplate edits.