fix: correct hero:theme protocol in skills and establish single source of truth #59

New issue

Closed

opened 2026-03-19 14:39:12 +00:00 by mik-tf · 0 comments

mik-tf commented

2026-03-19 14:39:12 +00:00

Owner

Problem

The hero_ui_dashboard skill documented the wrong postMessage type (hero-os-theme) for iframe theme sync. All production repos (hero_redis, hero_foundry_ui, hero_aibroker) use hero:theme with a vars object for CSS variable injection and a hero:theme-ready readiness signal — none of which were documented.

The web_embed skill had no mention of theme sync at all, despite being the natural home for cross-service iframe protocols.

Solution

web_embed becomes the single source of truth for the hero:theme postMessage protocol (message format, canonical receiver snippet, CSS variable rules, standalone fallback)
hero_ui_dashboard references web_embed for the protocol and keeps only dashboard-specific UI (toggle button, icon logic)

Related: lhumina_code/hero_aibroker#17

## Problem The `hero_ui_dashboard` skill documented the wrong postMessage type (`hero-os-theme`) for iframe theme sync. All production repos (hero_redis, hero_foundry_ui, hero_aibroker) use `hero:theme` with a `vars` object for CSS variable injection and a `hero:theme-ready` readiness signal — none of which were documented. The `web_embed` skill had no mention of theme sync at all, despite being the natural home for cross-service iframe protocols. ## Solution - **`web_embed`** becomes the single source of truth for the `hero:theme` postMessage protocol (message format, canonical receiver snippet, CSS variable rules, standalone fallback) - **`hero_ui_dashboard`** references `web_embed` for the protocol and keeps only dashboard-specific UI (toggle button, icon logic) Related: https://forge.ourworld.tf/lhumina_code/hero_aibroker/issues/17