hardware-electronics-engineering

v0.1.2

Hardware / electronics engineering team — agents (hardware-systems-architect, pcb-design-engineer) for the BOARD embedded firmware runs on: architecture & build-vs-buy (module vs custom PCB), MCU/component selection + supply-aware BOM, power architecture (LDO-vs-switcher, budgets), schematic capture, PCB layout (stack-up, impedance, decoupling, grounding), signal & power integrity, DFM/DFA/DFT, and bring-up. skills (scope-a-hardware-design, select-components-and-bom, review-schematic-and-layout), a knowledge bank (a Mermaid module-vs-custom-PCB tree + a dated 2026 EDA/fab/compliance reference), best-practices. ENGINEERING decision-support, not a certification/safety-sign-off authority; component specs, fab/DFM rules, and regulatory thresholds are volatile + vendor/jurisdiction-specific, retrieval-dated + verify-at-use; datasheets read at the operating point. Distinct from embedded-iot-engineering (firmware) and robotics-autonomous-systems-engineering. Requires ravenclaude-core@>=0.7.0.

Claude Code3 Skills

By Matt CorbettLicense: MIT7 GitHub starsUpdated last week

Directory evidence

Runtimes: Claude Code
Parsed components: 3 skill or MCP entries
Source updated: Sep 15, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install hardware-electronics-engineering for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install hardware-electronics-engineering@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/mcorbett51090/RavenClaude

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/hardware-electronics-engineering/.

Plugin files

plugins/hardware-electronics-engineering/

├── .claude-plugin/plugin.json
├── skills/review-schematic-and-layout/SKILL.md
├── skills/scope-a-hardware-design/SKILL.md
└── skills/select-components-and-bom/SKILL.md

Included Skills3

review-schematic-and-layoutskills/review-schematic-and-layout/SKILL.md

Review a schematic and PCB layout before fab: correctness (ERC/DRC, footprints/pinouts/polarity, power), integrity (decoupling at the pin, grounding/return paths, stack-up, controlled impedance), and DFM/DFA/DFT against the target fab's rules — returning a prioritized findings list with fixes. Reach for this before sending to fab, or on an inherited design. Driven by pcb-design-engineer.

scope-a-hardware-designskills/scope-a-hardware-design/SKILL.md

Turn a product idea into a hardware architecture: decide module/dev-board vs custom PCB (via the decision tree), name requirements before parts, sketch the power tree, the interface plan, and an EMC/pre-compliance posture — against a cost/power/size/volume/schedule budget. Reach for this at the START of any board project. Driven by hardware-systems-architect.

select-components-and-bomskills/select-components-and-bom/SKILL.md

Select the MCU/SoC and key components and build a supply-aware BOM: match parts to requirements, read datasheet parameters at the operating point (worst-case + margin), and weigh availability / second-source / lifecycle / cost at the target volume. Reach for this after the architecture is scoped, before schematic capture. Driven by hardware-systems-architect.

Plugin manifests1

plugins/hardware-electronics-engineering/.claude-plugin/plugin.json

{
  "name": "hardware-electronics-engineering",
  "version": "0.1.2",
  "description": "Hardware / electronics engineering team — agents (hardware-systems-architect, pcb-design-engineer) for the BOARD embedded firmware runs on: architecture & build-vs-buy (module vs custom PCB), MCU/component selection + supply-aware BOM, power architecture (LDO-vs-switcher, budgets), schematic capture, PCB layout (stack-up, impedance, decoupling, grounding), signal & power integrity, DFM/DFA/DFT, and bring-up. skills (scope-a-hardware-design, select-components-and-bom, review-schematic-and-layout), a knowledge bank (a Mermaid module-vs-custom-PCB tree + a dated 2026 EDA/fab/compliance reference), best-practices. ENGINEERING decision-support, not a certification/safety-sign-off authority; component specs, fab/DFM rules, and regulatory thresholds are volatile + vendor/jurisdiction-specific, retrieval-dated + verify-at-use; datasheets read at the operating point. Distinct from embedded-iot-engineering (firmware) and robotics-autonomous-systems-engineering. Requires ravenclaude-core@>=0.7.0.",
  "author": {
    "name": "Matt Corbett"
  },
  "homepage": "https://github.com/mcorbett51090/RavenClaude",
  "license": "MIT",
  "keywords": [
    "hardware-engineering",
    "electronics",
    "pcb-design",
    "schematic-capture",
    "bom",
    "component-selection",
    "power-integrity",
    "signal-integrity",
    "dfm",
    "emc",
    "fcc",
    "board-bring-up",
    "kicad",
    "altium",
    "mcu-selection",
    "power-architecture"
  ],
  "requires": {
    "plugins": [
      "ravenclaude-core@>=0.7.0"
    ]
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[hardware-electronics-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/hardware-electronics-engineering)