← Commit history

Hero: Windows title bar + app-name kicker + ≥90px gutter (conform to adom-wiki-hero-image); README: skillpack mandatory sections

John Lauer ·6bf351f489 ·4mo ago ·parent 0e5f5ae
2 files changed +60−63
README.md+60−63
@@ -2,97 +2,94 @@  **DigiKey's catalog — millions of parts, real-time stock and quantity pricing — one command away.** +`adom-digikey` is the single-vendor DigiKey tool for the Adom ecosystem: one Rust binary with three+faces — a JSON **CLI**, a first-class **Hydrogen webview app**, and the shared **backend service**+that powers `service-digikey` and feeds [`adom-parts-search`](/adom/adom-parts-search). -`adom-digikey` is the single-vendor DigiKey tool for the Adom ecosystem — one Rust binary, three-faces:+## Install -- **CLI** — `adom-digikey search | part | health` for quick JSON-returning shell use and BOMs.-- **Hydrogen app** — `adom-digikey app` opens a searchable UI as a first-class Hydrogen tab.-- **Backend service** — `adom-digikey serve` runs the shared proxy (port 8777) that powers the-  `service-digikey` container and feeds [`adom-parts-search`](/adom/adom-parts-search).+```bash+adompkg install adom-digikey+``` -It replaces the old `gallia/services/digikey` + MCP setup: no MCP server, no Adom Viewer.+## Quick start  ```bash-adompkg install adom-digikey+# One-shot search (auto-detects backend, falls back to a direct DigiKey call) adom-digikey search "BME280"-``` -## Real-time stock, straight to the bench+# Interactive UI as a Hydrogen tab+adom-digikey app -DigiKey shines when you need it *today*. Every card shows live stock, qty-1 price and the full-break ladder, lead time, RoHS and lifecycle — and DigiKey's deep catalog means the obscure sensor-or alt part is usually right there.+# One exact part+adom-digikey part "296-TPS62840DLCRCT-ND"+```++## Screenshots -![adom-digikey results for a BME280 humidity sensor — Bosch, alternatives from Sensirion, with stock, pricing and interface attributes](/blob/app/adom-digikey/screenshots/results-sensors.png)+### Real-time stock, straight to the bench+DigiKey shines when you need it today. Every card shows live stock, qty-1 price + the break ladder,+lead time, RoHS and lifecycle — and the deep catalog means the obscure sensor or alt is right there. -## Find the exact part, and its alternates+![adom-digikey results for a BME280 humidity sensor — Bosch plus Sensirion alternatives with stock, pricing and interface attributes](/blob/app/adom-digikey/screenshots/results-sensors.png) -Search a function (`buck regulator 1A SOT-23`) or a precise MPN. DigiKey's parametric data lets the-cards surface the specs that actually drive a decision — Iq, Iout, Vin range, package — so the-substitute is one glance away when the first choice is out.+### The exact part, and its alternates+Search a function (`buck regulator 1A SOT-23`) or a precise MPN; parametric data surfaces the specs+that drive the decision, so the substitute is one glance away when the first choice is out.  ![adom-digikey results for a TPS62840 buck regulator with alternates from TI and Monolithic Power, showing current, input range and price breaks](/blob/app/adom-digikey/screenshots/results-buck.png) -## Scriptable from the first keystroke+### Scriptable from the first keystroke+`search`/`part`/`health` return JSON — pipe to `jq`, a BOM, or another Claude step. -`search` returns JSON; `part` fetches one MPN; `health` checks the backend's OAuth token. Pipe it-into `jq`, a BOM, or another Claude step.+![Terminal showing adom-digikey search piped to jq for the first component, then a health check reporting the backend OAuth fresh](/blob/app/adom-digikey/screenshots/cli.png) -![Terminal showing adom-digikey search piped to jq for the first component, then a health check reporting the backend OAuth is fresh](/blob/app/adom-digikey/screenshots/cli.png)+## Dependencies -```bash-adom-digikey search "TPS62840DLCR" | jq '.components[0]'-adom-digikey part "296-TPS62840DLCRCT-ND"-adom-digikey health-```+| Dependency | Required? | Why |+|---|---|---|+| `service-digikey` backend (`adom-digikey serve`) | Recommended | Manages the DigiKey OAuth handshake + token refresh + cache; the CLI auto-detects it |+| Direct DigiKey API | Fallback | Used automatically when no backend is reachable | -## Install+## Features -```bash-adompkg install adom-digikey-```+- **Three faces** — CLI verbs, a Hydrogen webview app, and the shared backend service.+- **OAuth handled for you** — the backend does the DigiKey v4 handshake + token refresh.+- **Deep catalog + parametrics** — millions of parts; cards surface the spec that matters.+- **The go-to alternate** — when Mouser is out or long-lead, [`adom-parts-search`](/adom/adom-parts-search) flips to DigiKey automatically. -## How it works+## Talk to the AI -```-  any container                          service-digikey-  $ adom-digikey search "BME280" ──POST──▶  adom-digikey serve  (:8777)-  $ adom-digikey app                        DIGIKEY_CLIENT_ID + OAuth-    (Hydrogen webview tab)                  token-refresh + cache-                                                 │-                                                 ▼-                                          api.digikey.com (v4)-```+- "price a TPS62840 buck on DigiKey"+- "is the BME280 in stock at DigiKey"+- "find a 1A buck regulator in SOT-23 on DigiKey"+- "datasheet for an SHT40 on DigiKey" -The backend manages the DigiKey OAuth handshake and token refresh for you; the CLI auto-detects it-(or a local `:8777`). DigiKey is the go-to alternate when Mouser is out of stock or long-lead —-see how [`adom-parts-search`](/adom/adom-parts-search) flips the recommendation automatically.+## Skills -## See also+| Skill | Purpose |+|---|---|+| `adom-digikey` | When/how Claude drives the search — verbs, MPN vs keyword, reading the cards |+| `adom-digikey-build` | Release workflow (build, publish to the wiki) | -- [`adom-parts-search`](/adom/adom-parts-search) — searches Mouser, DigiKey and JLCPCB at once and picks the best buy.+## CLI reference -## Open source — make it yours, then give it back+| Command | What it does |+|---|---|+| `adom-digikey search "<q>"` | Search DigiKey → JSON |+| `adom-digikey part "<dk-pn>"` | Fetch one part → JSON |+| `adom-digikey app` | Open the searchable Hydrogen tab |+| `adom-digikey health` | Check the backend + OAuth token |+| `adom-digikey serve` | Run the shared backend proxy (port 8777) | -This app is **open source under the MIT license**. Fork it, rewrite it, rename it, bend it to your-own workflow — and when you've made it better, **send your changes back to the Adom Wiki so the-whole community benefits**. Every wiki page is a git repo with a package registry on top, so-contributing back is first-class — improvements that land here ship to every Adom user who installs-the app.+## Open source — make it yours, then give it back -```bash-adompkg install adom-digikey      # install it-#   …edit the source to taste…-adompkg publish             # publish your own fork, or-#   open a pull request against this page so the change lands for everyone-```+This app is **open source under the MIT license**. Fork it, improve it, then send it back: `adompkg+publish` your own version, or open a pull request against this page so the change lands for everyone. -> **One caveat — the search backend is an Adom service.** The actual lookups run against-> Adom's hosted DigiKey backend (`service-digikey`), which uses **Adom's vendor API credentials and counts against Adom's quota**. That-> hosted backend is an Adom service and is **subject to change** — rate limits, endpoints, and-> availability can move at any time. Everything client-side (the CLI, the webview, the rendering-> and recommendation logic) is yours to fork and republish; the cloud API quota is not.+> **One caveat — the search backend is an Adom service.** Lookups run against Adom's hosted DigiKey+> backend (`service-digikey`), which uses Adom's API credentials and counts against Adom's quota —+> an Adom service, **subject to change**. Everything client-side is yours to fork and republish.  ## License 
screenshots/hero.png
⋯ 1 unchanged line ⋯