Circuitry

Controls for board pad inspection, design-rule results and assembly variants.

Build a specialised workspace with Vlak’s paper, ink, and hairlines. Each component includes a live specimen, a contextual example, and generated documentation for agents.

Board pad inspection

Example geometry and nets are supplied records; no board calculation runs here.

Connector pads

Example board, revision C

Pad
Pad identifier
pad-a
Footprint reference
J1
Pad number
1
Net
Supply
Pad type
Through hole
Shape
Circle
Layers
Front copper, Back copper
Supplied geometry
DimensionValueUnit
Pad diameter1.80mm
Drill diameter0.90mm

Selected pad: pad-a

Browse the collection

Keep pad identity, nets, layers and geometry together; inspect supplied rule violations with their recorded status.

  • Pad inspector. Circuit-board pad selection with supplied footprint references, net and layer records, pad types and a dimension table with explicit units.
  • Design rule results. Supplied board-check violations with severity and status filters, object and location details, and host-confirmed selection and resolution actions.

Inspect population, bill-of-materials inclusion and placement inclusion independently for every reference and variant.

  • Assembly variant matrix. Edits independent population, bill-of-materials, and placement flags per reference and assembly variant, preserving unspecified choices.

Preserve independent assembly flags

Population, bill-of-materials inclusion and placement inclusion are separate supplied flags. An unspecified state is not false and no flag silently rewrites another.

Read geometry without inferring connectivity

Pad numbers, net assignments, layer names, shapes and dimensions come from the board model. Missing data remains explicit; these views do not run a netlist, router or geometry engine.

Keep rule results tied to their source

The host provides violation severity, status, location and available resolution actions. A resolve request does not establish that a board passes its rules; return confirmed results after the board model changes and checks rerun.

Agents can read this guide as Markdown, filter the MCP catalogue by electronics, or search for individual components through the CLI.