Definitions
Public Made by Adomby adom
Use when the user asks "what is [term]", "define [term]", "what does [term] mean", "glossary", "definitions", or needs clarification on Adom platform terminology.
Fire on browser task-phrases + add a 'when the user says browser' routing pitch (pup vs nb vs wv, hc qualifier)
Ask (2 small changes to the definitions skill, for the Hydrogen launch):
TRIGGERS: add task-phrase triggers so the skill fires when a user says a browser TASK, not only "what is X": "browser", "open in browser", "open in the browser", "show in browser", "open my web app", "preview my app", "which browser should I use". definitions is in adom/core, so this covers BOTH h and hc — it is the only skill in the bootstrap tree positioned to catch the bare word "browser" on day one.
ROUTING PITCH: in the Browser Control section, add a 3-line "when the user says browser" decision: AI needs to drive/show/test -> pup (SAY "pup" so users learn the word; on h, ab is bundled so pup is always there); user wants it in THEIR browser (their logins / hand-off) -> nb; docked preview next to the editor -> wv. Qualifier for hc: pup requires Bridge (ab) — if not connected, use wv and offer the Bridge install.
Why: hydrogen-bootstrap -> core + adom-bridge. pup's own skill is getting into the ab tree (issue filed on adom/adom-bridge today), but the vocabulary-level routing ("browser" -> which surface, and teaching users to say pup / nb) belongs in definitions, which both platforms already ship. Context: John hardening browser auto-discovery before the Hydrogen launch (2026-08-10).
0 Replies
Log in to reply.