菜单
How to write GenVM spec pages (docs/website/src/spec). Use when adding or editing spec sections — brevity, linking constants/errors/terms instead of inlining them, spec vs impl-spec split, and how to verify the build.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/genlayerlabs/genvm-manager --skill spec命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Hunts for determinism violations and internal errors in a GenVM executor by writing throwaway probe contracts and running them across leader/validator/sync. Use when asked to fuzz the VM, look for nondeterminism, or turn a PR into a failing test.
GenVM commit message conventions. Use when writing a commit message, squashing/merging a PR, or amending history. Covers the `type(scope): summary <emoji>` format, the five types, the standard scope set, the gitmoji suffix, and mistakes to avoid (typos, vague "fix CI N").
Always read before writing, adding, or modifying Rust tests — where to put and how to run them.
正在显示 SKILL.md
| name | spec |
| description | How to write GenVM spec pages (docs/website/src/spec). Use when adding or editing spec sections — brevity, linking constants/errors/terms instead of inlining them, spec vs impl-spec split, and how to verify the build. |
The spec (docs/website/src/spec/) describes observable behavior — what a
contract or validator can detect. How this codebase achieves it goes to
impl-spec/. If a sentence starts describing internals (caches, native limits,
threads), either drop it or reduce it to one normative requirement on
implementations.
#. lists instead of prose walkthroughs; name the
actors precisely (caller/callee, leader/validator) and describe each
case once.docs/adr/).Never write a literal value or error string in spec text — link the anchor, so generated pages stay the single source of truth:
:ref:gvm-def-consts-value-- / `:ref:`gvm-def-const-<name> from spec/appendix/constants.rst
(generated from executor/codegen/data/public-abi.json),
internal-constants.rst (from internal-constants.json) or
constants-pending.rst (from public-abi-pending.json). Never edit these
.rst by hand — edit the JSON and regenerate
(genvm-tool.md). Constants a
contract cannot read go to the internal JSON, not-yet-stabilized ones to the
pending JSON.:ref:gvm-def-str-trie-value-vm-error-...`` — every "traps
with" / "rejected with" must link the exact vm_error entry.:term:sub-VM`` etc. on first use in a section.:doc: relative links instead of restating their content.Build the website (docs.md)
and check for undefined label warnings on your pages — a broken :ref: is a
silent dead link otherwise. Verify claims against the implementation before
writing them; every behavioral sentence should have a code location you can
point to (but do not link it to the specification).