Community recipe · Computer tasks
Build a reviewable PCB fabrication candidate from engineering requirements
Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.
The problem
Turning circuit requirements into fabrication files involves component, pin-mapping and geometry checks that can leave costly ambiguities for an engineer to resolve.
Agent job
Clarify requirements, verify components and pins, edit KiCad files and review electrical, design-rule and geometry checks.
Expected output
A PCB fabrication candidate, validation findings and sourced cost estimates for engineer approval.
Where this framing comes from
- Core problem: Editorial purpose framing
- Agent job: Editorial purpose framing
- Expected output: Editorial purpose framing
- Relevant job roles: Editorial purpose framing
- Benefit type: Editorial purpose framing
Editorial framing and outcome limits
Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.
Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.
Case-specific decision guidance · untested
Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.
Read the attributed source evidence and original caveats below ↓
Why use this
A PCB can pass automated checks while a connector orientation, footprint or component substitution remains wrong for the intended assembly. Manufacturing files make these ambiguities expensive because a clean export can still describe an unusable board.
This job could organize a fabrication candidate around explicit engineering decisions and evidence. Keeping requirements, component provenance and unresolved geometry issues beside the files would help an engineer decide what is ready for review and what must remain blocked.
Why an agent / simpler alternative
- Useful judgment
Cross-check structured requirements, pin mappings and design reports for engineering review.
- Simpler alternative
Use a proven reference design when the required circuit already matches a supported configuration.
- Unsuitable when
The design is safety-critical or the agent is expected to certify electrical performance.
Proposed inputs
- Name
Engineering requirements
- Owner
Design owner
- Minimum scope
Power, interfaces, mechanical constraints and intended operating conditions
- Quality check
Identify critical missing specifications before component selection.
- Name
Design and component references
- Owner
Engineer
- Minimum scope
Authorized KiCad copies, datasheets, footprints and approved parts
- Quality check
Verify exact part variants and pin-one/orientation conventions.
Access and setup — proposed or unknown
- Proposed minimum
Work on versioned design copies and propose validation before local export or supplier interaction.
- Compatibility unknowns
Unknown: KiCad versions, helper compatibility, part availability and manufacturing constraints.
- External actions requiring approval
Installing tools, uploading designs, ordering boards or publishing intellectual property.
Expected deliverable and review checks
- Proposed artifact
Fabrication-candidate package plan with requirement traceability, check reports, unresolved issues and cost-source fields.
- Critical checks
Schematic pin assignments agree with footprints and connector orientation.
ERC/DRC passes do not override unresolved mechanical or component evidence.
- Missing output evidence
No new run or output inspection in this editorial layer; see linked source-specific limits.
Failure signals and proposed responses
- Signal
A footprint matches the part name but reverses connector orientation.
- Why it matters
Assembly may be physically incompatible despite electrical connectivity.
- Proposed response
Inspect datasheet and board geometry together and block readiness until confirmed.
- Signal
A suggested replacement has a different voltage or package rating.
- Why it matters
A sourcing change could invalidate the design.
- Proposed response
Require engineer review of the substitution against all relevant requirements.
Effort and cost — unknown
- Setup work
Complete requirements and verify component/footprint provenance.
- Ongoing review
Review design-rule exceptions and reassess supplier substitutions.
- Unknowns
Unknown: fabrication prices, component supply, engineering review and physical validation costs.
First check — proposed, unexecuted
- Status
proposed_unexecuted
- Synthetic fixture
A synthetic low-voltage connector board has a mirrored footprint and a substitute part with an incompatible rating.
- Acceptance checks
Both issues block the fabrication candidate.
No supplier upload or order is implied by a clean file export.
- Stop conditions
Critical requirements, orientation or component suitability remain unresolved.
Limits
A reviewable file package is not evidence of a working circuit, manufacturability or regulatory certification.
Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.
Original source
https://github.com/liseman/pcbclaw/blob/main/SKILL.md ↗Attributed to: liseman
Community recipe- Original action type
- computer_action
- What the source supports
- The agent clarifies critical requirements, checkpoints work, verifies components and pin mappings, edits KiCad files, reviews ERC/DRC and geometry, then packages manufacturing files and sourced cost estimates.
- Source outcome limits
- Documented recipe only. No fresh-machine end-to-end design run, fabricated board, physical circuit test or production certification inspected.
- Evidence attribution caveat
- This community recipe describes a procedure; it does not prove successful execution or independently reproduced results.
- Source approval description
- Critical gaps require clarification. Supplier access/uploads and publication require authorization; local exports follow design validation. Unresolved orientation problems block readiness.
- Named tools
- OpenClaw, KiCad, kicad-cli, pcb_helpers.py, JLCPCB/LCSC
- Model or version
- pcbclaw 0.2.0-beta.1; OpenClaw compatibility noted against 2026.9.4; KiCad 9 target
- Publication date
- Unknown
- Source last checked
- 2026-10-14
- Demonstrated in Canada
- Unknown
- Canadian availability
- Unknown
- Proposed Canadian adaptation
- Verify Canadian component availability, delivered currency/taxes and relevant electrical requirements before adaptation; no Canadian deployment or entitlement verified.
- Recommended approval boundaries
- Engineer approval before fabrication; explicit supplier-upload, purchase and publication approval.