--- name: ravi-email-writing description: Best practices for writing high-quality emails that look professional and avoid spam filters. Reference this before composing, replying, or forwarding emails with ravi-email-send. --- # Email Writing Guide Write emails that look like they came from a real person — not an AI. Good email hygiene improves deliverability, avoids spam filters, and gets responses. ## Subject Lines - **40-60 characters** — long subjects get truncated on mobile - **Be specific** — "Q3 metrics review for Acme project" beats "Update" - **No ALL CAPS** — spam filters penalize this heavily - **Avoid spam triggers** — "free", "act now", "limited time", "click here", "urgent", "guaranteed", "no obligation" - **Match the tone** — casual for teammates, professional for external contacts ## HTML Body Structure The `--body` argument in `ravi email compose` accepts HTML. Always use semantic tags — never pass plain text. **Note:** `--subject` is only used with the compose command. Reply and forward commands auto-derive the subject from the original message (prepending `Re:` or `Fwd:`). **Do this:** ```html

Opening line that states the purpose.

Supporting details in a second paragraph.

Closing with a clear next step or ask.

Best,
IDENTITY_NAME

``` **Don't do this:** ```html Plain text with no tags at all Or this:

Using br chains

instead of paragraphs ``` **Rules:** - Always wrap text in `

` tags - Use `

` for section headers (not `

`) - Use `