vero-source-verus

Translate Verus source code to Lean 4 with classification rules and type mappings.

2|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/sunblaze-ucb/vero --skill vero-source-verus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vero-source-verus
Source: https://github.com/sunblaze-ucb/vero/tree/main/.claude/skills/vero-source-verus
Command: npx skills add https://github.com/sunblaze-ucb/vero --skill vero-source-verus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill translates Verus source code to Lean 4, providing specific classification rules, type mappings, and patterns for the ratified curation paradigm.

Core Features & Use Cases

  • Verus to Lean 4 Translation: Converts Verus source code into Lean 4, maintaining specific rules and mappings.
  • Classification Rules: Offers classification rules for Verus source code items (spec/proof/exec fn modes).
  • Type Mappings: Provides mappings between Verus and Lean 4 types (Seq/Map/Set vs List/AssocList).
  • Patterns: Supplies patterns for mapping Verus constructs into the Lean 4 bundle paradigm (Impl/ + Spec/ + Bundle + Harness).
  • Use Case: It can be used in conjunction with other skills like vero-discover, vero-plan, vero-translate, and vero-verus-pitfalls to create a complete translation pipeline for Verus code.

Quick Start

Use the vero-source-verus skill to translate the Verus source code in the 'BankLedger-source-verus' directory to Lean 4.

Frequently Asked Questions about vero-source-verus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate Verus source code to Lean 4?

You can translate Verus source code to Lean 4 by applying specific classification rules and type mappings that convert Verus constructs into Lean 4 implementations and specifications, following the ratified curation paradigm.

What type mappings are used when converting Verus code to Lean 4?

Verus to Lean 4 translation uses specific type mappings, such as converting Verus Seq, Map, and Set types into Lean 4 List and AssocList. It also maps constructs into the Lean 4 bundle paradigm including Impl, Spec, Bundle, and Harness.

How are Verus spec, proof, and exec functions classified in Lean 4 translation?

Verus source code items are classified into spec, proof, and exec function modes using specific rules. These classification rules determine how each item maps into the Lean 4 bundle paradigm structures.

Can I use this Verus to Lean 4 translation in a complete curation pipeline?

Yes, Verus to Lean 4 translation is intended for curation pipelines. It works in conjunction with other skills like vero-discover, vero-plan, vero-translate, and vero-verus-pitfalls to create a complete translation pipeline.

What patterns are applied when mapping Verus constructs to the Lean 4 bundle paradigm?

Mapping Verus constructs to the Lean 4 bundle paradigm uses specific patterns that structure the translated code into Impl, Spec, Bundle, and Harness components. This ensures the translated Lean 4 code aligns with the ratified curation paradigm.