36 lines
2.4 KiB
Markdown
36 lines
2.4 KiB
Markdown
# Welcome Email Pattern
|
|
|
|
When drafting a welcome/onboarding email for a new Hermes user, **first load the `email-style-guide` skill** for the full formatting rules. The welcome email follows the Gemini-derived style rules.
|
|
|
|
## Formatting requirements
|
|
|
|
- `## Title` + `---` divider (per style guide)
|
|
- `###` section headers only -- no H4+
|
|
- **Bold lead-ins** for paragraph context
|
|
- **Ordered lists** (1. 2. 3.) for accomplishments -- NOT bullet dashes, NOT em dashes
|
|
- **Unordered lists** (hyphens) for simple groupings
|
|
- Hyphens not em dashes, full words not contractions, "example:" not "e.g."
|
|
- No raw URLs -- all links in `[Action Description](URL)` format
|
|
- H2 rendered as `<h2>` in HTML, H3 as `<h3>`, `---` as the red accent `<hr>`
|
|
|
|
## Section structure (in order)
|
|
|
|
1. **Heading + divider:** `## Welcome to Hermes, [Name].` then `---`
|
|
2. **What Hermes Is:** paragraph explaining Hermes as a personal AI agent on a private server
|
|
3. **What We've Built:** ordered list (1. 2. 3.) of real accomplishments the main user has achieved with their agent. Each item: bold lead-in + hyphen + description. Example: "1. **Task name** - What was accomplished."
|
|
4. **Email:** two bold lead-in paragraphs. First asks if they want their email set up ("Yahoo access."). Second states the permission policy: Sho'Nuff will not act without explicit approval.
|
|
5. **Backup & Safety:** unordered list (hyphens) of backup layers: live sync, daily backup, provider snapshots, standby recovery, model fallback.
|
|
6. **Getting Started with Telegram:** three numbered steps. Step 1 = create bot via BotFather. Step 2 = get user ID via userinfobot. Step 3 = reply with token + ID + email decision.
|
|
7. **Commands:** unordered list of useful Hermes commands (/queue, /retry, /undo, /clear, /title, /goal, /compress).
|
|
8. **Server Details:** minimal -- primary model (provided by main user) and backup model (built in). No IPs, no SSH, no local model address.
|
|
9. **Close:** Sho'Nuff signature with random closing quote (no "Thanks" or "Regards").
|
|
|
|
## Delivery workflow
|
|
|
|
1. Draft the full email with body + signature
|
|
2. Send draft to Germaine (g@germainebrown.com) for approval, BCC him
|
|
3. After approval, send to the recipient (e.g. browo955@yahoo.com), BCC Germaine
|
|
4. From: `shonuff@germainebrown.com`
|
|
|
|
The style guide (`email-style-guide` skill) has the definitive rules for HTML rendering, closing quotes, rotating titles, and signature anatomy. Load it before composing the email.
|