Skip to main content
skill CX Codex

fab-release — Claude Code skill for PCB fabrication

The fab-release Claude Code skill prepares manufacturing files from a KiCad project through Copper. It runs on requests to export Gerbers, release a board, or estimate PCB or PCBA costs.

MIT ★ 119 updated 2026-11-16

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add claynicholson/copper-kicad-mcp
/plugin install copper@copper
Open on GitHub

What fab-release does

The skill creates a fabrication package from a KiCad project using Copper: Gerbers, Excellon drill data, a BOM, and a component placement file. Choose a built-in or custom fab profile; jlcpcb is the default. Other built-in options include pcbway, oshpark for bare boards, and generic for Gerber X2, Excellon, a KiCad position file, and a plain BOM.

Before export, Copper checks ERC and DRC, schematic-to-board parity, component sourcing, and design review. The board revision must also be updated and a checkpoint created. Export is blocked when a profile rule fails; a check can be waived only with the user's explicit consent, and the waiver must be reported. Files go to <project>/copper-out/fab/.

What it helps with

  • prepare Gerbers and drill data for board fabrication
  • create a BOM and component placement file
  • check a PCB before sending it to a fab
  • estimate component loading costs for a board

Example prompts for the agent

  • Prepare a manufacturing package for this KiCad project and report any release blockers.
  • Export Gerbers for a JLCPCB board order.
  • Create the BOM and placement file for PCB assembly.

How to install fab-release

1Plugin marketplace

/plugin marketplace add claynicholson/copper-kicad-mcp
/plugin install copper@copper

This installs the whole copper plugin with all its skills

2Skills CLI (Vercel)

npx skills add claynicholson/copper-kicad-mcp --skill fab-release -a claude-code

3Manually: put the files in place

~/.claude/skills/fab-release/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/fab-release/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about fab-release

How do I install fab-release in Claude Code?

Add the marketplace with /plugin marketplace add claynicholson/copper-kicad-mcp, then install the plugin with /plugin install copper@copper.

What does fab-release do?

It builds a PCB fabrication package through Copper, including Gerbers, drill data, a BOM, and a placement file. Copper runs board and parts checks before export.

What does fab-release need to work?

It needs a KiCad project used with Copper. Export follows the active fab profile; custom profiles can be stored in $COPPER_HOME/fabs/ or <project>/.copper/fabs/.

Source text

SKILL.md · MIT
---
name: fab-release
description: Produce a manufacturing package (Gerbers, Excellon drill, BOM and placement file) for a PCB fab from a KiCad project with Copper, after verification gates pass. Works with any fab through fab profiles — JLCPCB by default, PCBWay, OSH Park, a generic Gerber X2 pack, or a user-defined profile. Use when the user asks to "order", "export gerbers", "make fab files", "release", "send to the fab" or wants a cost estimate for PCB/PCBA.
---

# Releasing a board to a fab with Copper

Which fab the pack is for is **configuration, not an assumption**. `copper_status` (or `project_summary`) shows the
project's active fab profile under `config`; `fab_export(profile='list')` lists every profile with its design rules,
what blocks an order, and a `notes` field saying which numbers were checked against the fab and which were not.
Never quote a fab's limits from memory: read them from the profile.

Built-in profiles: `jlcpcb` (the default), `pcbway`, `oshpark` (bare boards), `generic` (Gerber X2 + Excellon +
KiCad position file + plain BOM, for any other fab). Users add their own as JSON in `$COPPER_HOME/fabs/` or
`<project>/.copper/fabs/`. To use another profile for one export, pass `profile=`; to switch the project, set
`"fab": {"profile": "<name>"}` in `<project>/.copper/config.json` and run `pcb_setup(rules='fab')` so the design
rules follow.

## Gate: do not release a board that fails verification

1. `verify` (ERC + DRC with zone refill + schematic↔PCB parity) → **0 errors, 0 unconnected items**.
2. `parts_source_bom(write=false)` → every assembled part is sourced (for the default setup: an LCSC number with
   JLC stock; with other parts providers: the project's part-number field, or just value + footprint for generic parts).
3. `design_review` → no `high` findings (or the user explicitly accepts each one).
4. Bump the revision: set the title block `rev` and add a dated silkscreen revision text. Make a
   `checkpoint(action="create", label="release vX")`.

## Generate

`fab_export()` writes the order pack to `<project>/copper-out/fab/`. Exact paths are in the tool result:

| Output | Content |
|---|---|
| `gerbers/` + zip | Gerbers for all copper, mask, silk, paste and Edge.Cuts layers and the Excellon drill, plotted with the profile's settings (Protel extensions or `.gbr`, X2 or not, PTH/NPTH split or merged) |
| BOM CSV | the profile's columns; one line per unique part, DNP excluded |
| placement CSV | the profile's own columns with its rotation corrections, or KiCad's standard position file |

With the default `jlcpcb` profile that is `<name>-JLCPCB.zip`, a BOM with `Comment, Designator, Footprint, LCSC Part #`
and a CPL with `Designator, Mid X, Mid Y, Layer, Rotation` (JLC rotation corrections applied), plus Basic/Extended
counts and the estimated Extended-part loading fee.

The tool refuses (`FAB_BLOCKED`) when something the profile lists under `blocks` is wrong. Pass `waive=[...]`
(`erc`, `drc`, `parts`, `outline`, `parity`, `unrouted`, `empty`) only with the user's explicit consent, and state in
your answer what was waived. `assembly=false` makes a bare-board pack.

## Upload checklist (tell the user)

The result's `summary.order_notes` are written for the active profile: relay them. In general:

1. Upload the Gerber zip and check the fab's online viewer: outline, drill holes, silkscreen orientation.
2. FR-4, 1.6 mm, 1 oz copper suits most boards; pick ENIG for fine-pitch QFN/BGA. A 4-layer board needs the fab's
   matching stackup selected.
3. For assembly, upload the BOM and the placement file, confirm every line matched a part, and **check the rotation
   of every polarized part** (diodes, LEDs, ICs, electrolytics, connectors) in the fab's placement preview. Assembly
   houses do not all share KiCad's zero orientation; a profile's rotation table fixes the common cases for that fab,
   but the preview has the final word.
4. Single-side assembly is usually far cheaper than double-sided.

## After ordering

Keep the exact fab folder with the commit/checkpoint. When the boards arrive: check the power rails with a
current-limited supply before plugging in USB, then flash firmware.

© Clay Nicholson · MIT · claynicholson/copper-kicad-mcp

Similar skills

SKILL.md skills catalog →

From the same set5

Project sponsors

Companies that keep this analytics open