Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

boardfarm-dev

Estrellas31

Forks36

Actualizado23 de julio de 2026 a las 09:41

Cookie-cutter entry point for boardfarm plugin development. Use when a developer wants to build any new boardfarm component — template (ABC), device class, connection driver, or use-case function. Triggers on: "new boardfarm component", "help me write a boardfarm plugin", "I want to build a new boardfarm device", "boardfarm cookiecutter", "scaffold a boardfarm template/device/connection/use-case", or any request to create new boardfarm code. Dispatches to the right sub-skill; performs no code generation itself.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

lgirdk

lgirdk/boardfarm

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Otras ocupaciones informáticasOcupaciones informáticas y matemáticas·SOC 15-1299

SKILL.md

readonly

name: boardfarm-dev description: Cookie-cutter entry point for boardfarm plugin development. Use when a developer wants to build any new boardfarm component — template (ABC), device class, connection driver, or use-case function. Triggers on: "new boardfarm component", "help me write a boardfarm plugin", "I want to build a new boardfarm device", "boardfarm cookiecutter", "scaffold a boardfarm template/device/connection/use-case", or any request to create new boardfarm code. Dispatches to the right sub-skill; performs no code generation itself.

boardfarm-dev — Root Orchestrator

Your job is to present a numbered menu and dispatch to the right sub-skill. You do NOT generate any code, stubs, or scaffolding yourself.

Step 1 — Read the registry

Read the file at skills/registry.md inside this plugin directory (.claude/plugins/boardfarm-dev/skills/registry.md relative to the repo root). Parse the table to extract the "Skill name" and "Covers" columns.

Step 2 — Present the menu

Present the menu using the "Covers" column text verbatim, numbered from 1:

"What kind of boardfarm component do you want to build?

[1] Abstract base class (template) definition → /boardfarm-dev:new-template [2] Concrete device class + hookimpl wiring → /boardfarm-dev:new-device [3] Transport / connection driver → /boardfarm-dev:new-connection [4] Use-case function(s) typed against a template → /boardfarm-dev:new-use-case

Pick a number, or name the sub-skill directly (e.g. new-device)."

Step 3 — Dispatch

Developer picks a number or names a sub-skill: Announce "Using /boardfarm-dev:<name> to guide you through this." then invoke that sub-skill.

Developer describes something spanning multiple sub-skills (e.g. "I need a new template AND a device for it"): Say: "I handle one component at a time. Since your template doesn't exist yet, start with /boardfarm-dev:new-template to create the ABC, then come back and run /boardfarm-dev:new-device to implement it. Shall I start with the template?"

Developer names a sub-skill not in the registry: Say: "That sub-skill isn't in the registry. Here's what's currently available:" then print the full registry table and stop.

Constraints

You perform no code generation, file creation, or scaffolding.
You read the registry fresh every time (do not cache between sessions).
If the registry file is missing, say: "The registry at skills/registry.md could not be found. Ensure the boardfarm-dev plugin is correctly installed from the repo root with claude plugin install .claude/plugins/boardfarm-dev."

Más de este repositorio

mismo repositorio

boardfarm-dev-new-connection

lgirdk/boardfarm

Guide for creating a new boardfarm connection driver (transport class). Use when a developer needs to add a new transport that doesn't exist in boardfarm3/lib/connections/ — e.g. a new protocol, auth mechanism, or wrapper. Triggers on: "new connection", "add a connection driver", "new transport", "write a connection class", "new SSH variant", "add a serial connection". Follow the 3-phase contract: Discover → Interview → Generate.

2026-07-2331

boardfarm-dev-new-device

lgirdk/boardfarm

Guide for creating a new boardfarm concrete device class. Use when a developer needs to implement a vendor- or transport-specific device that satisfies an existing template. Triggers on: "new device", "add a device", "implement a template", "write a device class", "new CPE device", "new ACS implementation", "concrete implementation of". Follow the 3-phase contract: Discover → Interview → Generate.

2026-07-2331

boardfarm-dev-new-template

lgirdk/boardfarm

Guide for creating a new boardfarm Template (Abstract Base Class). Use when a developer needs to define a new device category API that does not yet exist in boardfarm3/templates/. Triggers on: "new template", "add a template", "write an ABC for", "create a boardfarm template", "define a device interface". Follow the 3-phase contract: Discover → Interview → Generate.

2026-07-2331

boardfarm-dev-new-use-case

lgirdk/boardfarm

Guide for creating new boardfarm use-case functions. Use when a developer needs to add a protocol- or feature-oriented function typed against template ABCs. Triggers on: "new use case", "add a use case", "write a use-case function", "protocol function", "feature function for boardfarm", "add to use_cases". Follow the 3-phase contract: Discover → Interview → Generate.

2026-07-2331

boardfarm-dev-scan-plugins

lgirdk/boardfarm

Discover installed boardfarm plugins and report which templates, devices, and use-cases they contribute beyond core boardfarm3. Use when a developer wants to see what's installed, or is automatically invoked by other boardfarm-dev sub-skills before their own discovery phase, to avoid duplicating components a plugin already provides. Triggers on: "what boardfarm plugins are installed", "scan plugins", "check my boardfarm environment", "what templates do I have", "list installed boardfarm devices".

2026-07-2331

boardfarm-dev-verify-device

lgirdk/boardfarm

Verify a boardfarm device class actually works, at one of three levels of rigor — lint plus unit tests, a live connectivity smoke check, or a full boardfarm boot. Use when a developer wants to check their work before committing, is mid-way through writing a device's _connect() method and wants fast signal, or needs to debug why a device's boot hook is failing. Triggers on: "verify my device", "test this device class", "check connectivity", "run boardfarm against my device", "does my device connect", "debug boot hook failure".

2026-07-2331