Skip to content

Theme creator

Build an app theme while you watch it take shape, with an AI assistant that also draws its logo in SVG (the theme's icon). On the left is Kino (Home, the side menu, search and a dialog) with sample data and, below it, the logo as the app would show it; on the right, the theme's values; below, the code as it gets written. It starts from Kino's own theme: every value you move changes the view at once, and whatever Kino would drop (for contrast or range) is dropped here too and explained underneath, in the kit's own words.

Press the three-line menu to open the side menu and Home to go back to Home. With TV you see the side rail and the focus. You can also type or paste the JSON below: the controls follow what you write.

The logo and the AI assistant

A theme's logo (logo) is vectors only: a wordmark (the long logo of the menu and the header), a mark (the square in the TV rail) and a decor drawn over the "o" of Kino's own logo. The creator really draws them: in the phone's header and menu, in the TV rail, and in the Your logo in the app strip under the preview.

Ask the assistant in your own words ("a neon lightning icon", "a wave mark for my blue theme") and it writes the paths. While it works you see which step it is on: preparing the request, asking the AI, reading the answer, checking the values and updating the preview. Every value it proposes is checked against the contract's rules before it is applied: 1 to 8 paths of up to 2,000 characters each, only SVG path commands (M L H V C S Q T A Z), a canvas of at most 1,000 × 1,000 and at most 8 times wider than tall, and a fill of accent, onAccent, textPrimary, textSecondary or a #RRGGBB. Anything that does not fit is not applied and the reason is shown underneath.

The logo can also come in the JSON you paste, and it is included in the code and in the kino-plugin.json you download. In the Logo and icon section on the right you can see each piece's size and path count and remove them one by one.

Publishing the plugin from the creator

The Publish to GitHub panel uploads kino-plugin.json, plugin.js (with export {};) and a .gitignore to a repository of yours that already exists, without leaving this page. It also writes the repository's description and, if you leave the box ticked, adds the kino-plugin topic: the only way Kino discovers a plugin, and it must be a public, non-fork repository (Publishing your plugin). The description you type in the panel is also the text of your plugin's card in Kino (up to 300 characters), and your GitHub username becomes the author. When it finishes it tells you the owner/repo to type in Kino.

It does not create repositories or ask you to sign in with your account. You set it up once:

  1. On GitHub, create an empty public repository, with no README.
  2. At github.com/settings/personal-access-tokens create a fine-grained token. Under Repository access pick Only select repositories and tick just that repository. Under permissions set Contents: Read and write and Administration: Read and write (the latter is for the topic and the description).
  3. Type the repository in the panel and paste the token.

The token only reaches that repository: if it leaked, nothing else in your account is exposed. It is kept in that tab, wiped when you close it (or with Forget the token), and the browser sends it only to api.github.com: it does not pass through any server of this site or of a third party. If you would rather not use a token, download kino-plugin.json and upload it yourself.

Sign in with GitHub (optional) saves you creating the token: the page shows a code, you type it at https://github.com/login/device and approve. It is more convenient but less strict: the scope is public_repo, which reaches all your public repositories, and the token passes through a Kino proxy (a Cloudflare Worker, code in github-oauth-worker/) that stores and logs nothing, does not forward the refresh token and only answers this page. If you would rather nothing passes through it, use the one-repository token.

Using the result

  1. Download kino-plugin.json (or copy the code) and put it in a new GitHub repository, with a plugin.js that only says export {};, or let the Publish to GitHub panel do it for you. A plugin that only ships themes needs no capabilities and no hosts: A plugin that only brings themes.
  2. Give the repository the kino-plugin topic and publish it.
  3. Validate with node sdk/validate.mjs . (the kit): it prints the same warnings you see here.

The preview is an approximation of Kino made with HTML and CSS: it is good for choosing colors, shapes and borders, but the app has the last word. The Player values are kept in the theme even though the preview only shows a small bar. The price (price), the experience (experience) and the person's adjustments (adjustable) are written by hand in the code: see App themes.