create-bridgething 0.15.1 → 0.15.2

package/dist/index.mjs

@@ -354,6 +354,7 @@ function scaffoldApp(root, spec) {
 		source: spec.repoUrl,
 		icon: null,
 		screenshots: [],
+		categories: [],
 		min_libbridgething_version: SDK_VERSIONS.libbridgething
 	});
 	const manifest = readJson(join(dir, "public", "manifest.json"));
@@ -522,8 +523,8 @@ async function addApp(root, args) {
 	console.log(`
 Next:
 
-  fill in the description in apps/${slug}/public/manifest.json, and check the author
-  and repo url in apps/${slug}/catalog.json
+  fill in the description in apps/${slug}/public/manifest.json, then check the author
+  and repo url and pick one or two categories in apps/${slug}/catalog.json
 
   bun run dev ${slug}      develop against a connected Car Thing
   bun run check            ensure your app and source are valid

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-bridgething",
-  "version": "0.15.1",
+  "version": "0.15.2",
   "type": "module",
   "description": "Scaffold a bridgething app source: webapps for the Spotify Car Thing, published as a catalog.v1 on GitHub Pages.",
   "license": "MIT",

package/template/_claude/skills/bridgething/reference/ship.md

@@ -33,6 +33,12 @@ Raise `version` in `public/manifest.json` before you share an update. Keep `id`.
 
 ## Publish to the store
 
+Before the first publish, set `categories` in `apps/<slug>/catalog.json` to one
+or two of `music`, `clocks-weather`, `dashboards`, `home-control`,
+`productivity`, `ambient`, `games`, `travel`, `tools`, most fitting first. The
+store files apps by it, and `bun run check` warns when it is missing. Take at
+least one screenshot with `bun run shot <slug>`: only apps with one get featured.
+
 From the repo root, `bun run bump <slug> <major | minor | patch>` moves the
 version, then a push to main runs the publish workflow. It builds every new
 version into `catalog.v1.json` on the `gh-pages` branch. GitHub Pages has to

package/template-source/CLAUDE.md

@@ -69,7 +69,7 @@ Running and driving the app: `.claude/skills/bridgething/reference/develop.md`.
 - `settings` names the page built from `settings/`, capped at 1 MiB. It talks to the companion app through `@bridgething/client/settings` and embeds `<ConfigForm/>` for the declared fields. A button on it that acts on those fields awaits the form's `flush()` first. The companion keeps the page loaded between visits, so it rereads device state in `settings.onRefresh`. It is also where a user picks a file for the app (`settings.pick` + `settings.blob.put`), which the webapp then shows through `client.blob`.
 - `extension` declares the desktop-side Deno process and the host permissions it gets.
 
-**`apps/<slug>/catalog.json`** is the store listing and nothing else: `author`, `homepage`, `source`, an `icon` override, `screenshots`, and `min_libbridgething_version` (the oldest daemon the app works against). Never restate anything the manifest already says. An app that ships an extension must carry its `github.com` repo url in `source`, because the store shows that link next to the host permissions it is asking for.
+**`apps/<slug>/catalog.json`** is the store listing and nothing else: `author`, `homepage`, `source`, an `icon` override, `screenshots`, `categories`, and `min_libbridgething_version` (the oldest daemon the app works against). `categories` is one or two of `music`, `clocks-weather`, `dashboards`, `home-control`, `productivity`, `ambient`, `games`, `travel`, `tools`, most fitting first; always set it, because an app without one is left off every category shelf in the store. A launcher or overlay may leave it empty, since those get their own shelves. Never restate anything the manifest already says. An app that ships an extension must carry its `github.com` repo url in `source`, because the store shows that link next to the host permissions it is asking for.
 
 **`apps/<slug>/CHANGELOG.md`** carries a `## <version>` section per release, which becomes that version's changelog in the catalog.
 
@@ -84,7 +84,7 @@ bun run check
 
 `new` scaffolds into `apps/<slug>`. Never add an app by hand: the scaffold generates the uuid, writes the store listing, wires the dev server to a connected device, and lands the tsconfig and scripts CI expects.
 
-`shot` captures the kiosk over CDP into `apps/<slug>/screenshots/`. The image fronts chromium's debugging port on `bridgething.local:9222`, so it needs nothing but the device plugged in. Up to six, filename order, first is the store card.
+`shot` captures the kiosk over CDP into `apps/<slug>/screenshots/`. The image fronts chromium's debugging port on `bridgething.local:9222`, so it needs nothing but the device plugged in. Up to six, filename order, first is the store card. Only an app with a screenshot can be featured at the top of the store, so take at least one.
 
 `bump` writes `public/manifest.json` and `package.json` together and opens the changelog section. Editing one without the other fails the build.
 

package/template-versions.json

@@ -1,6 +1,6 @@
 {
   "@bridgething/client": "^0.15.1",
   "@bridgething/extension": "^0.15.1",
-  "@bridgething/source": "^0.15.1",
+  "@bridgething/source": "^0.15.2",
   "libbridgething": "0.15.1"
 }