@zxkmm/kicad-footprint-generator
BGenerates production-ready KiCad footprint scripts (.py) from component datasheets (images, PDFs, or text). Specializes in precise coordinate math and official KiCad API compliance.
Install
agr install @zxkmm/kicad-footprint-generator --target claudeWrites 6 files into .claude/skills/, pinned to git-f2fad572.
- .claude/skills/kicad-footprint-generator/LICENSE
- .claude/skills/kicad-footprint-generator/README.md
- .claude/skills/kicad-footprint-generator/SKILL.md
- .claude/skills/kicad-footprint-generator/image-1.png
- .claude/skills/kicad-footprint-generator/image-2.png
- .claude/skills/kicad-footprint-generator/image.png
Document
name: kicad-footprint-generator description: > Generates production-ready KiCad footprint scripts (.py) from component datasheets (images, PDFs, or text). Specializes in precise coordinate math and official KiCad API compliance.
KiCad Footprint Generator
๐ฏ Primary Goal
Transform component physical specifications into a fully functional, hardcoded KiCad Footprint Wizard script. The output must be a ready-to-run Python script that automates the generation of a .kicad_mod file within the KiCad environment.
๐ Strategic Workflow
1. Specification Research
Extract precise dimensions from provided inputs (images, PDFs, or descriptions). Focus on:
- Pin/Pad geometry (pitch, width, length).
- Package body dimensions and Pin 1 orientation.
- Thermal pad (EPad) requirements and courtyard clearances. Refer to Analysis Guide.
2. Template Selection & Mapping
Identify the package type (SOP, QFP, BGA, QFN, etc.) and map it to the corresponding template in templates/.
Refer to Templates Reference.
3. Implementation (Hardcoded Logic)
Generate a standalone Python script where all dimensions are hardcoded.
- Rule: The user should not have to configure parameters; the script should generate the specific footprint immediately upon execution.
- API Compliance: Strictly follow the conventions in
docs/API_REFERENCE.md.
4. Local Verification
Before delivering the script, perform the mandatory verification steps:
- Syntax Check:
python3 <script>.py - Lifecycle Test: Run
BuildFootprint()via CLI. Refer to the full Verification Workflow.
5. Deployment & Delivery
- Deploy the script to the detected KiCad scripting directory.
- Provide clear run instructions to the user. Refer to Environment & Deployment.
๐ Supporting Documentation
- Detailed Guide - Deep dive into the generation process.
- API & Templates - KiCad Python API and blueprint mapping.
- Environment Setup - Path detection and installation.
- Verification - Mandatory testing procedures.
- Examples - Reference implementations.
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicensecopyleft/unknown โ index-and-link only
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged โ not that the artifact is safe.
Versions
git-f2fad5725b5c2026-07-31