fpga skills

19 tagged fpga, measured the same way as everything else here.

Browse within: accept-language 8cos 8flutter 8gin 8eda 7vivado 5xilinx 5

Eriemon/verilog-generator

Skill Codex

Use when creating, writing, reviewing, annotating, repairing, refactoring, or validating readable Verilog RTL, including synthesizable Verilog-2001 .v files, existing-RTL analysis, semantic comment annotation, testbench scaffold planning, ASIC-quality review, local or remote Vivado/xsim validation, evidence-backed…

not rated 321 +4 2mo ago A 77 tokens original Apache-2.0

vivado-cdc-audit

02

mapleleavessssssss-wq/vivado-mcp

Skill Claude CodeCodex

A Vivado workflow for reviewing clock-domain crossing, or CDC, reports in FPGA designs. CDC checks whether signals moving between unrelated clock rates are synchronized and transferred safely.

not rated 162 +3 1mo ago A 58 tokens original Apache-2.0

vivado-debug

03

adeleempurpled290/FPGA-Agent-skills

Skill Claude CodeCodex

Use this skill when the user needs help with Vivado in-system debugging, hardware programming, or debug core configuration. This includes ILA (Integrated Logic Analyzer) configuration and trigger strategies, VIO (Virtual I/O) usage for signal monitoring and control, JTAG-to-AXI Master for AXI transaction generation…

not rated 37 1mo ago A 183 tokens GPL-2.0

Eriemon/hls-generator

Skill Codex

Use when you need to create, write, review, annotate, or validate readable HLS, Vitis HLS, high-level synthesis, or HLS debug workflows.

not rated 32 2mo ago A 40 tokens

cobbpeng/fpga-hardware-design-and-review-guide

Skill Claude Code

Comprehensive FPGA hardware design guide based on real-world project experience. Covers pipeline architecture, timing optimization, SystemVerilog coding patterns, CDC handling, and practical debugging techniques. Use this skill when: (1) designing FPGA modules with timing constraints, (2) implementing video processing…

not rated 20 8mo ago A 99 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: