zener-language

zener-language

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

• pcb doc --package <package> shows the public API (types, io, config) of installed or registry packages. It returns type-level listings, not field-level details — for interface field names, check the stdlib reference above or read the source in .pcb/stdlib/.

• 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.

Weekly Installs498Repositorydiodeinc/pcbGitHub Stars212First SeenMar 17, 2026Security AuditsGen Agent Trust HubPassSocketPassSnykPassInstalled onclaude-code497gemini-cli53github-copilot53amp53cline53codex53