Three in the box, ten more a command away.

1.0 · Bundled

Ships with kobe.

kobe keeps its bundled set deliberately small — open Settings with ctrl+, and pick one, nothing to install. Each preview paints the sidebar, the selected task, and a diff with that theme's own slots, so what you see is the contrast you'll actually get. Every theme also defines a light mode; the previews show dark.

2.0 · Downloadable

Ten more, one command away.

These live here as plain JSON instead of inside the binary — which is all a theme ever is. Copy the command, run it, restart kobe. Several of them shipped bundled in earlier versions; nothing changed about them except where they're stored.

3.0 · Write one

A theme is one JSON file.

Drop any *.json into ~/.kobe/themes/ and it appears in the picker at next boot. Name it after a bundled theme and yours wins. You don't have to fill every slot — missing ones fall through (borderActive → border → text), so a dozen lines is already a usable theme.

// ~/.kobe/themes/darkside.json
{
  "$schema": "https://raw.githubusercontent.com/sma1lboy/kobe/main/packages/kobe/src/tui/context/theme/theme.schema.json",
  "defs": { "brand": "#cc785c" },
  "theme": {
    "background": "#141413",
    "text": "#eae7df",
    "primary": "brand",
    "accent": { "dark": "#cc785c", "light": "#c96442" }
  }
}

defs is an optional named palette a slot can reference by name. A slot value is a hex string, a defs key, or a { dark, light } pair — and when you use the pair form, both sides are required. The $schema line is what gives you autocomplete in your editor.

4.0 · Publish

Share a URL. That's the whole registry.

There is no submission queue and no manifest to write. Installation reads a raw file over HTTPS, so anything you can link to is installable — a repo, a gist, your own host.