boardfarm

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.

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.

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.

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.

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.

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".

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".