Skip to content

Keitark/pcba-design-skills / .agents/skills/pcb-layout-review

pcb-layout-review

Verified

Audit, finish, or port PCB placement and routing using circuit intent, mechanical constraints, sourcing evidence, native DRC/connectivity, rendered views, and manufacturing feedback. Use before routing, after autorouting, before fabrication release, when adapting a proven board to another connector, enclosure, platform, or regional variant, or when reviewing layers, GND references, power distribution, decoupling, buses, controlled interfaces, RF keepouts, vias, cost-driving features, opens, or DRC findings.

references/eda-adapters.md

View on GitHub
# PCB layout adapters

An adapter must identify native source/project, supported edit method,
connectivity query, raw/classified DRC, layer/zone inspection, renderer,
manufacturing export, protected artifacts, and known limitations.

- **KiCad:** first-class text project/board plus `kicad-cli` and supported
  native API/IPC. Pair board and project rules when snapshotting.
- **Altium:** use PCB project, rules, native DRC, layer stack, Draftsman/outputs,
  and automation. Do not modify binary PCB documents with a generic parser.
- **EasyEDA Standard/Pro:** use the matching editor/export and distinguish the
  editions. Capture rule, layer, and origin conventions.
- **EAGLE/Fusion Electronics:** use legacy XML only when it is authoritative;
  otherwise use Fusion's native project/export path.
- **IPC-2581/ODB++:** useful structured review/manufacturing evidence when the
  exporter is trusted, but not automatically an editable source.
- **Gerber/drill/CPL or images only:** permit DFM and visual review. They cannot
  safely prove full net connectivity or support arbitrary layout edits.

For unsupported tools, require equivalent evidence or mark the affected gate
BLOCKED; do not fall back to visual plausibility.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall