easygerber7.36 KB
View saved version →
---
name: easygerber
description: Create, inspect, revise, export, or explicitly delete EasyGerber circuit boards, or submit user-requested EasyGerber feedback, using its remote MCP tools. Use for EasyGerber board work, bug reports, and feature requests; ordinary firmware-only edits do not require this skill.
---
# EasyGerber board design
Use the installed EasyGerber MCP tools and their current schemas. Hosts may prefix tool names differently. If the connection is missing, direct the user to https://easygerber.com/agents. Never ask for credentials in chat or read them from project files.
Follow [the workflow reference](references/workflow.md) for the thin schematic format, placement, physical settings, recovery, and permission details.
## Create and continue a board
1. Read only the relevant requirements and firmware to identify signals, power, and connectors. Send the minimum needed board data. Clarify electrical choices that cannot be inferred.
2. Search published parts with `search_parts`, supplying known filters and electrical requirements. Public browsing needs no account or board. Reuse a qualified candidate's returned ID, facts and verified pins. Check another candidate on mismatch. Resolve unknowns against the exact part’s datasheet and operating conditions. Only the first candidate includes pins when available. Call `get_part` on the selected ID for missing pins or facts. Preserve catalog IDs, pin identities, footprints, and available 3D models. For an existing board's strict Part List, retain its `boardRef` on every catalog call.
3. For a new board, generate one private `boardRef`: `egbr1_` followed by 32 cryptographically random bytes encoded as unpadded base64url (43 characters after the prefix). Call `create_board` with that reference, a fresh UUID `requestId`, a name, the complete thin intent, and `boardEdits` that size the board and position every part and reference designator. Nothing is placed or sized automatically; the layout routes the board as you placed it. The service uses the valid connected account or establishes private access automatically. No guest setup or account-mode choice is needed. Leave other settings at their defaults; author only requested app-visible settings. Never invent parts or hidden routing/manufacturing constraints.
4. Keep the same `boardRef` in private tool context across turns and pass it to all subsequent board operations. It replaces the need to coordinate a board ID and a separate access token. Each save returns the board's current `revision`: use it as `expectedRevision` with a new request ID for the next edit, and read `get_board` first when you do not hold the current board. On a revision conflict, reread and reconcile instead of overwriting a newer change.
5. Saving lays out the board. Each successful `create_board` or `update_board` that leaves the board without a current layout starts the layout, waits for it and for its check, and returns the board as it is afterwards: its new `revision`, `layout.current`, and `validation` with any blocking issues. If the result has `pollAfterSeconds` instead, the layout is still running: follow that `generation.id` with `get_generation` (with the same `boardRef` alone if the ID was lost), wait the returned interval, and stop at completed, failed, or cancelled; then use its `boardRevision` and run `check_board_layout`. Call `generate_layout` only to retry after a failed or cancelled job, or when a save reports `layoutNotStarted`; never to ask whether a job finished.
6. Return the private board link and requested artifacts. For manufacturing export, report any blocking issues in the saved board's `validation`; when it is null on a current layout, run `check_board_layout` first. For an editable `.egb` backup, export the valid saved project directly, even if layout is missing, incomplete, or stale; do not generate or check a layout solely for that backup.
The reference is private authority, not a public board UUID or a request ID. Ke
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.