zener-language

Original：🇺🇸 English

Translated

Canonical Zener HDL semantics, package rules, manifests, and high-value stdlib APIs. Use before non-trivial `.zen` creation, editing, refactoring, or review when the task touches `Module()`, `io()`, `config()`, imports, `pcb.toml`, `pcb.sum`, stdlib interfaces or units, or unfamiliar package APIs. Read this before editing instead of guessing.

12installs

Sourcediodeinc/pcb

Added on2026-03-18

NPX Install

npx skill4agent add diodeinc/pcb zener-language

SKILL.md Content

View Translation Comparison →

Zener Language

Use this skill as the semantics companion to

idiomatic-zener

for non-trivial

.zen

work.

Workflow

Start from nearby workspace code. Prefer the local package's patterns before generic examples.
Open only the relevant reference file:
- ```
references/language.md
```
  for modules, nets/interfaces, components,
```
io()
```
  ,
```
config()
```
  , utilities, and tool-managed metadata
- ```
references/packages.md
```
  for imports, workspace layout, manifests, dependencies, and
```
pcb.sum
```
- ```
references/stdlib.md
```
  for prelude, interfaces, units, checks, utils, properties, and generics
- ```
references/examples.md
```
  for example snippets
For installed package or registry APIs, run
```
pcb doc --package <package>
```
instead of guessing. This skill is the canonical owner of that workflow.
For broader toolchain semantics, consult
```
~/.pcb/docs/spec.md
```
and
```
~/.pcb/docs/packages.md
```
.
Check exact semantics before editing when the code touches unfamiliar syntax, manifests, imports, stdlib APIs, or package interfaces.
Never invent syntax, stdlib modules, interfaces, fields, or package APIs.

Notes

Use this with
```
idiomatic-zener
```
for non-trivial
```
.zen
```
creation, editing, refactoring, or review.
Use
```
reference-design
```
for vendor and reference-circuit translation work.
Use
```
component-search
```
when the problem is finding or importing a part rather than understanding the language.