Use when learning or applying the TLA+ ecosystem end-to-end: selecting VS Code, Toolbox, or CLI; choosing PlusCal vs raw TLA+; writing specs above the code level; structuring properties and cfg files; running SANY, TLC, Apalache, or TLAPS; debugging…
Build mock-free integration and E2E tests that hit real databases, real APIs, and real services with structured logging. Use when: replacing mocked tests with real-DB tests, transaction rollback isolation, test data factories, structured JSON-line test…
Compose evidence-backed pages (lessons, technical explainers, run reviews, sales letters, dashboards, feedback surfaces, document collections) as single-file HTML in the lev.now shell. By default, write a content-specific GenUI page, inspect it in light and…
Automate the user's logged-in Chromium browser: read pages, fill forms, scrape data, operate tabs, test a UI, or debug a website. Requires the bsk CLI and browser extension.
Use when guiding decision interviews that produce a design artifact in .lev/pm/designs before proposal or implementation planning.
Use when compiling captured or designed intent into a Lev plan (human runbook, migration, architecture plan, multi-slice roadmap), deepening or reviewing a plan, changing plan state under `.lev/pm/plans/`, reviewing slice readiness, rendering a slice map, or…
Use when you need an evidence-first provenance report from `cass`, repo docs, `.lev`, `~/.agents/diagrams`, `qmd`, or Grep/Glob tools.
Use when routing tracked work through lifecycle lanes, resolving workstream context, or deciding which lifecycle skill owns the next entity transition.