fritzing-custom-component-workflow
Provides a robust process for designing, mapping, and validating custom electronic components for Fritzing.
Install
mkdir -p .claude/skills/fritzing-custom-component-workflow && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17978" && unzip -o skill.zip -d .claude/skills/fritzing-custom-component-workflow && rm skill.zipInstalls to .claude/skills/fritzing-custom-component-workflow
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill to create or integrate a custom Fritzing part end-to-end with fewer connector and SVG errors.Key capabilities
- →Create a new custom Fritzing part from datasheet information.
- →Adapt an existing Fritzing part to a new variant.
- →Integrate a part into local bins for sharing.
- →Troubleshoot connector mapping, SVG structure, or moduleId issues.
How it works
The skill guides the user through selecting a base part, defining it in Part Creator, building view SVGs, enforcing connector conventions, validating the part, and packaging it.
Inputs & outputs
When to use fritzing-custom-component-workflow
- →Create custom fritzing part
- →Troubleshoot component mapping
- →Integrate part into local library
- →Build part from datasheet
About this skill
Fritzing Custom Component Workflow
Use this skill to create or integrate a custom Fritzing part end-to-end with fewer connector and SVG errors.
When to use
Use this skill when you need to:
- Create a new custom part from datasheet information.
- Adapt an existing forum or GitHub part to a new variant.
- Integrate a part into local bins and prepare it for sharing.
- Troubleshoot connector mapping, SVG structure, or moduleId issues.
Required inputs
Collect these before editing:
- Mechanical dimensions (body size, pin spacing, holes, keepouts).
- Pin map with exact order and names.
- Interface behavior (power, analog/digital, I2C/SPI/UART, active-low details).
- Source references (datasheet, product page, photos front/back).
Workflow
- Select a base part
- Prefer cloning the closest known-good part instead of starting from scratch.
- Keep connector numbering stable from the beginning.
- Define the part in Part Creator
- Set title, label, tags, and author/version metadata.
- Create connector list once and treat numbering as canonical.
- Build view SVGs
- Breadboard: include top-level breadboard group and connector pin/terminal IDs.
- Schematic: use consistent pin geometry and a top-level schematic group.
- PCB: include top-level pcb group and pads matching connector indices.
- Enforce connector conventions
- Part connectors: connector0, connector1, connector2, ...
- SVG IDs: connector0pin, connector0terminal, connector0pad (as applicable).
- Do not switch to name-based connector IDs once numbering is established.
- Validate
- Run static checks (group IDs, connector IDs, missing terminals, mapping drift).
- Perform a smoke test in Fritzing by wiring each connector in all views.
- Export once to verify rendering and connector survivability.
- Package and integrate
- Bundle .fzp with all required SVG views.
- Import to local workspace bins (Contrib or Mine).
- Keep a versioned package copy for rollback.
- Share for review
- Post bundle to Fritzing forum parts-help/parts-submit.
- Include references, dimensions, tested behavior, and known limitations.
Common failure patterns
- Missing top-level SVG view groups.
- Missing connector terminal elements.
- Pin/pad IDs inconsistent across views.
- Schematic pin geometry not following normal conventions.
- Metadata and filename drift after moduleId changes.
Recommended output format
When using this skill, return:
- Short summary of intended part behavior.
- Connector map table (index, label, function).
- Validation findings (pass/fail with fixes).
- Packaging and integration steps.
- Forum-share checklist status.
Acceptance criteria
- Connector indexing is consistent across .fzp, breadboard, schematic, and pcb views.
- Required wrapper groups exist in all SVG views.
- Validation findings are explicit (pass/fail) with concrete remediation for failures.
- Packaging plan includes .fzp and all required SVG assets.
- Share-readiness call is explicit (ready/not ready).
Invocation example
Prompt example:
- Create a custom Fritzing part for a 3-pin water level sensor module and include connector mapping for breadboard, schematic, and pcb views.
Expected response shape:
- Part behavior summary.
- Connector map table.
- SVG and .fzp mapping plan.
- Validation checklist status.
- Packaging and forum-share readiness.
When not to use it
- →When the goal is not to create or integrate a custom Fritzing part.
- →When the user does not have mechanical dimensions, pin maps, or interface behavior details.
Limitations
- →The skill requires existing datasheet information for part creation.
- →Validation steps are described but require user execution.
- →Sharing for review is a manual step to the Fritzing forum.
How it compares
This skill provides a structured workflow for creating Fritzing parts, reducing common errors by enforcing conventions and validation steps, unlike a manual process that might overlook consistency checks.
Compared to similar skills
fritzing-custom-component-workflow side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fritzing-custom-component-workflow (this skill) | 0 | 2mo | No flags | Intermediate |
| draw | 0 | 3mo | Review | Beginner |
| printable | 0 | 4mo | Review | Advanced |
| diagram-driven-execution | 0 | 1mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
draw
Anhvu1107
ALWAYS use this when the request matches Draw: Vector graphics and diagram creation, format conversion (ODG/SVG/PDF) with LibreOffice Draw.
printable
rohittp0
Use when the user wants to create, design, or build a 3D model for 3D printing using OpenSCAD. Triggers on mentions of 3D printing, OpenSCAD, STL export, printable parts, or physical object design.
diagram-driven-execution
sergio-sisternes-epam
>-
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
svg-precision
dkyazzentwatwa
Deterministic SVG generation, validation, and rendering. Use for icons, diagrams, charts, UI mockups, or technical drawings requiring structural correctness and cross-viewer compatibility.
blender-toolkit
Dev-GOM
Automate Blender tasks like creating 3D shapes, managing materials, and retargeting Mixamo animations with real-time control.