Sexp Module
SkillFiles & storageGives your agent guidance on parsing and writing KiCad board files using the project's S-expression engine and Python bindings.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Sexp Module skill
About this capability
How the Zig S-expression engine and typed KiCad models work, how they are exposed to Python (pyzig_sexp), and the invariants around parsing, formatting, and freeing. Use when working with KiCad file parsing, S-expression generation, or layout sync.
What this skill tells your AI
The instructions your AI receives, as published by atopile/atopile in .claude/skills/sexp/SKILL.md and read by ahel’s review.
The sexp subsystem provides:
- a fast S-expression tokenizer/parser/pretty-printer in Zig, and
- typed Zig models for KiCad formats (PCB, footprint, netlist, symbol, schematic, fp_lib_table),
exposed to Python via the
pyzig_sexpextension module.
Source-of-truth docs and code:
src/faebryk/core/zig/README.md(high-level overview)src/faebryk/core/zig/src/sexp/*(tokenizer/AST/structure)src/faebryk/core/zig/src/python/sexp/sexp_py.zig(Python API + critical memory rules)
Quick Start
from pathlib import Path
from faebryk.libs.kicad.fileformats import kicad
pcb = kicad.loads(kicad.pcb.PcbFile, Path("board.kicad_pcb"))
_text = kicad.dumps(pcb)
Relevant Files
- Zig core:
src/faebryk/core/zig/src/sexp/tokenizer.zig(tokenization + line/column tracking)src/faebryk/core/zig/src/sexp/ast.zig(SExp tree + KiCad pretty formatting)src/faebryk/core/zig/src/sexp/structure.zig(decode/encode + error context)src/faebryk/core/zig/src/sexp/kicad/*(typed KiCad models)
- Python extension entrypoint:
src/faebryk/core/zig/src/python/sexp/init.zig(exportsPyInit_pyzig_sexp)src/faebryk/core/zig/src/python/sexp/sexp_py.zig(module + type binding generation)
- Generated Python stubs (what users “see”):
src/faebryk/core/zig/gen/sexp/*.pyi
- Convenience wrapper used throughout the codebase:
src/faebryk/libs/kicad/fileformats.py(namespaces modules + caching +loads/dumps)
Dependants (Call Sites)
src/faebryk/libs/kicad/fileformats.py(primary integration layer)- KiCad exporters and layout sync:
src/faebryk/exporters/pcb/kicad/*src/faebryk/exporters/pcb/layout/layout_sync.py
- KiCad plugin workflow:
src/atopile/kicad_plugin/*
How to Work With / Develop / Test
Core Concepts
- Two-level model:
- raw
SExpparsing/formatting (tokenizer.zig,ast.zig) - typed KiCad decoding/encoding (
structure.zig+sexp/kicad/*.zig)
- raw
- Python API shape: the extension exposes per-format modules (e.g.
pcb,netlist) with:- module-level
loads(data: str) -> File - module-level
dumps(file: File) -> str File.free(...)for releasing Zig-owned allocations
- module-level
- Convenience wrapper:
faebryk.libs.kicad.fileformats.kicadwraps these modules and provideskicad.loads(...)/kicad.dumps(...).
Development Workflow
- Modify Zig:
- parsing/formatting:
src/faebryk/core/zig/src/sexp/* - Python exposure:
src/faebryk/core/zig/src/python/sexp/sexp_py.zig
- parsing/formatting:
- Rebuild:
ato dev compile(importsfaebryk.core.zig)
- If you changed the API:
- verify stubs under
src/faebryk/core/zig/gen/sexp/*.pyiupdate accordingly - adjust
src/faebryk/libs/kicad/fileformats.pyif needed
- verify stubs under
Testing
- Best practical test is round-trip:
- load a known
.kicad_pcb/.kicad_sch, dump it, and ensure KiCad accepts it (formatting-sensitive).
- load a known
- Zig unit tests (where present):
zig test src/faebryk/core/zig/src/sexp/ast.zigzig test src/faebryk/core/zig/src/sexp/structure.zig
Best Practices
- Prefer
faebryk.libs.kicad.fileformats.kicadunless you explicitly need the raw module API. - Be mindful of shared-object caching in
kicad.loads(...): path-based loads are cached and returned by reference (mutations are shared).
Memory & Lifetime Invariants (critical)
The Python bindings duplicate the input S-expression string into a persistent allocator because parsed structs contain pointers into the input buffer.
Implications:
- Repeated
loads(...)of large files can grow memory if you never callfree(...)on the returned*File. - The convenience wrapper currently caches loaded objects by path; do not
free(...)cached objects unless you also invalidate the cache.
Signals
- GitHub stars
- 4k
- Forks
- 234
- Last commit
- Jun 2026
Advanced
- Catalog kind
- skill
- Gateway key
sexp- Source
- github.com/atopile/atopile