Results for “transaction”

Design and implement transactional and marketing email templates. Use when asked to "build an email template", "transactional email", "welcome email", "password reset email", "email design", "React Email", "MJML", "dark mode email", or "email copy review". Inbox / SPF / spam → enhance-email-deliverability.

Identify a North Star Metric and 3-5 supporting input metrics, classify the business game (Attention, Transaction, Productivity), and validate against seven criteria for an effective North Star.

Installs and routes to official Loops.so agent skills (API, CLI, LMX, email best practices) for transactional and marketing email. Use when integrating Loops, sending transactional mail, auditing deliverability, or when the user mentions Loops.so — not for Content Factory `.cursor/loops/` workflow loops.

Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. This includes the Loops HTTP API and official SDKs for server-side contact, contact-property, mailing-list, event, API-key-validation, transactional-email, content editing (campaigns, campaign groups, transactional groups, audience segments, email messages, themes, and components), and workflow inspection. Trigger on phrases like "Loops API", "Loops SDK", "create a campaign via API", "update email message LMX", "send a Loops event from my app", "add a contact to Loops in a webhook", "send a transactional email from backend code", or any time the user wants to integrate Loops into their app, backend, webhook, or automation. Do not trigger for CLI or shell-only requests.

Analyzes and documents a two-track design system with cinematic dark marketing pages and light transactional surfaces, including color palettes, typography hierarchy, and component vocabulary.