engineer-platform-web

Integrate the Braze Web SDK in Smart TVs, browser extensions, and strict CSP contexts.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-platform-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineer-platform-web
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/engineer-platform-web
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-platform-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables reliable Braze Web SDK deployments in non-standard browser environments and security-constrained contexts where the default web assumptions (service workers, cookies, inline scripts) do not hold, reducing integration failures and runtime feature gaps.

Core Features & Use Cases

  • Smart TV integration: Guidance for Tizen and webOS including use of the core bundle, ES5 concerns, disabling push maintenance, and implementing custom rendering for in-app messages and Content Cards.
  • Browser extensions: Initialization patterns for Manifest V3 and storage substitutes for persistent device IDs; guidance on manifest CSP and permission considerations.
  • Content Security Policy: Nonce propagation via contentSecurityNonce, required connect-src/script-src/img-src directives, and options to avoid unsafe-inline or unsafe-eval by using the NPM/bundled SDK.
  • Accessibility & frontend engineering lens: Checklist for WCAG conformance, focus management, ARIA roles, and testing approaches for custom templates.

Quick Start

Initialize the Braze Web SDK for your target environment by instructing the assistant to initialize with the appropriate flags (for Smart TVs set disablePushTokenMaintenance and manageServiceWorkerExternally to true; for extensions persist deviceId in chrome.storage; for strict CSP pass contentSecurityNonce).

Frequently Asked Questions about engineer-platform-web

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I initialize the Braze Web SDK on a Smart TV using Tizen or webOS?

To initialize the Braze Web SDK on Tizen or webOS Smart TVs, use the core bundle and set initialization flags like disablePushTokenMaintenance and manageServiceWorkerExternally to true, ensuring compatibility by disabling default service worker assumptions and implementing custom UI rendering.

Can I use the Braze Web SDK in a Manifest V3 browser extension?

Yes, you can use the Braze Web SDK in Manifest V3 browser extensions by persisting the device identifier externally using chrome.storage instead of cookies, and configuring manifest Content Security Policy permissions to allow required SDK domains.

How do I configure Content Security Policy headers to avoid unsafe-inline when loading the Braze Web SDK?

To avoid unsafe-inline or unsafe-eval under strict Content Security Policy, load the Braze Web SDK via the NPM or bundled version and propagate a contentSecurityNonce value, specifying required connect-src, script-src, and img-src directives.

Why does Braze Web SDK initialization fail in non-standard browser environments?

Braze Web SDK initialization fails in non-standard environments because default web assumptions like service workers, cookies, and inline scripts do not hold, requiring you to disable push token maintenance and externally manage service workers for compatibility.

What accessibility considerations are needed for custom Braze Content Card templates?

Custom Braze Content Card templates require WCAG conformance checks, proper focus management, and appropriate ARIA roles to ensure accessibility, along with dedicated testing approaches for the frontend engineering lens.

Do I need to manage service workers externally for Braze Web SDK integrations on Smart TVs?

Yes, you need to set manageServiceWorkerExternally to true during Braze Web SDK initialization on Smart TVs to externally manage service workers and prevent runtime feature gaps in environments where default service workers are unsupported.