vyges loom — CLI reference

Generated from vyges loom --help — this page is the tool’s own output, verbatim.

vyges-loom 0.1.53 (2a55b6c)

The shared design-data foundation — the "loom" the engines weave on. Parses the
standard formats once into a shared in-memory design database. Common, design-wide
commands live here; tool-specific verbs (timing, power, extraction, …) belong to
the engines (built on the vyges_loom library).

USAGE:
  vyges loom <command> [files...] [options]

COMMANDS:
  inspect <files...>   parse files into the design DB and summarize
  check   <files...>   parse-validate files; non-zero exit on any parse error
  fst <file.fst> ...   query an FST waveform: --info, --list, transitions, --sample_at
  fst-write <in> -o <out.fst>   VCD -> FST, or a window/signal subset of an FST
  fst-to-vcd <in.fst> -o <out.vcd> --start T --end T <signals...>   bounded export

  ⛔ Never convert an FST to VCD to inspect it: the VCD can fill the disk and an agent's
     context. Query the FST in place (vyges loom fst <file> --help).
  version              print version
  help                 print this help

FILE TYPES (by extension):
  .v / .sv   netlist       .json  netlist (Yosys write_json)
  .lib       liberty       .sdc   constraints
  .spef      parasitics    .lef/.tlef  tech-LEF   .def  DEF

OPTIONS:
  --json        machine-readable output (inspect)
  -q, --quiet   fewer diagnostics (repeatable)
  -v, --verbose more diagnostics (repeatable)
  -h, --help    this help
  -V, --version version

Report a bug:      https://github.com/vyges/community/issues/new?labels=bug
Request a feature: https://github.com/vyges/community/issues/new?labels=enhancement
© 2026 Vyges. All Rights Reserved.  https://vyges.com

Contract

Generated from vyges loom --describe.

loom

shared design-data foundation — parse netlist / Liberty / SDC / SPEF / LEF / DEF into the design DB; query FST waveforms in place (fst: –info, –list, a –start/–end window, –limit, –sample_at). Never convert an FST to VCD to inspect it: the VCD can exhaust the disk and an agent’s context; fst-to-vcd is bounded to a window and a signal list.

Maturity: structured

Assertion: none; this operation establishes no engineering claim

Provenance limitations

• Reports what the named files contain; it does not verify that they describe the same design, nor that they are the files a flow actually consumed.