bridge-greetinglisted

Context-aware terminal greeting (MOTD) for Bridge instances — renders a per-instance logo, palette, today's filtered calendar, the instance's "Doing" board and uncommitted work, resolved from which org folder the terminal was opened in. Includes gen-logo.py (ANSI-Shadow logo generator from a word) and the branding convention that feeds every Bridge UI. Trigger: "/bridge-greeting", "terminal greeting", "motd", "startup logo", "instance logo", "terminal greeting", "fastfetch logo", "branding", "generate logo", "per-folder terminal", "folder logo".
bks-lab/open-bridge · ★ 8 · AI & Automation · score 74

Install: claude install-skill bks-lab/open-bridge

# Bridge Greeting A login-shell greeting that is **instance-aware**: the org folder you open the terminal in resolves to a Bridge instance, and the greeting then shows that instance's identity — logo, colours, calendar tags, task board, and repos. Home / unknown dirs → the full system dashboard (fastfetch cascade + global board). Inside an org tree → a focused panel for the resolved instance. ## The model — branding belongs to the Bridge, not the script The greeting reads its visual identity from the **resolved instance's theme** (`themes/<theme>.yaml` → `branding:` block), so a logo "comes from" its Bridge instance the same way `identity/agent/` and vocabulary do. Three layers: | Layer | Owns | Tier | |---|---|---| | **Engine** (`scripts/render-motd.sh`) | discovery, rendering, board parsing — no instance literals | CORE → open-bridge | | **Theme branding** (`themes/<theme>.yaml` `branding:`) | logo path, `logo_color_1/2`, `calendar_tags` per instance | per-instance | | **Local override** (`~/.config/fastfetch/bridge-motd.local.sh`) | per-org fallbacks for instances whose theme has no `branding:` yet; the org→instance machine map | USER (machine-local, never committed) | Discovery scans `~/Developer/*/*/bridge-config.yaml` to build the org-folder → instance map automatically — no hardcoded instance names in the engine. ## Purpose tagline �� the instance's north-star under the logo When the resolved instance's `bridge-config.yaml` has a non-empty `purpose.statement`,