What problem does it solve?
Writing a correct HOLOLINK_def.svh configuration header for the NVIDIA Holoscan Sensor Bridge (HSB) FPGA IP requires knowing dozens of macros, their legal values, and cross-macro constraints. This Skill removes hand-editing errors by generating, validating, comparing, and explaining def files with bundled Python tooling and authoritative macro references.
Core Features & Use Cases
- Guided Generation: Build a HOLOLINK_def.svh from confirmed board requirements via a one-question-per-turn workflow, or directly from a YAML/JSON profile; the generator validates before writing output.
- Rule-Based Validation: Lint an existing def file against a catalog of stable rule IDs (HD-Exxx/Wxxx/Ixxx) with JSON or text output, including HD-W3xx silent-fallback footgun warnings.
- Semantic Comparison: Diff two def files while ignoring whitespace, comments, and equivalent syntactic forms.
- Use Case: An FPGA engineer bringing up a new HSB board answers questions about sensor interfaces, host width, clocks, and peripherals, then receives a validated HOLOLINK_def.svh targeting IP rev 16'h2604.
Quick Start
Ask your agent to use hsb-ip-def to generate a HOLOLINK_def.svh for your new HSB board, or to validate your existing def file and explain any warnings.