Skip to main content
PCBFreeNewv1.0.0

阵列摆放与电源打孔规划

矩形/蛇形器件阵列坐标与位号冲突检查、电源地焊盘八方向逃逸打孔规划(旋转焊盘包络、过孔/焊盘 clearance 碰撞);离线契约报告。

Installs: 0Rating: –Updated:
Claude CodeCursorCodexGemini CLI+1

Badges only claim the demo-run passed on that host; cross-host installation is handled by the adapter layer.

Preview gallery

You say
Generate coordinates and designators for a 4×8 LED array at 5 mm pitch with serpentine numbering, and plan escape vias for the given power pads.

Content matches the files inside the package; extracted by the publish pipeline.

LCEDA placement / pattern generation bundle

Offline cores from two Apache-2.0 LCEDA plaza extensions: array-generator (grid math, self-labeled pure) and lceda-pcb-autofanout (net classify + escape geometry + collision rules). Silkscreen/outline/beautify members are procedures (references/procedures.md).

Cores

scripts/demo.mjs (Node >= 20, no deps):

  • Array: row/col/serpentine order, x = ox + c*colSpacing, y = oy + r*rowSpacing (mil); designators prefix + (start+i); conflict = intersection with existing designators; limits rows/cols 1-50, total <= 1000.
  • Fanout: only power/ground nets (GND token regex, V-token/voltage regex); 8 directions ordered by pad aspect; distance = padExtent + stub + viaRadius + step2viaRadius with padExtent = (|cos|+|sin|)*mask + |cos|*sizeX/2 + |sin|*sizeY/2; collisions: point-rect pad clearance, circle-circle via clearance; via-in-pad when 2r <= min(padW,padH); merge same-net vias within maxIdealExtent + stub + viaRadius + 2viaRadiusmergeFactor.

Run

node scripts/demo.mjs --out-dir <dir> [--input <json>]

Default scripts/fixtures/input.json; stdout = edaskills.report.v1; artifacts array-positions.csv, fanout-plan.csv. Input: { array:{rows,cols,rowSpacingMil,colSpacingMil,originX,originY, order,prefix,startNum,existing[]}, fanout:{pads:[{id,net,x,y,sizeX,sizeY, rotation}], vias:[{x,y,diameterMil}], config:{viaHoleMm,viaDiaMm,stubMm, clearanceMm,traceWidthMm,maxSearchSteps,mergeFactor}} }.

When to use

  • Pre-place LED/key matrices and check designator collisions before batch creation in-editor.
  • Plan BGA/power fanout vias offline, then apply in-editor with DRC.

Not for: polar arrays (not in source), trace routing between vias, keepout-aware escape (in-editor), or silkscreen art generation.

What you get

  • Rectangular/serpentine array coordinates with row/col-major numbering
  • Designator conflict pre-checks
  • Power/ground escape-via plans (8 directions, rotated extents, clearance collisions)

Good fit for

  • Bulk placement of LED matrices, resistor arrays and headers
  • Via planning for dense power/ground pads

Not for

  • Executing placement in the editor (coordinates and plans only)
  • SI-driven via optimization (use the cross-plane review skill)
Before you start

You provide

  • Array rows/columns/pitch/origin/numbering mode
  • Pad geometry plus existing via/pad occupancy JSON

Environment

  • node ≥ 20

Last tested

v1.0.0 · Claude Code, Cursor, Codex, Gemini CLI · Ran 2026/11/19

Dependencies

No dependencies
This skill works standalone.

Demo run

Passed with warnings0 errors · 3 warnings

node v24.19.0 · 2026/11/19

  • [info] FANOUT (P1): via at (100, 174.96) mil, 90 deg step 2
  • [info] FANOUT (P2): via at (140, 174.96) mil, 90 deg step 2
  • [info] FANOUT (P4): via at (140, 214.96) mil, 90 deg step 2
  • [warning] NO_ESCAPE (P5): no free escape direction for P5 (+5V)
  • [warning] VIA_IN_PAD (P6): via fits inside pad; confirm fab capability (filled/plugged)

FAQ

Ratings & reviews

Not rated0 ratings

5 star0
4 star0
3 star0
2 star0
1 star0

Sign in to rate this skill.

Sign in

Versions

  • v1.0.0Latest187.8 KB

    首发种子版本。

    License: MITSourceSHA-256: bc591db6d715c274…

Related skills