← Browse

@majiayu000/systemverilog

B

SystemVerilog development guidelines for FPGA and ASIC design covering modular design, verification, and timing optimization.

skillclaude

Install

agr install @majiayu000/systemverilog --target claude

Writes 2 files into .claude/skills/, pinned to git-dd10cf75.

  • .claude/skills/systemverilog/SKILL.md
  • .claude/skills/systemverilog/metadata.json

Document


name: systemverilog description: SystemVerilog development guidelines for FPGA and ASIC design covering modular design, verification, and timing optimization.

SystemVerilog Development

You are an expert in SystemVerilog for FPGA and ASIC design, verification, and hardware optimization.

Modular Design & Code Organization

  • Structure designs into small, reusable modules to enhance readability and testability
  • Begin with a top-level module and decompose into sub-modules
  • Use clear interface blocks for module connections
  • Maintain consistent coding style and naming conventions

Synchronous Design Principles

  • Prioritize single clock domains for simpler timing analysis
  • Implement proper clock domain crossing (CDC) handling for multi-clock designs
  • Prefer synchronous over asynchronous reset to ensure predictable behavior
  • Avoid combinational loops and latches

Timing Closure & Constraints

  • Establish XDC (Xilinx Design Constraints) files early
  • Review Static Timing Analysis reports regularly
  • Use timing reports to identify critical path bottlenecks
  • Address violations through pipelining or logic optimization
  • Deploy pipelining in high-frequency designs to reduce critical path loads

Resource Utilization & Optimization

  • Write efficient code for LUT/FF/BRAM usage
  • Use reg [] for RAM inference
  • Minimize unnecessary register usage
  • Leverage built-in IP cores (AXI interfaces, DSP blocks, memory controllers)
  • Select appropriate optimization priorities (area vs. speed)

Power Optimization

  • Implement clock gating for dynamic power reduction
  • Enable power-aware synthesis for low-power applications
  • Minimize switching activity in non-critical paths

Verification & Debugging

Testbenches

  • Develop comprehensive testbenches covering typical and edge cases
  • Use assert statements for property checking
  • Implement self-checking testbenches

Simulation

  • Run behavioral and post-synthesis simulations
  • Use Integrated Logic Analyzer (ILA) for real-time debugging
  • Apply assertion-based verification to catch protocol violations

Advanced Techniques

Clock Domain Crossing

  • Apply synchronizers or FIFOs for safe CDC implementation
  • Use proper handshaking protocols
  • Verify CDC paths thoroughly

Interface Optimization

  • Optimize AXI interfaces for high-throughput with proper burst sizing
  • Implement efficient handshaking protocols
  • Balance latency and throughput

Pipelining

  • Implement fine-tuned pipeline stages for performance-critical modules
  • Balance pipeline depth with latency requirements
  • Use retiming for optimization

Repository README

Describes majiayu000/claude-skill-registry-data as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.

Claude Skill Registry (Data)

This repo contains the archived skill contents (the heavy, browsable skill files).

Canonical layout

  • Category folders at repo root (e.g. development/, documents/, data/, ...)
  • Each skill lives under a category: <category>/<skill>/SKILL.md + <category>/<skill>/metadata.json
  • Case conflicts are resolved with {name}-{owner}-{repo} suffixes (fallback: -{short-hash}).

Archive status

  • Live badges above are sourced from claude-skill-registry-core stats.json.
  • Counts in this README are intentionally dynamic, not hardcoded.
  • If the badges look stale, refresh the core build/index pipeline rather than editing numbers here.

Where the index + site live

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-dd10cf7562c12026-07-31