← ClaudeAtlas

espos-signalk-pluginlisted

Building a Signal K plugin or webapp for signalk-espOS (manager, HMI designer, display stream, signalk-zigbee, or your own) so a boat owner installs it and it works: enabling it by default, defaults that need no configuration, finding devices instead of asking for addresses, and webapps and plugin config forms that work on a touchscreen at the helm.
signalk-espOS/skills · ★ 0 · Web & Frontend · score 72
Install: claude install-skill signalk-espOS/skills
# Signal K plugins a boat owner never has to configure Verified against signalk-server 2.36.0 (Admin UI on `@rjsf/core` 5) and signalk-espos-manager 0.8.1, November 2026. Sources: signalk-server `src/interfaces/plugins.ts`, `docs/develop/plugins/configuration.md`, `docs/develop/webapps.md`; manager `package.json`, `src/config.ts`, `web/src/style.css`. The person installing a signalk-espOS plugin is a boat owner, often on a phone or the chart plotter's touchscreen. Every field they have to fill in is a step where they give up. Aim for: install from the App Store, restart, and it works. ## Enable it by default Add this to `package.json`, next to the `signalk` block: ```json "signalk-plugin-enabled-by-default": true ``` What the server does with it (`plugins.ts`, `isEnabledByPackageEnableDefault`): * It only applies while the plugin has **no saved `enabled`**, so a fresh install. A user who disables the plugin stays disabled. * The server writes `{ enabled: true, configuration: {} }` to the plugin's options file and starts the plugin with **an empty configuration**. The schema's `default`s are not applied (see below), so a plugin that reads `options.port` gets `undefined`. * It takes effect when the server starts after the install. The App Store asks for that restart anyway. * Adding the flag to a plugin already in use: an options file that has a `configuration` but no `enabled` key gets that configuration replaced by `{}`. The Admin UI always saves `enabled`,