doc

To audit hardware documentation, this skill reads config scripts, board headers, routing definitions, and manufacturing files to collect source-of-truth values. It then compares these against website documentation to report and automatically fix every mismatch.

Syncing project documentation after a BOM update involves running this skill to collect authoritative manufacturing data. It detects outdated entries across documentation pages, corrects discrepancies, and verifies the website documentation builds successfully.

Yes, you can automatically fix outdated website documentation by auditing it against current hardware configuration files. The skill corrects mismatches across schematic, component, manufacturing, and PCB pages, then validates the documentation build.

Auditing schematics and PCB layouts requires reading config scripts, board header files, routing definitions, and manufacturing data. These authoritative source-of-truth files provide the baseline values needed to detect and correct discrepancies in the documentation.

You should run a documentation audit whenever you modify the PCB layout, update the BOM, or change hardware configurations. This ensures website documentation accurately reflects the new hardware specifications and prevents manufacturing errors.

To regenerate schematics before auditing, the skill uses the authoritative config files as the baseline. It then collects source-of-truth values from these regenerated schematics to compare against website documentation and fix any discrepancies.