Seb works best when it knows your hardware. Drop supporting documents into your project or ask Seb to fetch them, and it will use them as context for code generation and debugging.Documentation Index
Fetch the complete documentation index at: https://docs.rootaccess.ai/llms.txt
Use this file to discover all available pages before exploring further.
Supported context
Place files in your project root ordocuments/ folder:
- Schematics — KiCad (
.sch,.kicad_sch), Altium (.schdoc). Ask Seb to parse them into markdown for use in future messages. - Datasheets — Drop them in manually or ask Seb to fetch from the registry (e.g. “Get the BMP280 datasheet”).
- Requirements docs — PRDs, specs, or compliance requirements your firmware needs to meet.
- BOMs — Bill of materials for component-level context.
- Other design docs — Block diagrams, pin maps, interface specs, or anything Seb should know about your hardware.
Plan mode
Use/plan before a message to have Seb propose an approach without making changes.
- “Plan out a migration from STM32F4 to NXP LPC55”
- “Help me plan adding FreeRTOS to my bare-metal project”
SEB.md
Seb creates and maintains aSEB.md file in your project root with software and hardware context it discovers. You can edit this file to add project-specific notes, constraints, or preferences that Seb should know about.
