majiayu000 The preview is for visual verification before sending - it shows how the newsletter will "feel" with proper branding applied.
What does the user want?
- "preview the newsletter" → Preview existing markdown
- "convert to HTML" → Same as preview
- "refresh design" / "update design tokens" → Re-extract from website
- "download assets" → Re-download brand images
Is there a specific file?
- If user specifies a file, use that
- Otherwise, use the latest
output/newsletter_*.md
Does the user want to see it in browser?
- Default: Yes, open via Playwright MCP
- If user says "just generate" → Create HTML only
| User Intent | Workflow |
|---|---|
| Preview newsletter / see how it looks | workflows/preview-newsletter.md |
| Refresh design / update styles | workflows/extract-design.md |
| Re-download brand assets | workflows/download-assets.md |
User: "preview the newsletter"
→ Route to: workflows/preview-newsletter.md
The workflow will:
- Find the latest newsletter markdown in
output/ - Convert to HTML using the template and design tokens
- Open in browser via Playwright MCP
- Take a screenshot for reference
workflows/extract-design.md
Re-extract design elements (colors, fonts) from catskillcrew.com using Playwright. Use when the website design has changed.
workflows/download-assets.md
Re-download brand assets (logo, divider images) from catskillcrew.com. Use when assets need refreshing.