Writing clean and consistent code is important for any hardware design. Zener HDL code has its own set of style rules that make designs easier to understand and maintain. These rules help you avoid common mistakes and keep your .zen files looking professional.
You will learn how to handle optional parts using DNP patterns instead of conditional instantiation. The guide also covers typed configs with physical units, voltage checks on power pins, and smart component naming. By following these idioms, your designs will be simpler and more reliable.
Whether you are writing new modules or reviewing existing ones, these style rules act like a checklist for quality. They help you minimize component count and use computation in named functions with datasheet references. This skill is useful for any engineer working with Zener HDL.
Global
mkdir -p ~/.claude/skills/idiomatic-zenerProject
mkdir -p .claude/skills/idiomatic-zenerSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective