Keitark/pcba-design-skills / .agents/skills/pcb-layout-review
pcb-layout-review
VerifiedAudit, 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.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 7.5 KB |
| agents/openai.yaml | config | 245 B |
| references/connector-stack-and-fanout.md | markdown | 3.5 KB |
| references/eda-adapters.md | markdown | 1.2 KB |
| references/layout-review-checklist.md | markdown | 4.4 KB |
| references/layout-review-record.md | markdown | 1.9 KB |
| references/proven-lessons.md | markdown | 3.5 KB |
| references/variant-porting.md | markdown | 5.5 KB |
| scripts/record_lesson.py | script | 1.7 KB |
| scripts/score_experiment.py | script | 3.6 KB |
references/proven-lessons.md
View on GitHub# Proven reusable layout lessons
- Freeze placement from architecture and physical connector pin order before
optimizing wire length or launching an autorouter.
- Route shared spines and scarce corridors early. Late common-bus routing can
strand endpoints even when block placement is reasonable.
- Reserve routing capacity for power fanout before dense signal routing. Never
treat different power nets as one category during collision checks.
- Avoid via-in-pad on fine-pitch parts unless the footprint and fabrication
process explicitly support it. Use collision-checked offset fanout.
- A new through-via must be checked on every traversed layer and verified to
retain its requested net after save and any selective zone refill.
- Refill only affected zones after local edits; global refill can change
connectivity under rule or setting drift.
- Reject a zero-open candidate that adds clearance, short, power-island, return-
path, or manufacturing defects. Connectivity and physical legality are
independent metrics.
- Treat live quote surcharges as feedback. Resize only verified legal features,
preserve density-critical exceptions, regenerate all checks and release
artifacts, and compare the new quote.
- Supplier placement preview is not PCB placement validation. It is a separate
post-release interpretation requiring machine and visual review.
- Treat a connector, enclosure, platform, or regional derivative as an
electrical-and-mechanical constraint remap, not a cropped parent layout.
- Preserve the mating-edge datum, fingers, tongue, and insertion keepouts. Add
board area only in a direction verified against the host and enclosure.
- Reuse functional topology and physical pin-bank orientation rather than
absolute donor coordinates; repeat every placement and reference-path gate.
- Import coupled corridor repairs atomically. Never cherry-pick the headline
net from a donor that also displaced neighboring lanes.
- When an autorouter omits a target route, inspect target pins, fixed/movable
scopes, and result occurrences before changing normalization or retry flags.
- Compare derivative boards at one orthographic physical scale. Independently
fitted renders cannot prove relative dimensions or mechanical fit.
- Close layout review with normalized silkscreen checks and both-side visual
evidence. Preserve polarity/pin-1 meaning and classify intentional connector
overhang separately from fabrication defects.
- Promote connector mechanics in stages: electrical mapping, exact orderable
part, verified footprint, defined mating stack, then measured physical fit.
A clean DRC cannot replace a missing connector sample or drawing.
- Distinguish harmless body/mating-mouth overhang from pads or support features
that lack substrate. Check transformed physical pads against the real outline.
- Classify every dense connector/module power and GND escape before signal
routing. Local placement and pad-specific dogbones are safer than hoping a
later fill or generic via grid will repair an impossible corridor.
- Treat same-net zone fragments as real opens until each reaches the canonical
rail through individually proven copper or stitches.
- Compare layer, outline, via, and routing experiments with the best safe saved
candidate from the same frozen input. Zero opens alone is not improvement.
- Use same-scale native multi-board renders and an orthographic dimension view;
label geometry estimates and proxy bodies so presentation evidence is never
mistaken for mechanical release proof.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |