Menu
SkillsMP has collected 16 skills from danielrosehill/Claude-Hardware-Spec-Assembly-Plugin. Open a skill to review its source and details.
Showing 16 of 16 collected skills.
Build a structured hardware specification and BOM for a project. Walks the user through goals, constraints, and functional requirements, then produces a markdown spec plus a structured BOM (parts, quantities, rationale) saved into the project directory.
Estimate the total cost of a project's BOM. Reads bom.json from a project, applies typical price ranges per vendor (informed by the user's preferred suppliers and location), and produces low/mid/high cost envelopes plus shipping considerations.
Produce a PCB design starting point from a project's BOM and wiring spec — schematic netlist, board stack-up and layout guidance, and ESP32-specific rules (antenna keep-out, strapping pins, decoupling). Output is KiCad/EasyEDA-ready design input, not finished…
Produce a textual wiring specification — pin map, connection table, and power distribution — suitable for handoff to a diagram tool (Fritzing, KiCad, Wokwi, draw.io) or for direct use during breadboarding. Not a graphical diagram itself.
Live web research for a project's components. Starting from a defined objective (integrations, radios, sensors) or an existing BOM, searches the web and the user's preferred marketplaces (AliExpress, Adafruit, Mouser, etc.) for real candidate parts with…
Recommend specific vendors for each BOM line, biased by the user's location and preferred suppliers. Produces a sourcing plan with vendor, expected lead time, and trade-offs (price vs. authenticity vs. speed).
Start from a free-form project description and work backwards to a candidate BOM. Lighter-weight than create-hardware-spec — used when the user wants a quick parts list to evaluate feasibility before committing to a full spec.
Query a user-defined MCP-connected inventory system to check live stock for a project's BOM. Use this when the user has a real inventory backend (warehouse management system, parts database, home-lab inventory) wired up via MCP, rather than a static on-hand…
Diff a project's BOM against the user's local on-hand inventory (the free-form list captured during onboarding). Reports which parts are already available, which need to be ordered, and which have plausible substitutes on hand.
Sanity-check the parts in a BOM against each other — voltage levels, logic-level compatibility, current draw vs. regulator capacity, I2C address conflicts, shared bus contention, and pin count adequacy on the chosen MCU. Flags issues before the user orders.
Generate step-by-step assembly instructions for a project — the order in which to wire/solder/mount parts, test gates between steps, and common gotchas. Reads the BOM, wiring spec, and datasheet quirks; writes a build guide the user can follow on the bench.
Fetch and summarise the datasheet for a part (or all parts in a project's BOM). Pulls the official PDF when locatable, extracts pinout, electrical characteristics, and typical application notes, and writes a per-part reference into the project directory.
Export a project's BOM (and optionally sourcing plan) to CSV and a clean markdown table. Useful for sharing with collaborators, pasting into a spreadsheet, or feeding into ordering workflows.
Generate visual mockups of the finished hardware project using fal.ai's nano-banana (Gemini 2.5 image) model. Useful for early-stage visualisation, communicating intent to collaborators, or scoping enclosure design before any parts arrive.
First-run setup for hardware-spec-assembly. Captures the user's location, preferred parts vendors, the kinds of hardware projects they typically work on (e.g. ESP32-based sensors, robotics), and the gear/components they already have on hand. Writes a profile…
Suggest 3D-printable parts that would complement the project — enclosures, mounts, brackets, knobs, jigs. Where possible, points to existing models on Printables / Thingiverse / MakerWorld; otherwise specifies dimensions and constraints for a custom design.