Email Love

braze-liquid

Write, review, and debug Liquid personalization in Braze email, push, in-app message, SMS, WhatsApp, Content Card, and Banner templates. Use this skill whenever someone is writing Braze personalization tags or Liquid logic, asks why a Braze message rendered blank or was aborted, is building abandoned-cart or catalog product loops, is working with Connected Content, Content Blocks, catalogs, or Canvas entry properties, hits an "Unexpected end token" error or an unexplained abort in the Message Activity Log, or shares Braze template code and wants it checked. Trigger on "Braze Liquid", "custom_attribute", "connected_content", "abort_message", "Canvas entry property", or Braze campaign and Canvas personalization questions even when Liquid is not named. Braze-only, and do not apply it to Shopify, Customer.io, or other Liquid platforms, whose tag sets and variable syntax differ. Works on any email HTML, not only Email Love exports; also covers Braze emails built in Figma with the Email Love plugin.

customerio-liquid

Write, review, and debug Liquid personalization in Customer.io emails, SMS, push, in-app messages, webhooks, and snippets. Use this skill whenever someone is writing Liquid for Customer.io, asks why a Customer.io message shows as Failed or Undeliverable, is building loops over event or object data, is working with snippets, layouts, journey attributes, collections, or trigger data, hits a composer error like "if tag was never closed" or "Unidentified method", or shares Customer.io template code and wants it checked. Trigger on "Customer.io liquid", "customer.attribute", "trigger data", "journey attribute", "cio_link", or Customer.io campaign and broadcast personalization questions even when Liquid is not named. Customer.io-only, and do not apply it to Braze, Shopify, or Klaviyo, whose namespaces, tags, and error behavior differ. Works on any email HTML, not only Email Love exports; also covers Customer.io emails built in Figma with the Email Love plugin.

email-love-design-system-migration

Audit and migrate an entire legacy email design system or library into an Email Love Figma design system. Use when the user asks to assess migration readiness, inventory legacy email modules, determine source fidelity or scale, create Email Love foundations, convert a legacy library in batches, or migrate templates from Figma, a local folder, cloud storage, or a supported ESP. The source remains read-only and all conversion happens in a separate target Figma file. Do not use for building one campaign email; use email-love-figma-builder for that.

email-love-figma-builder

Build export-ready marketing and lifecycle emails inside Figma using Email Love components or the Email Love design-converter workflow. Use whenever the user asks to create, assemble, draft, convert, or build an email or email campaign in Figma; mentions Email Love, email design systems, mj-wrapper frames, ESP export, or AI Import; shares an email campaign brief with a Figma file; or asks to turn an existing email or Figma comp into an exportable email. Supports both customers with an existing Email Love design system and customers creating their first email without one. Do not use for migrating an entire legacy email design system; use email-love-design-system-migration for that.

email-love-figma-quality-gates

Audit an Email Love Figma design-system migration batch or reusable module before it is approved. Use for independent QA, completion review, or regression checks involving mobile icon geometry, real image fills, cropped social icons, component-property semantics, source fidelity, Email Love structure, or differences between the Figma canvas and the Email Love plugin Preview/export. Do not use this skill to build, migrate, or repair the modules themselves; route those tasks to the Email Love Builder, Design System Migration, or Template Repair skill first, then return here for acceptance.

email-love-template-repair

Diagnose and repair an existing Email Love email template or reusable module in Figma when the plugin rejects it, the canvas and export disagree, content flattens into images, Outlook clips text, mobile stacking or spacing is wrong, links or images fail, dark mode breaks, or component properties stop working. Use for targeted repair of Email Love structures that already exist. Do not use to create a new campaign, convert an ordinary Figma comp, or migrate a legacy library; route those to email-love-figma-builder or email-love-design-system-migration.

hubspot-hubl

Write, review, and debug HubL personalization in HubSpot marketing email — coded templates, custom modules, and programmable email. Use whenever someone writes HubSpot personalization tokens or HubL logic, asks why a token rendered blank, why a filter on a contact token did nothing in an email, or why an email template will not publish, is building crm_object / crm_objects / crm_associations loops, is working with programmable email, single-send API customProperties, smart content, or the CAN-SPAM footer tokens, or shares HubSpot template code to be checked. Trigger on "HubL", "personalization_token", "crm_objects", "isEnabledForEmailV3Rendering", "programmable email", or "Jinjava", even when HubL is not named. HubL is Jinjava, HubSpot's Java fork of Jinja2 — it reads like Jinja2 or Liquid but is neither. HubSpot-only; not for MoEngage Jinja, Braze or Shopify Liquid, or Customer.io. Works on any email HTML, not only Email Love exports; also covers HubSpot emails built in Figma with the Email Love plugin.

iterable-handlebars

Write, review, and debug Handlebars personalization code for Iterable email, SMS, push, in-app, and snippet templates. Use whenever someone writes merge tags or dynamic content for Iterable, asks why a personalization renders blank or shows raw {{curly braces}} in a sent message, is building abandoned-cart or product-recommendation loops over shoppingCartItems, catalogs, collections, or data feeds, needs conditional or date-based content in an Iterable template, hits a HandlebarsExecutionError or an unexplained send skip, or shares an Iterable template snippet and wants it checked. Trigger even when the user just says "Iterable merge tag", "why isn't my first name showing", "dynamic content in Iterable", or pastes Handlebars alongside an Iterable question, without naming Handlebars. Iterable-only — do not use it for Klaviyo, Customer.io, or Braze, which use Liquid-style templating. Works on any email HTML, not only Email Love exports; also covers Iterable emails built in Figma with the Email Love plugin.

klaviyo-django

Write, review, and debug personalization code in Klaviyo email, SMS, and push templates. Use this skill whenever someone is writing merge tags, conditionals, or dynamic blocks in Klaviyo, asks why a personalization renders blank or why a template will not preview, is building abandoned-cart or product loops over event data or catalog items, needs conditional show/hide logic or date formatting in a Klaviyo template, hits "Could not parse the remainder" or a skipped send, or shares Klaviyo template code and wants it checked. Trigger on "Klaviyo variable", "Klaviyo personalization", "Klaviyo dynamic block", "event.extra.line_items", or Klaviyo flow and campaign template questions, even when the templating language is not named. Klaviyo-only, and note that Klaviyo uses Django templates, NOT Liquid, so do not apply this skill to Braze, Customer.io, Shopify, or other Liquid platforms. Works on any email HTML, not only Email Love exports; also covers Klaviyo emails built in Figma with the Email Love plugin.

marketo-velocity

Write, review, and debug personalization in Adobe Marketo Engage emails — tokens and Velocity email scripting. Use this skill whenever someone is writing Marketo tokens or an Email Script token, asks why a token renders literally or a default value is ignored, is looping over custom objects or opportunities, needs conditional or date-formatted content in a Marketo email, hits a Velocity compile error or an email that fails to send, or shares Marketo template code and wants it checked. Trigger on "Marketo token", "my token", "Velocity", "email script token", "{{lead.", "$lead", "custom object in Marketo", or Marketo email personalization questions even when the mechanism is not named. Marketo Engage only — do not apply it to Salesforce Marketing Cloud, Iterable, Klaviyo, Braze, or Customer.io. Works on any email HTML, not only Email Love exports; also covers Marketo emails built in Figma with the Email Love plugin.

moengage-jinja

Write, review, and debug Jinja personalization in MoEngage email campaigns, plus push, SMS, WhatsApp, and on-site messages where the behaviour differs. Use this skill whenever someone is writing MoEngage Jinja, asks why a MoEngage campaign reached fewer users than the segment, says users dropped from a campaign or the message was not sent to some users, is choosing a fallback, is looping a ProductSet or recommendation, or is calling a Content API. Trigger on "MOE_NOT_SEND", "UserAttribute", "EventAttribute", "ProductSet", "ContentApi", "getAuxData", "personalization failed", "After Personalization Removal", or MoEngage campaign personalization questions even when Jinja is not named. MoEngage-only. It looks like stock Jinja2 and like HubSpot HubL, so do not apply it to HubSpot, Braze, or Customer.io, whose namespaces, fallback forms, and null handling are different. Works on any email HTML, not only Email Love exports; also covers MoEngage emails built in Figma with the Email Love plugin.

sailthru-zephyr

Write, review, and debug Zephyr personalization in Zeta Engage by Sailthru — HTML and Visual templates, campaigns, transactional and triggered sends, subject lines, code snippets, hosted pages, and Lifecycle Optimizer. Use whenever someone writes Sailthru template code, asks why a Sailthru email went out empty or never went out at all, is looping over or filtering a data feed, or shares Sailthru template code and wants it checked. Trigger on "Zephyr", "Sailthru template", "content library", "Lifecycle Optimizer", "empty email sent", `{foreach}`, `{if}`, `{* *}`, `assert()`, `cancel()`, `filter_content()`, `personalize()`, or `profile.vars` even when the language is not named. Zephyr and Sailthru only. Do not apply it to Zeta Marketing Platform, whose ZML language is Liquid-derived and uses double braces and percent tags, and do not apply it to Liquid, Handlebars, or Django platforms. Works on any email HTML, not only Email Love exports; also covers Sailthru emails built in Figma with the Email Love plugin.