Pull request
PreferredFork the repo, add your item and its registry.json entry, run the check, open a PR.
力 · Ryostore / Develop
Ryostore carries Ryoku's rices, plugins, colour schemes, and bundles. Make one, test it live, submit it.
力 · What you can make
力 · Develop
Ryoku runs your in-progress work from a folder on disk.
systemctl --user set-environment RYOSTORE_PLUGINS_DIR="$HOME/Work/ryostore/plugins"
systemctl --user restart ryoku-shellPlugins load from your folder, not the installed set.
mkdir -p ~/.config/ryoku
echo "file://$HOME/Work/ryostore" > ~/.config/ryoku/ryostore-baseYour item shows in the Store, installing off your disk. Edit registry.json and reopen.
journalctl --user -u ryoku-shell -fToggle it on, place it, watch the log. Edits hot-reload.
tests/validate-catalogue.shIt prints catalogue OK. CI runs the same check.
力 · Submit
Fork the repo, add your item and its registry.json entry, run the check, open a PR.
Tell us the kind, a short description, where it lives, and a preview. A maintainer opens the PR.
力 · Rashin for contributors
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.