Update to Sent

{
  "name": "template-builder-ui",
  "description": "Designs and audits tenant-facing Sent template builders, previews, validation, lifecycle UX, and API payload mapping. Use for template editor forms, variables, channel overrides, WhatsApp review, RCS suggestion chips, authentication templates, and safe submission flows.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 219
    },
    {
      "relative_path": "references/template-status-handling.md",
      "size_in_bytes": 1794
    },
    {
      "relative_path": "references/template-ui-wireflows.md",
      "size_in_bytes": 2110
    },
    {
      "relative_path": "references/template-validation-matrix.md",
      "size_in_bytes": 2868
    }
  ],
  "skill_md_contents": "---\nname: template-builder-ui\ndescription: Designs and audits tenant-facing Sent template builders, previews, validation, lifecycle UX, and API payload mapping. Use for template editor forms, variables, channel overrides, WhatsApp review, RCS suggestion chips, authentication templates, and safe submission flows.\n---\n\n# Sent Template Builder UI\n\nDesign the interface around Sent's v3 `definition` contract. The UI may import Meta material, but its canonical saved and submitted model must never be Meta's `components[]` payload.\n\n## Product model\n\nUse one draft object with:\n\n- optional `category` and `language`;\n- required `definition.body.multiChannel`;\n- optional complete body overrides for `sms`, `whatsapp`, and `rcs`;\n- optional `definition.header`, `footer`, `buttons`, `definitionVersion`, and `authenticationConfig`;\n- submission controls for `creation_source`, `submit_for_review`, and `sandbox`.\n\nDo not expose top-level create fields named `name`, `channels`, `body`, `header`, or `buttons`. If the product needs an internal display label, keep it outside the Sent create payload.\n\n## Recommended editor sequence\n\n1. Capture intent and category.\n2. Write the `multiChannel` body.\n3. Insert variables as structured entities.\n4. Add optional per-channel overrides.\n5. Add header, footer, and buttons where supported.\n6. Review live previews and accessibility.\n7. Validate locally and with `sandbox: true`.\n8. Save a draft, then explicitly submit for provider review.\n\nCategory should not block the first keystroke, but it must be visible before submission because it affects authentication rules and WhatsApp policy review.\n\n## Variable UX\n\nInserting a variable creates both:\n\n- a placeholder such as `{{0:variable}}`; and\n- a matching entity with `id`, `name`, `type`, and `props.sample`.\n\nRenumber atomically when variables move. Never let users edit placeholder syntax independently of the entity table. Show a clear error for naked `{{1}}` or IDs without definitions.\n\n## Validation matrix\n\nApply the exact rules in [references/template-validation-matrix.md](references/template-validation-matrix.md), including:\n\n- a 1,024-character maximum for every body;\n- 60 characters for header and footer;\n- no footer variables;\n- 10 buttons total;\n- button types `QUICK_REPLY`, `URL`, `VOICE_CALL`, `PHONE_NUMBER`, and `COPY_CODE` with their per-type limits;\n- no invented quick-reply-versus-CTA exclusivity;\n- `authenticationConfig` and authentication restrictions;\n- complete, independently valid channel overrides.\n\nRun the bundled `waba-template-author` linter against serialized JSON. Server validation remains authoritative.\n\n## Channel previews\n\n### SMS\n\nPreview plain text and estimated GSM/UCS-2 segments. Make clear that segment estimates affect billing and are not template body limits.\n\n### WhatsApp\n\nPreview header, body, footer, and buttons. Show sample values, category, language, and provider-review impact.\n\n### RCS\n\nCurrent Sent RCS guidance supports text plus up to four suggestion chips. Rich cards, carousels, and media attachments are roadmap capabilities, not current Sent builder controls. Do not generate capability declarations for unavailable features.\n\nChannel routing belongs to the send flow, not the template editor. If routing is shown in a simulator:\n\n- omitted `channel` or `[\"sent\"]` means automatic routing and fallback;\n- `[\"rcs\"]` pins RCS with no cross-channel fallback;\n- multiple explicit values mean broadcast and separate billable messages.\n\nNever describe an explicit RCS-plus-SMS array as ordered fallback.\n\n## Save and review behavior\n\nUse `sandbox: true` for validation. Save with `submit_for_review: false`. Before switching it to `true`, show:\n\n- category and language;\n- rendered previews with sample values;\n- channel overrides;\n- button actions;\n- any warnings;\n- the fact that provider review is an external state change.\n\nDo not autosubmit on save.\n\n## Lifecycle UX\n\nResource status values currently include `DRAFT`, `PENDING`, `APPROVED`, `REJECTED`, and `PAUSED`. Keep an unknown-state renderer.\n\nWhatsApp template webhook events use `field: \"templates\"`, no `sub_type`, and no `event`; the status is `payload.status`. Provider values can include `CATEGORY_UPDATED`, `DISABLED`, and other future strings. See [references/template-status-handling.md](references/template-status-handling.md).\n\n## Accessibility and failure recovery\n\n- Associate every error with a field and a summary.\n- Do not rely on preview color alone.\n- Preserve user edits after validation failures.\n- Keep raw JSON inspection available for advanced users.\n- Label imported Meta JSON as “Meta Cloud API source” until converted.\n- Provide a diff for server normalization and provider-driven category/status changes.\n\nUse [references/template-ui-wireflows.md](references/template-ui-wireflows.md) for state transitions. Use `waba-template-author` for copy and policy judgment, `sent-templates` for existing-resource operations, and `rcs-agent-onboarding` for RCS launch readiness.\n"
}