Template editor + send queue + delivery log — the transactional-email surface for a B2B app.
Three-pane workspace for managing transactional emails. Template list on the left, editor in the middle (subject + body + variable picker), and a preview + delivery log on the right. Includes variable substitution preview so the marketer or ops user can verify before sending.
Each section pre-wired with the right CleenUI primitives. Swap, remove, or extend any of them — the template is a starting point, not a constraint.
Left rail with templates grouped by type.
Subject line, body, variable picker, save state.
Rendered with sample values so what-you-see-is-what-the-customer-sees.
Recent sends with delivery status, opens, clicks.
All of these are in the catalog — the Builder skill imports them automatically. Each chip links to that component's page.
When the Builder skill scaffolds this template for you, these are the fields it asks about — or infers from your prompt.
Ask your AI agent to scaffold this template in your project — the Builder skill knows the Email Engine layout and the components it uses.
Two paths to your first component. Pick the one that fits how your team builds.
One prompt to your AI tool. The Setup skill handles dependencies, design tokens, build config, and component registration — all without leaving your editor.
The classic flow. Install the package, import the styles, drop in your first component. No agents required — same end result.