Skip to content
eda-schematics logo

EDA Schematics Skill

eda-schematics

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

SKILL.md

Full skill instructions

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"

More skills from majiayu000

xiaohongshu logo
majiayu000/claude-arsenal

xiaohongshu

xiaohongshu

286 148
View
agent-task-conductor logo
majiayu000/claude-skill-registry

agent-task-conductor

Conduct multi-agent task orchestration and workflow coordination.

663 1
View
conductor-setup logo
majiayu000/claude-skill-registry

conductor-setup

Initialize project with Conductor artifacts (product definition,

663 1
View
animation-designer logo
majiayu000/claude-skill-registry

animation-designer

Expert in web animations, transitions, and motion design using Framer Motion and CSS

663 1
View
diagramming logo
majiayu000/claude-skill-registry

diagramming

Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...

663 1
View
h3-pg logo
majiayu000/claude-skill-registry-data

h3-pg

PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.

23 1
View
conductor-development logo
majiayu000/claude-skill-registry

conductor-development

Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...

663 1
View
conductor-status logo
majiayu000/claude-skill-registry

conductor-status

Display project status, active tracks, and next actions

663 1
View
dockerization logo
majiayu000/claude-skill-registry

dockerization

Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.

663 1
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View