:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
import type { AiFirstSuggestion } from 'scenes/max/aiFirstCreate/AiFirstCreateScene'
import { AttachedContextItem } from '~/layout/ai/attachedContext'
import { MessageTemplate } from './types'
// Own dismiss groups: a dismissal is global and never resets, so a chip closed on a workflow must not strip this page.
// The picked template has its own group so removing its attachment clears the pick and nothing else.
const NEW_TEMPLATE_DISMISS_GROUP = 'new-email-template-composer'
export const PICKED_TEMPLATE_DISMISS_GROUP = 'new-email-template-picked'
const DESIGNING_EMAIL_TEMPLATES_SKILL = 'designing-email-templates'
export const NEW_TEMPLATE_AGENT_HEADLINES: string[] = ['What email would you like to create today?']
/** Prefills the composer when a saved template is picked. The person finishes the sentence. */
export const PICKED_TEMPLATE_PROMPT = 'Using this template, create a new email template that '
export const NEW_TEMPLATE_SUGGESTIONS: AiFirstSuggestion[] = [
{
title: 'Welcome email',
description: 'Greet new signups and point them to a first step',
prompt: 'Create a welcome email for new signups that introduces the product and points them to a first step',
},
{
title: 'Product update',
description: 'Announce a new feature with one call to action',
prompt: 'Create a product update email that announces a new feature with one call to action',
},
{
title: 'Finish onboarding',
description: 'Remind people who have not finished setup',
prompt: 'Create an email that reminds people who have not finished setup, with a link to continue',
},
{
title: 'Monthly newsletter',
description: 'A short intro and three highlights',
prompt: 'Create a monthly newsletter email with a short intro and three highlights',
},
{
title: 'Win back inactive users',
description: 'Reach out after 30 days of silence',
prompt: 'Create a win-back email for people who have not used the product in 30 days',
},
{
title: 'Event invitation',
description: 'Invite people to a webinar with a sign-up button',
prompt: 'Create an event invitation email for a webinar with the date, time and a sign-up button',
},
]
// All static strings below are our own build-time constants, which is what makes them safe to attach
// as trusted `instructions` items. The picked template rides an untrusted item, and the instruction
// refers to it by type only, so no user-entered name reaches trusted context.
const TOOLING_CONTEXT_ITEM: AttachedContextItem = {
type: 'instructions',
hidden: true,
dismissGroup: NEW_TEMPLATE_DISMISS_GROUP,
value:
`The user is starting a new email template from a description. Load the ${DESIGNING_EMAIL_TEMPLATES_SKILL} ` +
'skill before your first tool call; it covers the email design JSON schema and the design guidelines. Act ' +
'through the exec workflows-*-email-template commands (workflows-create-email-template, ' +
'workflows-get-email-template, workflows-patch-email-template, workflows-update-email-template, ' +
'workflows-show-email-template). Do not search for tools; use the exec `info <tool>` command when you ' +
'need a full input schema.',
}
// The fastest useful outcome from nothing is a saved template in the editor, refined with the agent alongside.
const DRAFT_FIRST_CONTEXT_ITEM: AttachedContextItem = {
type: 'instructions',
hidden: true,
dismissGroup: NEW_TEMPLATE_DISMISS_GROUP,
value:
'If an email_template context item is attached, call workflows-get-email-template with its id first and use ' +
'that design as the starting point; keep its layout and styling unless the user asks for changes, and never ' +
'modify the attached template itself. Then make workflows-create-email-template your next tool call and do ' +
'not ask clarifying questions first: save a name, a subject, a plain-text fallback and a first design. The ' +
'editor opens the template the moment it exists and reloads external edits live, so refine the design ' +
'afterwards with workflows-patch-email-template and finish with workflows-show-email-template.',
}
const SKILL_CHIP_CONTEXT_ITEM: AttachedContextItem = {
type: 'skill',
key: DESIGNING_EMAIL_TEMPLATES_SKILL,
label: 'Designing email templates skill',
dismissGroup: NEW_TEMPLATE_DISMISS_GROUP,
// Not dismissible: the page only advances once the template exists.
dismissible: false,
}
/** The picked template as untrusted context: a ref the agent fetches, plus the html the composer shows as a thumbnail. */
export function pickedTemplateContextItem(template: MessageTemplate): AttachedContextItem {
return {
type: 'email_template',
key: template.id,
label: template.name || 'Unnamed template',
previewHtml: template.content?.email?.html,
dismissGroup: PICKED_TEMPLATE_DISMISS_GROUP,
}
}
/** Skill pointer plus the draft-first instruction, and the picked template when there is one. */
export function buildNewTemplateComposerContext(pickedTemplate: MessageTemplate | null): AttachedContextItem[] {
const items = [TOOLING_CONTEXT_ITEM, SKILL_CHIP_CONTEXT_ITEM, DRAFT_FIRST_CONTEXT_ITEM]
return pickedTemplate ? [...items, pickedTemplateContextItem(pickedTemplate)] : items
}