科研 Skill
PCB布局布线审查
pcb-layout-review
Audits, finishes, or ports PCB placement and routing using circuit intent, DRC/connectivity, and manufacturing feedback. Use before routing, after autorouting, or before release.
SKILL.md
PCB Layout Reviewer
Use the humanized architecture and circuit constraints as placement policy, not reference-number order or one global wire-length score. Read references/layout-review-checklist.md and references/proven-lessons.md. Record the gate with references/layout-review-record.md and select an evidence path from references/eda-adapters.md. For modules, card sockets, daughtercards, or dense connector fanout, also read references/connector-stack-and-fanout.md. For a derivative board, also read references/variant-porting.md.
Establish truth
- Read repository rules, native board/project sources, product brief, architecture, sourcing lock, circuit review, schematic/netlist, mechanics, enclosure, manufacturer constraints, and project-local layout lessons.
- Identify the board source of truth and supported adapter. KiCad may use native CLI/API tooling; other EDA tools require equivalent native exports. Gerber or images alone permit review, not safe editable round-trip.
- Record board/project hashes, layer stack, net classes, rules, placement, connectivity, raw DRC, classified DRC, via/drill histogram, and top/bottom renders before changing anything.
- Record connector maturity and every assembly dimension as measured, drawing-derived, inferred, or TBD. Treat a plausible model as visual evidence, not mechanical proof.
- Distinguish hard constraints from negotiable targets. Never trade a short, new open, corrupted return path, unsupported pad, keepout violation, unsafe ownership state, or fabrication violation for a better score.
Port a derivative variant
- Freeze and hash the proven donor. Write an explicit delta for connector pin order and pitch, removed/added functions, power and audio paths, outline, mating datum, tongue, shell features, keepouts, and assembly constraints.
- Treat the port as a constraint remap, not a crop, scale, or pin-count swap. Preserve the mating edge and add area only in a mechanically verified direction.
- Reuse functional blocks, pin-bank orientation, local support relationships, and proven topology rather than absolute coordinates. Re-run architecture, mechanics, power/reference, and placement gates on the variant.
- Geometry-lock every candidate. Integrate a coupled corridor donor as one atomic net set and prove every displaced or non-whitelisted net.
- Diagnose an autorouter from its actual input/output: verify target pins, fixed versus movable scopes, target-route occurrences, and whether the minimum blocker was allowed to move.
- Compare donor and variant with one orthographic physical scale and explicit dimensions. Independently fitted screenshots are not size evidence.
Review in order
- Architecture placement: align external connector pin order with functional corridors; place protection, translation, processing, memory, and outputs along real flow. Keep ownership and reset controls direct.
- Critical locality: decoupling in the supply-pin escape path, tight regulator loops, correct crystals/feedback, connector protection, antenna edge/keepout, user access, thermal paths, and enclosure clearance. Before signal routing, prove that every dense connector/module power and GND pad has a legal standard-process escape or an approved process exception.
- Layer and reference strategy: choose layer count from bus density, routing channels, return paths, RF, controlled interfaces, power current, board size, and fabrication cost. A solid reference plane is normally more valuable than a dedicated low-current power plane; never assume four or six layers without analysis.
- Routing: preserve continuous return paths, short critical controls, sensible topology, no stubs where forbidden, appropriate width/spacing, matched pairs/groups only when budgets require them, and legal transitions.
- Power and zones: prove every rail and GND pad reaches the intended network. Same net name, overlapping fill, or zero pad-opens is not proof.
- Manufacturing: compare trace/space, annulus, mechanical drill, via type, finish, thickness, impedance, and other cost thresholds with the current fabricator quote. Treat premium features as measured DFM feedback, not an automatic reason to weaken electrical constraints.
- Independent visual pass: inspect clean 2D views, each signal layer, and
fresh top/bottom 3D renders. Verify bodies, pin 1, polarity, connector
overhang, pad support, antenna, outline, keepouts, silkscreen, and mechanics.
Run silk-over-silk, silk-over-copper, and edge-clearance checks before the
visual pass; preserve pin-1, polarity, and functional meaning, and leave
unresolved dense labels at
USER_REVIEW.
Experiment safely
Use named candidate states and paired project files. Make one coherent change,
then measure raw disconnects, real DRC, power disconnects, layout gates, and
manufacturing defects. Record it with scripts/score_experiment.py; write new
project-specific lessons with scripts/record_lesson.py. Both default to
.pcba-workflow/ and never mutate the installed skill.
Freeze the input and compare stackup, outline, via-process, and routing experiments with the current best safe candidate using the complete gate vector. A larger board or extra layer is useful only when it removes a measured blocker without regressing another gate.
Prefer high-scoring applicable methods. Do not repeat a negative method unless conditions materially changed. An accepted candidate must be a measured net improvement and may not add opens, real DRC, power disconnects, or verified manufacturing defects. A successful route for one trapped net is not promotable when its coupled donor set is incomplete or another lane becomes stranded.
In a recorded workflow, preserve hash-bound frames for initial placement, placement freeze, meaningful accepted/rejected experiments, final routing, individual signal layers, DRC/connectivity proof, and top/bottom 3D. Record actual regressions when they teach something, but never introduce a defect for the video. Keep every frame tied to the paired native board/project state.
Release gate
Require zero unexplained raw disconnects, zero real DRC errors, zero power
disconnects, all project layout checks passing, verified planes/critical nets,
and visual/mechanical/silkscreen PASS in the same saved board/project state.
If assembly depends on an unverified connector body, card thickness, insertion
depth, retention feature, or enclosure stack, the result remains
USER_REVIEW or BLOCKED even when DRC is clean.
Document only narrow, evidence-backed waivers in
.pcba-workflow/layout-review.json. Hand the result to
$release-pcba-fabrication; supplier CPL interpretation remains a separate
$operate-jlcpcb-order gate.
示例提示词
帮我在走线之前审查一下这块板的元件布局是否合理。
所属插件
安装该插件会一并获得同领域的 63 个 Skill / MCP。
同插件的其他科研 Skill
- ANDES电力系统动态仿真Runs ANDES power-system dynamic studies via PowerMCP: power flow, eigenvalue analysis, and time-domain simulation. Use for damping, stability, or oscillation-mode questions.
- 电池选型与电源预算Builds an evidence-tagged power budget and sizes a manufacturable battery with pouch outline, seals, and derating. Use when sizing runtime, mAh, charging, or supply rails.
- FPGA比特流生成与烧录Generates a Xilinx FPGA bitstream and programs it over JTAG, or burns an MCS image into flash for power-on boot. Use when flashing a board or diagnosing boot failures.
- 硬件项目发布包组装Assembles a hardware release package (fab files, BOM/CPL, carts, assembly guide, hashed manifest) and runs a ready-to-build gate. Use before ordering prototypes.
- 时钟域交叉风险审查Audits clock-domain-crossing risk on an FPGA design and applies the smallest safe synchronizer or constraint fix. Use to resolve CDC violations before sign-off.
- 硬件产品认证合规规划Plans certifications a hardware product needs per target market (FCC, CE/RED, UKCA, battery/radio rules), with cost and lead-time estimates. Use before PCB or enclosure tooling.
- Vivado XDC时序约束编写Authors a Vivado XDC timing constraint set from scratch: clocks, I/O delays, and timing exceptions. Use first, before timing closure, on a design with no or incomplete constraints.
- N-1/N-2应急违规处置Playbook for N-1/N-2 contingency violations: ranks contingencies and proposes preventive and corrective actions. Use after a study shows voltage or thermal problems.
- 潮流计算不收敛诊断Playbook for power-flow convergence failures in PSS/E, PSLF, PowerWorld, pandapower, PyPSA, surge, or OpenDSS. Use when a case diverges or fails to solve.
- 硬件成本核算与采购Prices a hardware product at multiple volumes with one-time vs per-unit cost, landed cost per country, and sourcing leads. Use to estimate unit cost before a pitch.
- RTL仿真覆盖率收敛Measures RTL simulation code coverage and iteratively closes it toward a target by adding testbench stimulus. Use for a sign-off-grade coverage report.
- 配电网DER接纳能力治理Playbook for distribution DER hosting-capacity limits: voltage rise, reverse flow, and thermal limits from PV and storage. Use to estimate how much DER a feeder can host.
- 电子电路设计与审查Designs, audits, or corrects an electronic circuit from a brief, schematic, or netlist, checking power domains, reset sequencing, and ratings. Use for circuit review.
- 硬件可制造性红队审查Red-team audit that fix-loops a hardware project to ready-to-build, re-deriving parts, rails, battery physics, and cost. Use for a reality check before committing to a design.
- 电力系统动态稳定处置Playbook for dynamic stability problems: poor damping, angle instability, or sustained oscillations from eigenvalue or time-domain studies. Use after an unstable study result.
- Egret电力市场调度优化Runs Egret market/operations optimization (DC-OPF, AC-OPF, unit commitment) via PowerMCP. Use for cheapest dispatch, unit commitment, or congestion checks.
- 电子元器件选型核查Researches electronic components against primary sources: part numbers, datasheet limits, lifecycle, stock, and price breaks, one dossier per part. Use to verify or source a BOM.
- EMC电磁兼容预测试Plans grounding, shielding, and filtering for EMC/EMI, and runs an emissions pre-scan with a root-cause fix sequence. Use before a lab test or after a failed EMI scan.
- 产品外壳参数化建模Designs a hardware enclosure as parametric CAD with STEP/STL/GLB output, a DFM check, and Blender assembly validation. Use when designing a case or checking fit.
- 电网频率响应问题处置Playbook for frequency problems: low inertia, high RoCoF, weak primary response, or UFLS risk after loss of the largest unit. Use when a study flags frequency issues.
- FPGA RTL到比特流全流程Drives a Xilinx FPGA design end to end through RTL, simulation, synthesis, implementation, and bitstream, gated at every stage. Use to run the complete build flow in one pass.
- 硬件产品全流程总协调Leads a physical electronic product from idea to a doable design, coordinating specs, parts, battery, PCB, enclosure, render, and cost sub-skills. Use starting a hardware product.
- 硬件原理图与BOM审查Reviews hardware projects: checks schematics against datasheets, pin connections, and firmware-to-hardware alignment across KiCad/Altium files. Use for a design alignment check.
- FPGA ILA在线逻辑调试Inserts an Integrated Logic Analyzer, programs the board, arms a trigger, and reads captured waveforms on real FPGA hardware. Use when sim passes but the board fails.
常见问题
PCB布局布线审查能做什么?
Audits, finishes, or ports PCB placement and routing using circuit intent, DRC/connectivity, and manufacturing feedback. Use before routing, after autorouting, or before release。
如何安装PCB布局布线审查?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「PCB布局布线审查」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
PCB布局布线审查需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
PCB布局布线审查经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。