Agent skill · software engineering · juxt
allium
Give your AI agents something more useful than a prompt. Velocity through clarity.
Why this skill is useful
Adds executable scripts for generating integration tests and driving the development loop autonomously, which are not standard practices in existing tools.
What it needs
Requires distill, elicit, propagate, tend, weed installed locally. About 9k tokens when loaded. Last updated 2026-07-22. 443 stars on the source repository.
What this skill does
Allium Allium is a formal language for capturing software behaviour at the domain level. It sits between informal feature descriptions and implementation, providing a precise way to specify what software does without prescribing how it's built. The name comes from the botanical family containing onions and shallots, continuing a tradition in behaviour specification tooling established by Cucumber and Gherkin. Key principles: Describes observable behaviour, not implementation Captures domain logic that matters at the behavioural level Generates integration and end-to-end tests (not unit tests) Forces ambiguities into the open before implementation Implementation-agnostic: the same spec could be implemented in any language Allium does NOT specify programming language or framework choices, database schemas or storage mechanisms, API designs or UI layouts, or internal algorithms (unless they are domain-level concerns). Routing table Task Tool When ------ ------ ------ Writing or reading .allium files this skill You need language syntax and structure Building a spec through conversation elicit skill User describes a feature or behaviour they want to build Extracting a spec from existing code distill skill User has implementation code and wants a spec from it Modifying an existing spec tend skill User wants targeted changes to .allium files Checking spec-to-code alignment weed skill User wants to find or fix divergences between spec and implementation Generating tests from a spec propagate skill User wants to generate tests, PBT properties or state machine tests from a specification Attesting a loop's convergence witness skill User wants to independently confirm a run's convergence claim from ground truth — tests really pass, no generated test was weakened, no blocking question was silently parked Driving the whole loop to convergence this skill (see driving the loop) User wants to build or reconcile a feature end to end — /allium <goal> runs the gather→act→verify→repeat …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills juxt/allium--86000a