What problem does it solve? Turning a hardware behavior contract into readable, validated Vitis HLS C/C++ kernels requires coordinating pragmas, interfaces, testbenches, configuration, and tool reports, which is error-prone when done manually. ## Core Features & Use Cases - Contract-driven generation: Create readable HLS C/C++ kernels, interface-aware testbenches, and structured specs from a confirmed HLS JSON contract covering pipeline behavior, streamability, and interface profiles. - Review and annotation: Inspect HLS sources, pragmas, and reports, or perform comment-only rewrites with Chinese semantic comments guarded by AST/token fingerprint comparison against a baseline. - Static and tool-based validation: Run static readiness checks locally and execute Vitis csim/cosim or remote board acceptance when a Vitis toolchain or approved remote server is available. - Use Case: Provide a confirmed contract for an AXI4-Stream FIR filter, then generate the kernel and testbench, add Chinese semantic comments, and validate through Vitis HLS cosim on a remote server. ## Quick Start Ask your AI assistant to use Readable HLS Generator to create a readable Vitis HLS kernel from your confirmed behavior contract, for example a vector-scale kernel with an AXI4 interface.