Skip to main content
Turn schematic files into markdown so Seb has hardware context for debugging and code generation. Supported formats: KiCad (.sch, .kicad_sch) and Altium (.schdoc). Seb extracts components, nets, power rails, signal paths, pin assignments, and sheet hierarchy—then uses that in later answers and code.

​
What Seb extracts

Component info · Net connections · Power rails · Signal paths · Pin assignments · Sheet hierarchy

​
Process schematics

Put schematic files in your project (root, schematics/, or hardware/). Then ask Seb to process them: “Process the schematic file hardware/main.kicad_sch” · “Parse hardware/board.schdoc” · “Parse all schematic files in the schematics folder”. Seb reads the file, extracts data, and saves markdown in your project.

​
Use the context

Debugging: “Why isn’t my I2C sensor working?” · “What components are connected to this pin?” · “Is my power supply configuration correct?” Code gen: “Generate code to read from the sensor on pin PA5” · “Write initialization code for my hardware” · “Create a driver for the component connected to SPI1” Verification: “Check if my schematic matches my code” · “Verify my pin assignments are correct” Re-process after design changes and use clear component/net names. Output markdown is used by Seb in future chats.