Stats
Actions
Tags
From claude-for-hardware
Drive the measure-don't-guess FPGA fit and timing loop on a design
How this command is triggered — by the user, by Claude, or both
Slash command
/claude-for-hardware:fpga-fit module target part or what's failing to fit/routeThe summary Claude sees in its command listing — used to decide when to auto-load this command
The user wants to fit an RTL design onto an FPGA, hit timing, or fix a route that will not converge. Context they gave: $ARGUMENTS Invoke the `fpga-synthesis-fit` skill, and `rtl-area-timing` if the bottleneck is a structure (a wide multiply, a barrel shifter, a compute-everything-and-select datapath). Then drive this loop, one measured step at a time: 1. Measure with the right number. Read post-pack nextpnr `TRELLIS_COMB` (or the equivalent post-place utilization), never the pre-pack synth LUT count. For timing, read the critical-path report and name the specific primitive on it. 2. If i...
The user wants to fit an RTL design onto an FPGA, hit timing, or fix a route that will not converge. Context they gave: $ARGUMENTS
Invoke the fpga-synthesis-fit skill, and rtl-area-timing if the bottleneck is a structure (a wide multiply, a barrel shifter, a compute-everything-and-select datapath). Then drive this loop, one measured step at a time:
TRELLIS_COMB (or the equivalent post-place utilization), never the pre-pack synth LUT count. For timing, read the critical-path report and name the specific primitive on it.rtl-area-timing (internal multiply pipeline, dead-arm removal, resource sharing, fixed-slice mux), then re-measure post-pack. Stop optimizing a resource once it leaves the critical path.Report each step's measurement and the one change you made, not a batch of speculative edits. Do not claim a win without a post-pack number.
npx claudepluginhub midstall/claude-for-hardware --plugin claude-for-hardware