extend-jbom

Implement new CLI subcommands and domain services for the jBOM KiCad BOM generator.

3|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/plocher/jBOM --skill extend-jbom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extend-jbom
Source: https://github.com/plocher/jBOM/tree/main/.agents/skills/extend-jbom
Command: npx skills add https://github.com/plocher/jBOM --skill extend-jbom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, maintainable framework for extending the jBOM ecosystem, preventing architectural drift when adding new commands, services, or file formats.

Core Features & Use Cases

  • Modular Extension: Follows established patterns for adding CLI subcommands, domain services, and inventory file formats.
  • Type-Safe Integration: Provides clear guidelines for component classification, package type registration, and fabricator profile definitions.
  • Use Case: When a team needs to support a new proprietary inventory spreadsheet format or a custom fabricator output, this skill provides the exact registration steps and testing requirements to ensure the new feature integrates seamlessly with the existing codebase.

Quick Start

Use the extend-jbom skill to generate the boilerplate code and registration steps required to add a new custom CLI command to the jBOM project.

Frequently Asked Questions about extend-jbom

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new CLI subcommand to the jBOM KiCad BOM generator?

To add a new CLI subcommand to the jBOM KiCad BOM generator, use this skill to generate the required boilerplate code and registration steps. It provides procedural recipes ensuring the new command adheres to the project's command-query separation and dependency injection rules.

What is the best way to support a proprietary inventory spreadsheet format in jBOM?

Supporting a proprietary inventory spreadsheet format in jBOM requires following established architectural patterns for new file formats. This skill provides the exact registration steps and testing requirements to ensure the custom format integrates seamlessly without causing architectural drift.

How do I implement custom component classification logic for a KiCad BOM?

Implementing custom component classification logic for a KiCad BOM involves following type-safe integration guidelines for component classification and package type registration. This skill provides the architectural patterns to scale these extensions safely within the existing codebase.

Does extending the jBOM project require following specific architectural rules?

Extending the jBOM project requires strict adherence to command-query separation and dependency injection rules. This skill provides a structured framework to prevent architectural drift when adding new domain services, commands, or fabricator profile definitions.

Can I define custom fabricator output profiles in the jBOM BOM generator?

You can define custom fabricator output profiles in the jBOM BOM generator using provided type-safe integration guidelines. It outlines the exact registration steps needed to create and test fabricator profiles while maintaining codebase integrity.