Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Kicad Pcb Schematic Layout

ASecurity

Design, route, and verify printed circuit boards (PCBs) using KiCad 8 EDA. Master schematic capture, Electrical Rules Check (ERC), footprint assignments, multi-layer stackups, impedance-controlled trace routing, ground plane stitching vias, Design Rules Check (DRC), and manufacturing fabrication exports (Gerber RS-274X, Excellon drill files, IPC-D-356 netlists). Trigger when designing electronics, routing PCBs, or preparing hardware for fabrication.

8 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgogit

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add hamzabellouch/agent-skills --skill kicad-pcb-schematic-layout --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Kicad Pcb Schematic Layout?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Kicad Pcb Schematic Layout
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hamzabellouch-kicad-pcb-schematic-layout/badge)](https://www.skillsdirectory.com/skills/hamzabellouch-kicad-pcb-schematic-layout)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: kicad-pcb-schematic-layout
metadata:
  category: Hardware Design and EDA FPGA
description: Design, route, and verify printed circuit boards (PCBs) using KiCad 8 EDA. Master schematic capture, Electrical Rules Check (ERC), footprint assignments, multi-layer stackups, impedance-controlled trace routing, ground plane stitching vias, Design Rules Check (DRC), and manufacturing fabrication exports (Gerber RS-274X, Excellon drill files, IPC-D-356 netlists). Trigger when designing electronics, routing PCBs, or preparing hardware for fabrication.
compatibility: KiCad 7+, KiCad 8+, IPC-2221 PCB Design Standard
---

# KiCad PCB Schematic & Layout Skill Guide

This skill governs best practices, electronic design automation (EDA) workflows, and manufacturing readiness standards for designing printed circuit boards in KiCad.

---

## 1. PCB Design Life Cycle Flow

```text
[ Electronic Requirements & Component Sourcing ]
                      |
                      v
[ 1. Schematic Capture (Eeschema) ]
  |-- Connect functional blocks & bypass capacitors
  |-- Assign reference designators & component values
  |-- Run Electrical Rules Check (ERC) -> 0 Errors
                      |
                      v
[ 2. Footprint Association & Netlist Sync (F8) ]
                      |
                      v
[ 3. PCB Layout & Routing (Pcbnew) ]
  |-- Layer Stackup Definition (e.g. 4-Layer: SIG - GND - PWR - SIG)
  |-- Critical Net Routing (Differential pairs, 50-ohm RF, high-current traces)
  |-- Solid Ground Plane Pours & Thermal Relief
  |-- Run Design Rules Check (DRC) -> 0 Errors / 0 Warnings
                      |
                      v
[ 4. Manufacturing Export ] -> Gerbers + Drill + BOM + Pick & Place (CPL)
```

---

## 2. Standard 4-Layer Stackup & Rules

For modern high-speed microcontrollers (ESP32, STM32, RP2040) and high-speed digital buses, a **4-layer board with continuous ground reference planes** is standard practice:

| Layer # | Layer Name | Type | Recommended Usage |
|---|---|---|---|
| **Layer 1** | F.Cu (Top) | Signal / Component | High-speed traces, component placement |
| **Layer 2** | In1.Cu | Solid Ground Plane | Unbroken 0V reference plane for return currents |
| **Layer 3** | In2.Cu | Power Plane / Mix | 3.3V / 5.0V power rail pours, non-critical signals |
| **Layer 4** | B.Cu (Bottom) | Signal / GND | Low-speed signals, bottom test points, solid GND pour |

---

## 3. Critical PCB Layout Design Rules

### A. Decoupling Capacitor Placement
- Place ceramic decoupling capacitors ($0.1\,\mu\text{F}$ and $10\,\mu\text{F}$) **as physically close as possible** to the IC power pin ($\le 2\,\text{mm}$).
- Route power from the capacitor pin to the IC pin directly, or place the via on the outside of the capacitor so current flows through the capacitor pads before reaching the IC:

```text
[ Power Plane Via ] ---> [ Decoupling Cap Pad ] ---> [ IC VDD Pin ]
```

### B. Differential Pair Routing & Trace Geometry
- Use KiCad's Differential Pair Routing tool (`Route -> Route Differential Pairs`).
- Maintain constant trace spacing ($S$) and width ($W$) along the entire run to preserve differential impedance (e.g., $90\,\Omega \pm 10\%$ for USB 2.0 D+/D-).
- Avoid 90-degree corners; use $45^\circ$ bends or smooth circular arcs to prevent impedance discontinuities.

### C. Ground Stitching Vias
- Place ground vias along the perimeter of the PCB at intervals of $\le \frac{\lambda}{10}$ (typically every 3 to 5 mm) to suppress RF emissions.
- Stitch together top and bottom ground copper pours around sensitive analog/RF sections.

---

## 4. Pre-Fabrication Verification Checklist

- [ ] **ERC Cleared:** Zero unconnected pins (use `No Connect` flag on unused pins) and no conflicting power outputs in Eeschema.
- [ ] **DRC Cleared:** Run DRC against the specific fabricator's capabilities (e.g. minimum trace width 0.127 mm, minimum clearance 0.127 mm, minimum via drill 0.3 mm).
- [ ] **Thermal Reliefs:** Ensure thermal relief spokes are enabled on component through-hole pins connected to power/ground planes to facilitate hand-soldering.
- [ ] **Silkscreen Legibility:** Check that reference designators (R1, C1, U1) do not overlap exposed copper pads or vias.
- [ ] **Gerber Inspection:** Review generated Gerbers using KiCad's `GerbView` before submitting to the PCB fabrication house.

Attribution

hamzabellouchhamzabellouch
View sourceSee grades on GitHubMore from hamzabellouch →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →