FStarLang

Use the F* MCP server for interactive, incremental typechecking of F* and Pulse code

Verify F* and Pulse code with fstar.exe and interpret errors

Extract verified F*/Pulse code to C via KaRaMeL (.krml intermediate representation)

Structure a new F*/Pulse verification project with Makefile and directory layout

Systematic workflows for debugging F*/Pulse verification failures

Debug F* queries sent to Z3, diagnosing proof instability and performance issues

Build F*, Pulse, and KaRaMeL from source (fstar2 branch) for use in a verification project

Review F*/Pulse specifications for completeness, strength, and usability

Verify C code with PAL (Proof Annotated Language for C), which compiles annotated C into F*/Pulse. Use when verifying C code using PAL. This guide covers spec writing idioms as well as tips on how to progress stuck proofs.