avrOS-debug

Use when working with temporary files or evaluating scratchpads. Instructs AI agents on where to write test code, scratchpads, or temporary debug logs.

Use when working with avrOSdb debugging. This handles VS Code extension or GDB debugging, such as RSP trace logs logic, debugging connection issues over RSP, UPDI, or TCP. Use when changing application debugging logic inside avrOSdb main.c or gdb_rsp.c or investigating lockups or target side state.

Use when working with this project's specification, requirements, design, tests, or traceability. This project is managed by TraceR — doc/Project.xml is the SINGLE SOURCE OF TRUTH for design, requirements, and verification. USE FOR: reading, editing, creating, generating, updating, or regenerating any spec document — SDD (Software Design Document), HLRs (High-Level Requirements), LLRs (Low-Level Requirements), STP (Software Test Plan), Traceability matrix, or PVD (Product Vision Document); any change to doc/Project.xml or doc/PVD.md; adding, removing, or editing requirements (HLRs or LLRs); adding tests that trace or link to requirements; generating doc/SDD.md, doc/HLRs.md, doc/LLRs.md, doc/STP.md, or doc/Traceability.md; checking, fixing, or understanding test coverage; tracing or linking a requirement to a test; finding untested or uncovered requirements; explaining why a requirement or test is missing from a document; linting or validating the project spec. DO NOT USE FOR: routine source-code changes that