# open/close the menu (registered UI actions):
POST /ui/invoke {"id": "samples-menu.open"}     # and "samples-menu.close"

# list what the menu shows (id, label, blurb):
GET /claude/sample-prompts

[{"id":"thread-my-demo","label":"My demo","blurb":"one line","prompt":"the full prompt text"}]

---
name: hd-lightbulb
description: >
  The LIGHTBULB menu (sample prompts) in Hydrogen Desktop's title bar — the 💡
  button just right of the Adom logo (top-left, 0.1.265+; it lived by the CPU/RAM
  badges before). Each item opens a FRESH Claude AI thread and
  types a curated demo prompt for the user (parts search, KiCad/Fusion, pup,
  native browser, adom-tsci, shotlog, webviews, hands-free, "Speak Adom"
  shorthand training). Covers: how items run, the samples-menu.open/close AI
  commands, GET /claude/sample-prompts, and sample-prompts.json — the overlay
  file that adds or rewords prompts WITHOUT a new HD release. Trigger words:
  lightbulb, light bulb menu, sample prompts, samples menu, demo prompts, sample
  threads, speak adom, add a sample prompt, sample-prompts.json.
---

# hd-lightbulb — the sample-prompts (💡) menu

The **lightbulb button** just right of the Adom logo in HD's title bar (moved there
0.1.265 — the AI work happens on the left where VS Code lives) opens a menu of curated sample
prompts. Picking one opens a **new Claude conversation** in the editor and
human-types the prompt (open → ready → type → verify → submit, all verified) —
the user just watches it run. It exists to teach by DOING: each prompt
demonstrates a capability end to end.

## Current lineup (0.1.260+)

Full tour (everything at once) · Adom parts search · KiCad · Fusion 360 ·
Altium · pup (AI-driven browser) · Native Chrome/Edge · Google Workspace ·
chip-fetcher · adom-tsci (build a board) · shotlog · Webview panels ·
Hands-free (TTS) · **Speak Adom (wv, pup, nb...)** — teaches the popular Adom
shorthand with a cheat sheet in a wv and a quick quiz.

## Drive it as an AI

```bash
# open/close the menu (registered UI actions):
POST /ui/invoke {"id": "samples-menu.open"}     # and "samples-menu.close"

# list what the menu shows (id, label, blurb):
GET /claude/sample-prompts
```

## Where the list comes from (three layers, later wins)

1. **Compiled defaults** in the HD build (offline fallback).
2. **The wiki list** (0.1.263+): `lightbulb-prompts/prompts.json` on the HD wiki
   page — the fleet-wide lineup, updated INDEPENDENTLY of HD releases. HD checks
   it on every menu open (debounced 15 min) plus every 4 hours during business
   hours (Mon-Fri 7am-7pm local); a changed list pops into an open menu live.
   Cache: `%APPDATA%\hydrogen-desktop\sample-prompts-remote.json`. Docs + PR
   guide: the [Lightbulb Prompts sub-readme](https://wiki.adom.inc/adom/hydrogen-desktop/files/lightbulb-prompts/README.md).
3. **The user's local file** `%APPDATA%\hydrogen-desktop\sample-prompts.json` —
   personal overrides, always wins:

```json
[{"id":"thread-my-demo","label":"My demo","blurb":"one line","prompt":"the full prompt text"}]
```

- A **new id** appends a menu item; a **matching id** overrides a lower layer
  (label/blurb, and the prompt body if non-empty).
- Any `thread-*` id routes to the runner automatically — no code change needed.
- Bad JSON (local or wiki) is logged and ignored — the menu never breaks.
- To contribute a prompt for EVERYONE: PR `lightbulb-prompts/prompts.json` in the
  hydrogen-desktop repo (see the sub-readme above for the rules).

Prompts are written in the user's casual first-person voice, as ONE flat
paragraph (a typed newline would submit early). Never edit John's compiled
prompt bodies without permission; add new ids instead.