Not in the top 1,000 by GitHub stars
cobbpeng/fpga-hardware-design-and-review-guide
FPGA hardware design guide based on real-world projects. Covers SystemVerilog, Vivado workflow, timing closure, CDC handling, and Xilinx 7 series device selection. Perfect for AI coding assistants and FPGA developers.
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
SKILL.md
Week of Nov 2, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → e838005aca0c
No earlier version was observed for comparison.
Heat
0.3- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
30-day change not yet available: not enough history.
Individual skills in this repository
How it works
fpga-hardware-design-and-review-guide
When your agent uses it
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 or data path designs, (3) optimizing for resource utilization and timing closure, (4) reviewing RTL code for hardware implementation, (5) debugging synthesis or implementation issues.
What it loads into context
Frontmatter
169 tokensAlways available to the agent
SKILL.md
1,892 tokensWhen the skill is activated
Reference documents
11,714 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core Design Philosophy
- Timing Closure Practical Techniques
- Resource Optimization Strategies
- Debugging and Verification Methods
- Reference Documentation
- Golden Rules
Files
LICENSEasset1,061 bytesPUBLISH_GUIDE.mddoc676 bytesREADME.mddoc4,664 bytesSKILL.mdcore8,156 bytesreferences/design-patterns.mddoc16,653 bytesreferences/device-selection.mddoc7,932 bytesreferences/troubleshooting.mddoc14,123 bytes
Read SKILL.md
# FPGA Hardware Design Guide
A practical FPGA hardware design guide based on real-world project experience.
## Core Design Philosophy
### 1. Pipeline Architecture First
When processing high-speed data streams (video, network packets), adopt multi-stage pipeline design:
- **Single-stage processing**: Combinational logic delay too large, prone to timing violations
- **Multi-stage pipeline**: Insert registers at each stage, distribute delay, increase clock frequency
- **Typical applications**: RGB-to-YUV conversion, image filtering, protocol parsing
**Real Case**: RGB-to-YUV converter with 5-stage pipelineView the complete source on GitHubSkills included
- fpga-hardware-design-and-review-guide
Repository facts
- License
- MIT
- Created
- Feb 5, 2026
- Last pushed
- Feb 6, 2026
- Forks
- 1
- Open issues
- 0
- Project activity
- Slowing
Before you install
Network or broad shellAutomated signals, not a guarantee
Checked Nov 7, 2026
- 1 broad permissionin 1 file: SKILL.md:1
- No dangerous shell commands
- 3 network referencesin 1 file: README.md:1
- No hidden or obfuscated text
- No instruction overrides
- No executable scripts
- No access to secrets
- No requests to vote in Hot
Show all 4 signals by file
README.md
- Network accessline 1
[](https://github.com/cobbpeng/fpga-hardware-design-and-review-guide/blob/main/LICENSE) - Network accessline 6
[](https://opensource.org/licenses/MIT) - Network accessline 70
npx skills add https://github.com/cobbpeng/fpga-hardware-design-and-review-guide --skill fpga-hardware-design-guide
SKILL.md
- Broad permissionsline 1
Read Write Edit Bash
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Signal confidence: 4 facts
- Network access in prose of documentationREADME.md:1Low confidence
- Network access in prose of documentationREADME.md:6Low confidence
- Network access in code of documentationREADME.md:70Low confidence
- Broad permissions in the frontmatter of the SKILL.mdSKILL.md:1High confidence
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Compatible | Standard SKILL.md SKILL.md | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.