Skip to content

hashgraph-online/awesome-codex-plugins / plugins/aklofas/kicad-happy/skills/kicad

Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules. Reviews designs for bugs, traces nets, cross-references schematic to PCB, extracts BOM data, checks DRC/ERC, DFM, power trees, and regulator circuits. Every finding carries a confidence label and evidence source with trust_summary rollup. Analyzes PDF schematics from dev boards, reference designs, eval kits, and datasheets. Supports KiCad 5–10. Use whenever the user mentions .kicad_sch, .kicad_pcb, .kicad_pro, PCB design review, schematic analysis, PDF schematics, reference designs, Gerber files, DRC/ERC, netlist issues, BOM extraction, signal tracing, power budget, DFM, or wants to understand, debug, compare, or review any hardware design. Also for "check my board", "review before fab", "what's wrong with my schematic", "is this ready to order", "check my power supply", "verify this circuit", OSHWA certification readiness, or any electronics/PCB design question.

FileKindSize
SKILL.mdskill md79.1 KB
references/config-reference.mdmarkdown19.1 KB
references/datasheet-verification.mdmarkdown16.5 KB
references/deep-review.mdmarkdown9.7 KB
references/design-intent.mdmarkdown5.6 KB
references/diff-analysis.mdmarkdown17.6 KB
references/file-formats.mdmarkdown15.1 KB
references/gerber-parsing.mdmarkdown33.5 KB
references/manual-gerber-parsing.mdmarkdown24.5 KB
references/manual-pcb-parsing.mdmarkdown17.2 KB
references/manual-schematic-parsing.mdmarkdown12.8 KB
references/net-tracing.mdmarkdown12.0 KB
references/oshwa-certification.mdmarkdown4.5 KB
references/output-schema.mdmarkdown33.4 KB
references/pcb-layout-analysis.mdmarkdown27.3 KB
references/pdf-schematic-extraction.mdmarkdown15.2 KB
references/report-generation.mdmarkdown56.3 KB
references/schematic-analysis.mdmarkdown63.9 KB
references/standards-compliance.mdmarkdown33.5 KB
references/supplementary-data-sources.mdmarkdown12.5 KB
references/what-if.mdmarkdown19.5 KB
review/README.mdmarkdown4.1 KB
review/fixtures/deep_review.example.jsonconfig1.2 KB
review/fixtures/design_context.example.jsonconfig388 B
review/fixtures/review_annotations.example.jsonconfig707 B
review/prompts/design_context.mdmarkdown4.9 KB
review/schemas/deep_review.schema.jsonconfig3.3 KB
review/schemas/design_context.schema.jsonconfig2.2 KB
review/schemas/review_annotations.schema.jsonconfig1.9 KB
review/scripts/_mini_jsonschema.pyscript6.6 KB
review/scripts/build_review_plan.pyscript2.3 KB
review/scripts/deep_review_gate.pyscript27.3 KB
review/scripts/merge_annotations.pyscript7.0 KB
review/scripts/validate_review.pyscript2.6 KB
scripts/.gitignoreother13 B
scripts/README.mdmarkdown23.4 KB
scripts/analysis_cache.pyscript42.1 KB
scripts/analyze_gerbers.pyscript90.9 KB
scripts/analyze_pcb.pyscript7.4 KB
scripts/analyze_schematic.pyscript6.7 KB
scripts/analyze_thermal.pyscript48.5 KB
scripts/analyzer_envelope.pyscript15.5 KB
scripts/capability_mode.pyscript10.2 KB
scripts/check_report_sections.pyscript10.6 KB
scripts/cross_analysis.pyscript69.4 KB
scripts/cross_verify.pyscript23.1 KB
scripts/design_intent.pyscript13.5 KB
scripts/detection_schema.pyscript26.0 KB
scripts/detector_helpers.pyscript15.2 KB
scripts/diff_analysis.pyscript23.5 KB
scripts/diff_engine.pyscript47.2 KB
scripts/domain_detectors.pyscript260.5 KB
scripts/envelopes/__init__.pyscript0 B
scripts/envelopes/cross_analysis.pyscript5.9 KB
scripts/envelopes/gerber.pyscript16.1 KB
scripts/envelopes/pcb.pyscript25.9 KB
scripts/envelopes/schematic.pyscript23.1 KB
scripts/envelopes/thermal.pyscript7.4 KB
scripts/export_issues.pyscript27.6 KB
scripts/fab_release_gate.pyscript29.8 KB
scripts/finding_schema.pyscript25.7 KB
scripts/gen_output_schema_md.pyscript9.2 KB
scripts/inputs_builder.pyscript4.0 KB
scripts/kicad_core/__init__.pyscript0 B
scripts/kicad_core/classify.pyscript32.5 KB
scripts/kicad_core/cli.pyscript4.2 KB
scripts/kicad_core/coords.pyscript2.0 KB
scripts/kicad_core/diagnostics.pyscript1.9 KB
scripts/kicad_core/executables.pyscript1.0 KB
scripts/kicad_core/fields.pyscript5.9 KB
scripts/kicad_core/fileio.pyscript5.4 KB
scripts/kicad_core/hotloop.pyscript3.1 KB
scripts/kicad_core/instances.pyscript5.7 KB
scripts/kicad_core/model.pyscript4.8 KB
scripts/kicad_core/netnames.pyscript19.1 KB
scripts/kicad_core/netquery.pyscript6.7 KB
scripts/kicad_core/pairing.pyscript1.9 KB
scripts/kicad_core/parts.pyscript28.9 KB
scripts/kicad_core/passives.pyscript10.0 KB
scripts/kicad_core/pdn.pyscript1011 B
scripts/kicad_core/project.pyscript43.2 KB
scripts/kicad_core/render.pyscript2.7 KB
scripts/kicad_core/sexp.pyscript12.6 KB
scripts/kicad_core/textvars.pyscript5.4 KB
scripts/kicad_core/token_cache.pyscript2.2 KB
scripts/kicad_core/values.pyscript14.1 KB
scripts/kicad_types.pyscript15.1 KB
scripts/lifecycle_audit.pyscript6.7 KB
scripts/lifecycle_engine.pyscript52.8 KB
scripts/lookup_detectors.pyscript29.9 KB
scripts/lookup_helpers.pyscript3.0 KB
scripts/methodology_gerbers.mdmarkdown23.1 KB
scripts/methodology_pcb.mdmarkdown22.2 KB
scripts/methodology_schematic.mdmarkdown43.1 KB
scripts/netlist_queries.pyscript4.2 KB
scripts/output_filters.pyscript16.8 KB
scripts/output_io.pyscript5.3 KB
scripts/pcb/__init__.pyscript0 B
scripts/pcb/assembly.pyscript58.3 KB
scripts/pcb/connectivity.pyscript27.7 KB
scripts/pcb/copper.pyscript61.0 KB
scripts/pcb/dfm.pyscript56.9 KB
scripts/pcb/geometry.pyscript59.5 KB
scripts/pcb/pipeline.pyscript30.3 KB
scripts/pcb/presentation.pyscript24.3 KB
scripts/pcb/reader.pyscript87.1 KB
scripts/pcb/routing.pyscript53.5 KB
scripts/project_config.pyscript23.1 KB
scripts/risk_summary.pyscript3.1 KB
scripts/run_id.pyscript1.7 KB
scripts/schema_codec.pyscript5.0 KB
scripts/schematic/__init__.pyscript0 B
scripts/schematic/audits.pyscript56.0 KB
scripts/schematic/bom_stats.pyscript6.1 KB
scripts/schematic/connectivity.pyscript62.9 KB
scripts/schematic/erc_pins.pyscript8.4 KB
scripts/schematic/hierarchy.pyscript21.5 KB
scripts/schematic/ic_analysis.pyscript21.4 KB
scripts/schematic/legacy_reader.pyscript49.4 KB
scripts/schematic/net_analysis.pyscript75.5 KB
scripts/schematic/pipeline.pyscript72.2 KB
scripts/schematic/presentation.pyscript20.9 KB
scripts/schematic/reader.pyscript64.7 KB
scripts/schematic/system_analyses.pyscript126.9 KB
scripts/signal_detectors.pyscript248.0 KB
scripts/summarize_findings.pyexecutablescript17.4 KB
scripts/validation_detectors.pyscript75.3 KB
scripts/what_if.pyscript68.4 KB

references/design-intent.md

View on GitHub
# Design Intent Interpretation Guide

When presenting schematic or PCB analysis results, check the `design_intent`
object in the analysis JSON to understand the design context and calibrate
your review accordingly.

## Reading Auto-Detected Intent

The `design_intent` object contains:

- `product_class`: "prototype" or "production"
- `ipc_class`: 1, 2, or 3
- `target_market`: "hobby", "consumer", "industrial", "medical", "automotive", "aerospace"
- `confidence`: 0.0-1.0 (how confident the auto-detection is)
- `detection_signals`: list of strings explaining what was detected
- `source`: per-field dict showing where each value came from ("config", "pcb_fab_notes", "schematic_title", "auto")

**When confidence < 0.5**, ask the user to confirm before applying professional-grade
criteria:

> "Based on [detection_signals], this appears to be a [target_market] [product_class]
> design. Should I apply [target_market]-grade review criteria, or is this a prototype /
> hobby project?"

**When confidence >= 0.5**, apply the detected intent silently but mention it in your
review summary: "Reviewing as a [target_market] [product_class] design (IPC Class [N])."

## LLM Refinement Signals

Beyond what the heuristics detect, look for these contextual patterns when reviewing
analysis output. If you spot them, adjust your review priorities accordingly -- you do
not need to re-run the analyzers.

### Application domain indicators
- Silkscreen text: "MEDICAL DEVICE", "FOR AUTOMOTIVE USE", "MIL-SPEC", "CLASS III"
- Regulatory markings: CE, FCC, UL, CSA logos or text references
- Safety agency file numbers in title blocks or fab notes

### Component-level indicators
- AEC-Q100/Q200 prefixes in MPNs -> automotive
- MIL-PRF, MIL-STD, QPL references -> aerospace/defense
- All components from same temp grade (-40 to +85 or wider) -> production-grade
- Conformal coating callouts -> harsh environment
- Hi-rel screening levels (Class B, Class S) -> space-grade

### Design pattern indicators
- Redundant power paths, OR-ing diodes -> high-reliability
- Voting circuits (2-of-3, TMR) -> safety-critical
- Watchdog timers with external reset -> production embedded
- Isolation barriers (optocouplers, isolated DC-DC) -> medical or industrial
- Board revision detection circuitry (GPIO strapping, ADC divider) -> production
- All MPNs populated, consistent manufacturer choices -> BOM-locked production

### BOM maturity indicators
- Every component has an MPN field -> production-ready
- Multiple components from same manufacturer family -> intentional sourcing
- Second-source alternates listed -> supply-chain-aware production
- Lifecycle status fields populated -> active management

## Market-Specific Review Priorities

Adjust what you emphasize based on `target_market`:

### hobby
- Focus on: basic correctness, learning opportunities, cost optimization
- De-emphasize: DFM details, documentation completeness, test coverage
- Tone: educational, suggest improvements as learning points

### consumer
- Focus on: cost optimization, ESD on external I/O, package consolidation, EMC
- Flag: missing ESD protection on user-accessible connectors
- De-emphasize: test point coverage, fab notes completeness

### industrial
- Focus on: temperature range adequacy, long-lifetime components, test coverage, EMC
- Flag: electrolytic caps in designs with >10yr expected lifetime
- Flag: components with commercial temp range (-10 to +70) in industrial application
- Require: test point coverage >= 90%

### medical
- Focus on: safety components, isolation barriers, IPC Class 3 DFM, redundancy
- Flag: missing isolation between patient-connected and mains-connected sections
- Flag: single points of failure in safety-critical paths
- Require: test point coverage >= 95%, all safety components identified
- Recommend: formal FMEA if not referenced

### automotive
- Focus on: AEC-Q qualification, wide temp range (-40 to +125), vibration-sensitive footprints, EMC
- Flag: non-AEC-Q components in critical paths
- Flag: stress-sensitive MLCC placement near board edges or flex points
- Require: test point coverage >= 95%

### aerospace
- Focus on: IPC Class 3 DFM, derating (50% voltage, 60% power), full traceability
- Flag: any single-source components without documented alternatives
- Flag: components without radiation tolerance data (if applicable)
- Require: test point coverage >= 98%, full lifecycle documentation

## Severity Adjustment Table

Adjust report severity (info → SUGGESTION, medium → WARNING, high or critical → CRITICAL) based on `product_class` and `target_market`:

| Finding | prototype/hobby | production/consumer | production/industrial+ |
|---------|----------------|--------------------|-----------------------|
| Missing MPN | info | medium | high |
| No test points | info | medium | high |
| Missing fab notes | info | medium | high |
| Mixed passive sizes | -- | info | medium |
| Single-source IC | -- | info | medium |
| No ESD on external I/O | medium | high | critical |
| No hardware version detect | -- | info | medium |
| Electrolytic in long-life design | -- | info | high |
| Commercial temp in industrial | -- | -- | high |
| Missing isolation (medical) | -- | -- | critical |

"--" means suppress or skip this finding entirely for this context.

## User Confirmation Prompt

When the auto-detected intent changes the review substantially (e.g., from hobby
defaults to medical Class 3), confirm with the user before the first detailed
analysis presentation. An inferred medical or aerospace market only suggests Class 3
in the detection signals; `ipc_class` stays at the detected or default class until
`design_intent.ipc_class` is set. After confirmation, apply consistently for the rest
of the session without re-asking.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall