Embed Creator

Author or modify a Datex Studio embed (configurationTypeId=20) on a branch — a thin UI component whose entire surface is a single <iframe>. An embed renders either an external URL (a hosted map, dashboard, document viewer) or an in-memory HTML string (a generated email/report preview) and is almost always opened as a dialog via $shell.open<referenceName>Dialog(...) (prefixed with the embed's package when it's registered under a module).

References

• ../datex-studio-shared/branch-setup.md — Branch/connection selection (shared across skills)
• references/embeds.md — Authoritative embed authoring reference: file shape, minimal-valid skeleton, the iframe-only rule, the data: URI HTML-string pattern, dialog wiring, the print pattern, CSP caveats, pre-flight checklist
• ../datex-studio-conventions/file-format.md — configurationTypeId table and the TypeScript-expression encoding rule (applies to iframeConfig.href)
• ../datex-studio-conventions/naming-conventions.md — _embed/-embed suffix, filename-stem matching, display-name rule
• ../datex-studio-runtime/runtime-globals.md — platform-injected globals available in embed code ($embed, $shell, $datasources, $utils, ...)
• ../form-creator/references/forms.md — sibling component; pick a form when you need field controls/buttons alongside the content (the form-vs-embed decision)
• ../component-wiring-check/references/component-wiring.md — host reference contracts, vars-must-be-declared rule, moduleId rule for the component that opens the embed

Dependencies

• requirements-gathering skill — invoked to produce a requirements brief if one doesn't already exist in the conversation context
• form-creator skill — invoked when the requirement actually needs field controls or a toolbar next to the content (an embed is iframe-only; it has no button surface)
• component-wiring-check skill — invoked to audit the configParameters ↔ inParams contract on the component that opens the embed before push