MCPInstall

eda-schematics

by l3wi

Schematic capture and wiring. Create schematic sheets, place symbols, add wires and net labels, organize hierarchical designs.

Installs
491
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/l3wi/claude-eda --skill eda-schematics
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads eda-schematics automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

EDA Schematics Skill

Create and wire schematics for electronics projects.

Auto-Activation Triggers

This skill activates when:

  • User asks to "create schematic", "add component", "wire"
  • User is working with .kicad_sch files
  • User asks about net names, connections, or ERC
  • Project has component selections but no schematic
  • User mentions schematic organization or sheets

Context Requirements

Requires:

  • docs/component-selections.md - Selected components with LCSC numbers
  • docs/design-constraints.json - Project constraints
  • datasheets/ - Component datasheets for reference circuits

Produces:

  • hardware/*.kicad_sch - KiCad schematic file(s)
  • docs/schematic-status.md - Status and progress tracking

Workflow

1. Load Context

@docs/design-constraints.json
@docs/component-selections.md
@datasheets/ (relevant datasheets)

From design-constraints.json, extract:

  • power.topology - LDO vs buck affects schematic complexity
  • power.rails[] - All voltage rails to implement
  • board.layers - 2-layer = simpler designs, 4+ = can be more complex
  • thermal.budget - Identify hot components for grouping
  • dfmTargets.assembly - Package sizes must match

1.5. Validate Readiness

Before starting schematic:

  • All required components selected in component-selections.md?
  • MCU selected with known pinout?
  • Voltage regulators selected?
  • Critical passives (decoupling values) defined?
  • Datasheets downloaded for reference circuits?

If not, suggest running /eda-source [role] first.

2. Plan Sheet Organization

See reference/SCHEMATIC-HIERARCHY-DECISION.md for detailed guidance.

Based on complexity, organize into sheets:

Simple design (1-2 sheets):

  • Sheet 1: Everything

Medium design (3-4 sheets):

  • Sheet 1: Power (input, regulators)
  • Sheet 2: MCU and core logic
  • Sheet 3: Interfaces and I/O

Complex design (5+ sheets):

  • Sheet 1: Power input and protection
  • Sheet 2: Voltage regulation
  • Sheet 3: MCU and clock
  • Sheet 4: Communication interfaces
  • Sheet 5: Connectors and I/O
  • Additional sheets as needed

3. Create Schematic Structure

  • Create main schematic file
  • Add hierarchical sheets if multi-sheet
  • Set up page sizes and title blocks

4. Place Components (Per Sheet)

For each component:

  1. Place symbol from library
  2. Set reference designator
  3. Set value
  4. Add LCSC part number to properties
  5. Position logically

Tool syntax:

mcp__kicad-sch__add_component schematic_path="/path/to/file.kicad_sch" lib_id="EDA-MCP:SymbolName" reference="U1" value="10k" position=[100, 100]
  • Use symbol_ref from library_fetch response (e.g., EDA-MCP:ESP32-C3)
  • For standard parts, use KiCad libraries (e.g., Device:R, Device:C)
  • Position uses grid-aligned coordinates (1.27mm grid)

Placement guidelines:

  • Power flows top-to-bottom or left-to-right
  • Signal flows left-to-right
  • Group related components
  • Leave space for wiring

5. Add Power Symbols

  • Place VCC symbols for each rail
  • Place GND symbols
  • Use consistent power symbol naming

6. Wire Connections

Follow the reference circuits from datasheets:

  1. Wire power connections first
  2. Add decoupling capacitors to power pins
  3. Wire critical signals (crystal, reset)
  4. Wire communication buses
  5. Wire remaining signals

Use net labels for:

  • Inter-sheet connections
  • Buses
  • Avoiding wire crossing
  • Named signals (for clarity)

7. Verify and Document

  • Check all pins connected or marked NC
  • Run ERC (electrical rules check)
  • Document status

See reference/ERC-VIOLATIONS-GUIDE.md for fixing common ERC errors.

8. Pre-Layout Review

Before proceeding to layout, complete reference/SCHEMATIC-REVIEW-CHECKLIST.md:

  • Power section verification
  • Decoupling validation
  • Interface protection check
  • Test points present
  • Net naming consistency
  • Documentation complete

Net Naming Convention

See reference/NET-NAMING.md for complete conventions.

Quick reference:

Power:    VCC_3V3, VCC_5V, VBAT, GND, GNDA
Reset:    MCU_RESET, nRESET
SPI:      SPI1_MOSI, SPI1_MISO, SPI1_SCK, SPI1_CS
I2C:      I2C1_SDA, I2C1_SCL
UART:     UART1_TX, UART1_RX
GPIO:     LED_STATUS, BTN_USER, or GPIO_PA0

Output Format

schematic-status.md

# Schematic Status

Project: [name]
Updated: [date]

## Summary
- Total sheets: X
- Components placed: Y
- Wiring: Z% complete
- ERC: X errors, Y warnings

## Sheets

### Sheet 1: Power
- Status: Complete
- Components: U1 (regulator), C1-C4 (caps)
- Notes: ...

### Sheet 2: MCU
- Status: In Progress
- Components: U2 (MCU), Y1 (crystal), C5-C10
- Notes: Needs clock wiring

## ERC Issues
- [ ] Unconnected pin on U2.PA3 (intentional NC)
- [x] Missing power flag (fixed)

## Next Steps
- Complete MCU clock circuit
- Wire SPI bus to flash
- Run final ERC

Guidelines

  • Always check datasheets for reference circuits
  • Place decoupling caps within 3mm of IC power pins (in layout)
  • Use net labels for any signal that crosses sheets
  • Keep schematic readable - avoid wire spaghetti
  • Add notes for non-obvious connections
  • Mark intentionally unconnected pins with NC flag

Architecture Validation Warnings

Check these before proceeding to layout:

ConditionWarning
Buck converter selected but no inductor in schematicMissing critical component
USB interface but no ESD protectionAdd ESD diodes before layout
External connector but no protectionAdd TVS/ESD on exposed signals
MCU with <100nF per VDD pinVerify decoupling against datasheet
Crystal but no load cap calculationRecalculate CL values
I2C bus but no pull-upsAdd pull-ups (4.7K-10K)
SPI CS lines floatingAdd pull-ups to prevent glitches
Reset pin without RC debounceAdd debounce circuit

Reference Documents

DocumentPurpose
reference/NET-NAMING.mdNet naming conventions
reference/SYMBOL-ORGANIZATION.mdSchematic layout patterns
reference/REFERENCE-CIRCUITS.mdCommon circuit patterns
reference/SCHEMATIC-HIERARCHY-DECISION.mdSheet organization guidance
reference/SCHEMATIC-REVIEW-CHECKLIST.mdPre-layout validation
reference/ERC-VIOLATIONS-GUIDE.mdFixing ERC errors

Next Steps

After schematic is complete:

  1. Generate netlist
  2. Run /eda-layout to begin PCB layout
  3. Update design-constraints.json stage to "pcb"

FAQ

What does the eda-schematics skill do?

Schematic capture and wiring. Create schematic sheets, place symbols, add wires and net labels, organize hierarchical designs.

How do I install eda-schematics?

Run npx skills add https://github.com/l3wi/claude-eda --skill eda-schematics in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/eda-schematics/ (personal) or .claude/skills/eda-schematics/ (project).

Which AI agents can use eda-schematics?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is eda-schematics safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains eda-schematics?

It is published by l3wi in l3wi/claude-eda. It has 491 recorded installs.

More from l3wi/claude-eda

View all →

eda-pcb

l3wi/claude-eda

PCB layout and routing. Component placement, trace routing, copper pours, design rule configuration, and layout optimization for manufacturability.

Frontend & Design467 installs

eda-drc

l3wi/claude-eda

Design validation and review. Run DRC/ERC checks, verify against constraints, check component availability, and prepare comprehensive validation reports.

Frontend & Design160 installs

eda-architect

l3wi/claude-eda

Electronics project architecture and constraint definition. Guides users through defining project requirements, power systems, interfaces, and physical constraints.

eda-research

l3wi/claude-eda

Open the skill to read its SKILL.md instructions.

Popular other skills

View category →

hyperframes-cli

heygen-com/hyperframes

The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.

1.3M installs

triage

mattpocock/skills

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

1M installs

ask-matt

mattpocock/skills

Ask which skill or flow fits your situation. A router over the skills in this repo.

778.4K installs

to-questionnaire

mattpocock/skills

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

508.9K installs

wait-what

mattpocock/skills

Stop. That last message did not land: re-pitch it.

459.7K installs

loop-me

mattpocock/skills

Grill me about specs for the workflows I want to build, within this workspace.

447.9K installs