1. Habit
  2. Skills
  3. Allium skill
juxt · 4K installs

Allium skill
Runs by itself, you give a goal.

Spec, tests and code all agree.

Install the Allium skill and make it a habit: follow https://gethabit.dev/skills/juxt/allium.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

4K installs518 starsMIT licenceSource on GitHub ↗

Allium

by juxt · 4K installs

The skill

The allium skill is a formal language and loop for specifying software behaviour: it captures intent in .allium files, generates integration and end-to-end tests, and drives spec, tests and code to agreement.

Only when you ask.

The habit

Spec, tests and code all agree.

↻ Runs by itselfyou give a goal

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

you give a goal. Runs in Claude Code routine.

  • ↻ you give a goal
  • /allium <goal>

02

It checks its work

tests, weed, witness. If a check fails, it tries again.

  • ✓the .allium file passes CLI validation on every write
  • ✓generated tests pass
  • ✓weed reports no spec-to-code divergence
  • ✓no open question remains unresolved

03

It remembers

allium spec. The next run reads it first: the current .allium spec, open questions and the convergence ledger.

spec.allium

One run, step by step.
Then it stops.

Stop ruleStops when tests pass, weed finds no divergence, no open question remains and witness attests; otherwise after 2 loop retries.

  1. 01

    Gather context

    Your agent builds or extracts the spec with elicit from intent or distill from existing code.

  2. 02

    Generate tests

    It runs propagate to make integration and end-to-end tests, confirming new tests fail first in spec-first work.

  3. 03

    Implement

    It writes the application code, ordinary coding the spec and tests do not replace.

  4. 04

    Verify

    It runs the tests, then weed to find spec-to-code drift, then the CLI structural checks.

  5. 05

    Repeat

    It edits the spec with tend and re-propagates until the three artefacts agree.

  6. 06

    Witness

    An independent witness pass attests the convergence against ground truth, never weakening a test to pass.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Allium skill helps.

Use it when

  • ✓ specifying a feature's behaviour precisely
  • ✓ generating tests from a spec
  • ✓ reconciling spec and code drift

Skip it when

  • – you want unit tests only
  • – the task is a quick throwaway script

Questions

Allium skill, answered.

Can I run one step only?

Yes. A clear single task routes to one skill, elicit, distill, propagate, tend, weed or witness; a goal drives the whole loop.

What if the spec is ambiguous?

It escalates the genuine ambiguity to you rather than guessing, and the witness enforces that at the gate.

How do I install the Allium skill?

Copy the prompt at the top into your agent. It installs the skill from juxt/allium and sets up the habit. Or run npx skills add juxt/allium --skill allium.

Is the Allium skill free?

Yes. It is published under MIT. Habit is free too.

Allium. Now as a habit.

Install the Allium skill and make it a habit: follow https://gethabit.dev/skills/juxt/allium.md

  • Free
  • No account
  • Undo in one line

All juxt skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by juxt, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.