featherweight-vip

Structure a UVM testbench (the tests/uvm/ tree) around a fwvip-<proto> VIP and/or a fw-hdl class model — the env package(s), scenario/test package, HDL/HVL tops, and the dv-flow flow.yaml. Enforces the project convention that every UVM/fw-hdl class lives in its own .svh file, `include`d by a thin package .sv (no `ifndef/`define guards). Use when asked to create, scaffold, refactor, or add classes to a UVM testbench for a Featherweight design.

Create a new fwvip-<proto> Verification IP (the methodology layer) on top of an existing fw-proto-<proto> transactor kit — a UVM agent set (per-role agents, configs, drivers, sequences, optional register adapter + runtime-config object) and a Python/cocotb front-end, with simulation tests and a per-VIP usage skill. Use when asked to build, scaffold, or stand up a Featherweight VIP / UVM+cocotb agent set for a protocol whose transactor kit (fw-proto-<proto>) already exists.

Connect and drive the fwvip-wb Wishbone Verification IP — bind its initiator / target / monitor agents into a UVM env (register macros + config DB), write stimulus/responder sequences, run the reg-model front door, and/or drive the cocotb front-end. Use when integrating fwvip-wb into a testbench or generating stimulus for it.