- Home
- Skills
- Agents & Orchestration
- FPGA 07/13 · Timing Claude — Timing Closure
Works with the AI Agents you already use
FPGA 07/13 · Timing Claude — Timing Closure
Automates FPGA timing closure through precise setup/hold diagnosis, CDC synchronization, and targeted pipelining.
$10
FPGA 07/13 · Timing Claude — Timing Closure
Example session with this skill installed
WNS is -0.450ns after routing in Vivado. The worst path is in the DSP cluster fan-in. Review the report and suggest the exact register insertion point to close timing.
- Read your context and instructions
- Compiled the fpga 07 13
Violation classified as setup. WNS: -0.450ns, TNS: -12.4ns. The bottleneck is the combinational logic between data_reg[23] and the DSP48 input. Insert one pipeline register at the output of the first logic stage. Updated WNS: +0.050ns. No hold violations introduced.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
FPGAs often suffer from sporadic board failures or missed performance targets because timing violations are ignored or misdiagnosed. Developers frequently waste days manually inserting pipeline registers across the entire design instead of targeting the specific paths causing negative slack.
What it does
- Analyzes post-route timing reports to classify violations as setup (frequency-dependent) or hold (functional defects).
- Executes a report-driven pipelining loop, identifying the worst path and inserting a single register at the transition point to meet targets without bloating area.
- Identifies and constrains Clock Domain Crossing (CDC) paths using two-flip-flop synchronizers or handshakes with appropriate asynchronous markings.
- Audits constraint files for missing clock definitions and applies false-path or multicycle markings to prevent artificial analysis bottlenecks.
- Verifies system-level bottlenecks to ensure optimization effort isn't wasted on a core that is gated by a slow host interface.
Frameworks & tools
AMD Vivado, Intel Quartus, Xilinx Design Constraints (XDC), Synopsys Design Constraints (SDC), and Static Timing Analysis (STA) tools.
Why this beats prompting it yourself
General-purpose LLMs often confuse setup and hold remediation strategies, leading to useless clock adjustments for hold violations. This skill enforces a rigorous diagnosis-first workflow, ensuring every CDC path is correctly synchronized and every pipeline stage is quantitatively justified by WNS/TNS improvements.
Use cases
- Resolving negative WNS/WHS after implementation in high-frequency Vivado designs.
- Safely crossing clock domains without risking metastability or false timing alarms.
- Optimizing throughput in compute cores by balancing pipeline depth against fill latency.
- Cleaning up "phantom" timing violations by correctly marking false paths in legacy code.
Known limitations
Requires an existing routed design checkpoint and post-route timing reports to function. It does not perform physical floorplanning or placement-based optimization.
Requires post-route timing reports and design checkpoints. Does not perform manual floorplanning or physical placement optimizations.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
No special permissions declared or detected