· Ryostore / Develop

Build for the Ryoku desktop.

Ryostore carries Ryoku's rices, plugins, colour schemes, and bundles. Make one, test it live, submit it.

· What you can make

Eleven catalogues, one store.

  • RicesA whole-desktop look.
  • PluginsDesktop widgets and frame popouts.
  • Colour schemesA palette every app follows.
  • LockscreensThe face of a locked machine.
  • Bar stylesThe shape of the top bar.
  • Fastfetch presetsA terminal system readout.
  • Launcher imagesArt for the app launcher.
  • DecorsPoster and ornament art.
  • Live wallpapersMoving backgrounds.
  • BundlesTool sets installed together.
  • Nautilus packsRight-click file actions.

· Develop

Test it live before you submit.

Ryoku runs your in-progress work from a folder on disk.

  1. 01

    Point Ryoku at your copy

    For a single plugin.
    bash
    systemctl --user set-environment RYOSTORE_PLUGINS_DIR="$HOME/Work/ryostore/plugins"
    systemctl --user restart ryoku-shell

    Plugins load from your folder, not the installed set.

  2. 02

    Or point the whole store at your checkout

    For rices, colour schemes, bundles — anything.
    bash
    mkdir -p ~/.config/ryoku
    echo "file://$HOME/Work/ryostore" > ~/.config/ryoku/ryostore-base

    Your item shows in the Store, installing off your disk. Edit registry.json and reopen.

  3. 03

    Enable it and watch

    Toggle, place, observe.
    bash
    journalctl --user -u ryoku-shell -f

    Toggle it on, place it, watch the log. Edits hot-reload.

  4. 04

    Validate

    From the repo root.
    bash
    tests/validate-catalogue.sh

    It prints catalogue OK. CI runs the same check.

· Submit

Two ways in.

Pull request

Preferred

Fork the repo, add your item and its registry.json entry, run the check, open a PR.

Submission form

Tell us the kind, a short description, where it lives, and a preview. A maintainer opens the PR.

· Rashin for contributors

Let your agent read the machine.

Run a coding agent? Turn on Rashin. It keeps a vault your agent reads instead of guessing, and prowl-agent indexes the repo so it traces symbols and callers in one call.

Ship only what you may: your work, CC0, or licensed to redistribute. Review lists items, it does not audit.