---
name: deadbyte-advanced-pcb-engineering
description: Evidence-driven advanced PCB engineering workflow for schematic review, constraint capture, stackup-aware placement and routing, power and signal integrity, EMC, DFM/DFT, KiCad verification, manufacturing release, and hardware bring-up.
version: 1.0.0
audience: agent
---

# DEADBYTE ADVANCED PCB ENGINEERING

Use this skill for serious PCB design, review, rework, manufacturing preparation, and board bring-up. It is optimized for KiCad source artifacts but the engineering workflow applies to other EDA tools when equivalent primary evidence is available.

## Core law

The schematic expresses intent. The board file expresses implementation. ERC, DRC, manufacturing outputs, measurements, and hardware observations are evidence.

Never invent a stackup, dielectric constant, loss tangent, copper thickness, trace impedance, current capacity, thermal rise, manufacturer capability, timing budget, or connector pinout. Mark missing inputs as UNKNOWN and stop the affected calculation or claim.

Do not call a board ready because it renders, routes, exports Gerbers, or passes one checker.

## Operating loop

1. Freeze board identity: project, revision, source hashes, EDA version, target manufacturer, board class, environment, and physical envelope.
2. Extract the electrical interface matrix from the schematic: rails, clocks, resets, boot straps, buses, differential pairs, analog nodes, RF, connectors, test points, and programming paths.
3. Write the constraint contract before routing. Separate electrical, stackup, fabrication, assembly, mechanical, thermal, and test constraints.
4. Establish stackup and reference-plane assumptions before impedance or high-speed routing.
5. Place from physics outward: connectors and mechanical locks, power entry, clocks, high-speed endpoints, regulators, memory, analog, then low-speed logic.
6. Establish return-current paths before route aesthetics. Do not cross plane splits with fast signals unless the return path is explicitly engineered.
7. Close power integrity: source path, protection, regulation, bulk storage, local decoupling, high-frequency loop area, transient current, copper loss, and thermal dissipation.
8. Route critical interfaces from their actual edge rate and topology. Length matching is subordinate to topology, reference continuity, coupling, and timing budget.
9. Close EMC and ESD paths at the boundary. Keep noisy current loops local. Give external transients a short controlled path away from sensitive logic.
10. Add DFM and DFT evidence: clearances, annular rings, drill limits, solder-mask policy, fiducials, tooling, test points, programming access, polarity/orientation checks, and rework access.
11. Run deterministic board probe, EDA ERC/DRC, and the declared constraint gate. Preserve exact outputs and hashes.
12. Export fabrication and assembly artifacts only after source verification. Hash the release set and record the exact source revision that produced it.
13. Build a bring-up plan before power is applied. Start with shorts and rail resistance, current-limited power, sequencing, clocks, resets, boot straps, debug access, then peripherals.
14. Close each claim with observed evidence. Report PASS, FAIL, PARTIALLY VERIFIED, BLOCKED BY EVIDENCE, or HYPOTHESIS ONLY.

## Evidence hierarchy

Prefer datasheets and package drawings for external facts; native schematic and PCB sources for implemented connectivity and geometry; EDA ERC/DRC for rule checking; deterministic source inspection for structural observations; manufacturing outputs for release consistency; bench measurements for physical behavior.

A screenshot is weak evidence. A rendered trace is not a measured impedance. A DRC pass is not signal-integrity proof.

## High-speed rule

Before tuning a fast net, identify driver, receiver, signaling standard, edge rate, topology, reference plane, layer transition, via structure, stackup geometry, termination, timing budget, and allowed discontinuities. If any parameter required for a numerical claim is missing, do not fabricate the number.

## Bundled references

Load only what the task needs:
- references/constraint-model.md
- references/high-speed-layout.md
- references/power-integrity.md
- references/emc-mechanical-dfm.md
- references/bringup-evidence.md
- references/kicad-native.md

## Deterministic helpers

Use scripts/kicad_pcb_probe.py on a native KiCad PCB file. It performs a non-executing S-expression parse and emits source hash, format identity, layer list, net names, footprint/segment/via/zone counts, track-width range, and via geometry range.

Use scripts/pcb_constraint_gate.py with a JSON contract to compare observed source metrics against explicit minima and required names. The gate can prove only the rules it implements. It does not replace ERC, DRC, field solvers, thermal analysis, or bench measurement.

## Completion contract

Before claiming FAB READY or BOARD VERIFIED, record exact source hashes, exact EDA/tool versions, ERC and DRC results, constraint-gate result, unresolved waivers, fabrication and assembly output hashes, unverified SI/PI/thermal/EMC/mechanical assumptions, and physical bring-up evidence for hardware-dependent claims.

Never weaken a rule or verifier to make the board pass.
