luvus-module

Featured

Write a luvus module (an extension for luvus, mission control for your AI coding agents). Use when the user is building or debugging a luvus module: authoring luvus-module.toml, adding a sidebar dock, Luvus Bar widget, right-click action, event hook, module pane, module settings, or calling luvus back over its UHP.

Code & Development 810 stars 52 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 90/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Writing a luvus module A **luvus module** is a plugin for luvus, mission control for your AI coding agents. There is **no SDK and no scripting engine**: a module is a directory with a `luvus-module.toml` manifest that declares **argv commands** (any executable: `sh`, `python`, `node`, a compiled binary). luvus runs those commands as subprocesses with `LUVUS_*` context in the environment, and the command calls luvus back through the same UHP the `luvus` CLI uses. So a module in bash/python/node can do what a built-in feature does. Reference material in this repo (read for depth): `MODULE-GUIDE.md`, `docs/13-modules.md`, and the worked modules in `examples/modules/` (`branch-dock` = a sidebar dock, `agent-ping` = an event hook, `scratch-pane` = a pane). ## The manifest: `luvus-module.toml` Top-level keys (all required unless noted): ```toml id = "yourname.my-module" # unique, reverse-dns style name = "My Module" version = "0.1.0" min_luvus_version = "0.8.3" # oldest luvus this needs description = "One line." # optional platforms = ["macos", "linux"] # optional; omit = all. Also per-item. ``` Then any of these tables, each declaring an argv `command` (a list, run as-is, cwd = the module dir): - **`[[docks]]`** `id`, `title`, `placement` (`sidebar.left` | `sidebar.right`) — reserve a sidebar dock. luvus renders it; you fill it with `ui.dock.push` (see below). - **`[[bars]]`** `id`, `title`, `region` (`top-right` | `bottom-right`), optional `priority` — reserv...

Details

Author
RizRiyz
Repository
RizRiyz/luvus
Created
2 months ago
Last Updated
today
Language
Rust
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Featured

bohay-module

Write a bohay module (an extension for bohay, mission control for your AI coding agents). Use when the user is building or debugging a bohay module: authoring bohay-module.toml, adding a sidebar dock, a right-click action, an event hook, a module pane, or module settings, or calling bohay back over its socket API.

810 Updated today
RizRiyz
Code & Development Featured

luvus

Control Luvus through its local CLI and UHP. Use only for a line beginning with `=target message`, an explicit request naming Luvus, a request to delegate to a named live Luvus agent or pane, or an explicit Luvus operation involving sessions, workspaces, tabs, panes, agents, files, Git, DIFF, worktrees, tasks, leases, modules, themes, Luvus Bar, configuration, UI, integrations, or Luvus UHP. Do not use for ordinary coding, file edits, Git operations, tests, task planning, generic agent work, or parallelization unless the user explicitly connects the request to Luvus. Being inside Luvus does not trigger this skill by itself. Inside Luvus use the inherited session; outside use the installed production Luvus command and configured session.

810 Updated today
RizRiyz
Web & Frontend Solid

nuxt-modules

Use when creating Nuxt modules: (1) Published npm modules (@nuxtjs/, nuxt-), (2) Local project modules (modules/ directory), (3) Runtime extensions (components, composables, plugins), (4) Server extensions (API routes, middleware), (5) Releasing/publishing modules to npm, (6) Setting up CI/CD workflows for modules. Provides defineNuxtModule patterns, Kit utilities, hooks, E2E testing, and release automation.

45 Updated today
YuDefine