Propagate
by juxt7f7f008e0c6bNo license506 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 11 days ago
Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.
- 7f7f008e0c6bCurrentcommit 7f7f008Published Oct 8, 2026
Source and attribution
Source:juxt/alliuminskills/propagateat commit7f7f008
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from juxt/allium
Weed
juxt
Compares Allium specification files against implementation code, reports divergences, and helps resolve them.
Allium
juxt
Formal language for specifying software behaviour in .allium files, with a loop for spec, tests and code convergence.
Elicit
juxt
Guides a structured conversation to elicit requirements and build an Allium specification.
Tend
juxt
Writes, edits and validates Allium specification files, translating requirements into well-formed specs.
More in Software Development
Playground
anthropics
Builds self-contained interactive HTML playgrounds with controls, live preview, and copyable prompt output.
M5 Onboard
anthropics
Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.
Cardputer Buddy
anthropics
Guides iterating on a Cardputer-Adv MicroPython app bundle: adding apps, pushing files over USB-serial, tailing logs, and running REPL commands.
Web Design Guidelines
vercel-labs
Reviews UI code against Web Interface Guidelines fetched from a remote source and reports findings as file:line entries.
Vercel React Native Skills
vercel-labs
React Native and Expo best-practice rules covering list performance, animation, navigation, UI patterns, state, and monorepo setup.
Vercel React Best Practices
vercel-labs
Vercel's React and Next.js performance guidelines, organized as 70 rules for writing, reviewing, and refactoring code.