mirror of
https://github.com/boxpositron/absolute-dotfiles.git
synced 2026-10-24 16:33:19 +00:00
David Ibia
ea570af409
- Move the vendored skills from .config/opencode/skills to .config/omo/skills, with provenance and local changes in its README - Rewrite Impeccable's script paths to ~/.omo/agent/skills/impeccable so its detector and live-server verbs resolve under omo - frontend-workflow hands screenshots to a visual-engineering task instead of opencode run - Move the notes commands and /impeccable to .config/omo/prompts as omo prompt templates; setup-mcp stays behind because it writes opencode.json - Archive DEVELOPMENT-WORKFLOW.md and UI-WORKFLOW.md under .config/omo/archive; nothing loads them - link-ai-configs.sh links the skills into omo and Claude Code only and stops linking OpenCode's config, TUI, plugins and workflow docs - setup-mac.sh and Brewfile.apps stop installing OpenCode; README and .withcontextconfig.jsonc follow the new layout ~/.config/opencode/AGENTS.md stays linked: omo's rules engine reads it before ~/.claude/CLAUDE.md and stops at the first hit, so it carries the shared preferences and keeps OMC's instructions out of omo.
114 lines
2.3 KiB
Markdown
114 lines
2.3 KiB
Markdown
# Email Copy Guidelines
|
|
|
|
## Contents
|
|
- Structure
|
|
- Formatting
|
|
- Tone
|
|
- Length
|
|
- CTA Buttons vs. Links
|
|
- Personalization (merge fields, dynamic content, triggered emails)
|
|
- Segmentation Strategies (by behavior, by stage, by profile)
|
|
- Testing and Optimization (what to test, how to test, metrics to track)
|
|
|
|
## Structure
|
|
|
|
1. **Hook**: First line grabs attention
|
|
2. **Context**: Why this matters to them
|
|
3. **Value**: The useful content
|
|
4. **CTA**: What to do next
|
|
5. **Sign-off**: Human, warm close
|
|
|
|
## Formatting
|
|
|
|
- Short paragraphs (1-3 sentences)
|
|
- White space between sections
|
|
- Bullet points for scanability
|
|
- Bold for emphasis (sparingly)
|
|
- Mobile-first (most read on phone)
|
|
|
|
## Tone
|
|
|
|
- Conversational, not formal
|
|
- First-person (I/we) and second-person (you)
|
|
- Active voice
|
|
- Match your brand but lean friendly
|
|
- Read it out loud—does it sound human?
|
|
|
|
## Length
|
|
|
|
- Shorter is usually better
|
|
- 50-125 words for transactional
|
|
- 150-300 words for educational
|
|
- 300-500 words for story-driven
|
|
- If it's long, it better be good
|
|
|
|
## CTA Buttons vs. Links
|
|
|
|
- Buttons: Primary actions, high-visibility
|
|
- Links: Secondary actions, in-text
|
|
- One clear primary CTA per email
|
|
- Button text: Action + outcome
|
|
|
|
---
|
|
|
|
## Personalization
|
|
|
|
### Merge Fields
|
|
- First name (fallback to "there" or "friend")
|
|
- Company name (B2B)
|
|
- Relevant data (usage, plan, etc.)
|
|
|
|
### Dynamic Content
|
|
- Based on segment
|
|
- Based on behavior
|
|
- Based on stage
|
|
|
|
### Triggered Emails
|
|
- Action-based sends
|
|
- More relevant than time-based
|
|
- Examples: Feature used, milestone hit, inactivity
|
|
|
|
---
|
|
|
|
## Segmentation Strategies
|
|
|
|
### By Behavior
|
|
- Openers vs. non-openers
|
|
- Clickers vs. non-clickers
|
|
- Active vs. inactive
|
|
|
|
### By Stage
|
|
- Trial vs. paid
|
|
- New vs. long-term
|
|
- Engaged vs. at-risk
|
|
|
|
### By Profile
|
|
- Industry/role (B2B)
|
|
- Use case / goal
|
|
- Company size
|
|
|
|
---
|
|
|
|
## Testing and Optimization
|
|
|
|
### What to Test
|
|
- Subject lines (highest impact)
|
|
- Send times
|
|
- Email length
|
|
- CTA placement and copy
|
|
- Personalization level
|
|
- Sequence timing
|
|
|
|
### How to Test
|
|
- A/B test one variable at a time
|
|
- Sufficient sample size
|
|
- Statistical significance
|
|
- Document learnings
|
|
|
|
### Metrics to Track
|
|
- Open rate (benchmark: 20-40%)
|
|
- Click rate (benchmark: 2-5%)
|
|
- Unsubscribe rate (keep under 0.5%)
|
|
- Conversion rate (specific to sequence goal)
|
|
- Revenue per email (if applicable)
|