skills.rest
juxt
juxtOFFICIAL
Explore all skills by this author →
Website𝕏@juxtproGitHub

tend

Edit and validate Allium behavioral specification files against CLI tooling.

10|6|Updated Feb 8, 2026
Search Tags:#system design#spec maintenance#rule definition#allium#spec validation#spec refactoring#behavioral specification
One-click install
npx skills add https://github.com/juxt/claude-plugins --skill tend-juxt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tend
Source: https://github.com/juxt/claude-plugins/tree/main/plugins/allium/skills/tend
Command: npx skills add https://github.com/juxt/claude-plugins --skill tend-juxt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing Allium behavioral specification files requires deep knowledge of the language syntax, validation rules, and domain modeling best practices. This Skill eliminates the risk of introducing invalid specs, broken transition graphs, or ambiguous requirements by guiding you through compliant, well-structured spec edits.

Core Features & Use Cases

  • Spec Modification: Add, update, or refactor entities, rules, triggers, surfaces, and contracts in existing Allium files.
  • Error Correction: Fix syntax and validation errors in .allium files to ensure they pass allium CLI checks.
  • Requirement Translation: Convert vague or implementation-focused requirements into clear, behavior-focused Allium specifications, pushing back on ambiguous requests.
  • Use Case: If you need to add a new hiring workflow rule to an existing Allium spec for your HR system, this Skill ensures the rule is syntactically correct, doesn't create unreachable transitions, and aligns with your existing domain model.

Quick Start

Use the tend skill to update the order processing Allium spec to add a new rule that triggers a payment hold when an order total exceeds $10,000.

Frequently Asked Questions about tend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new rule to an existing Allium behavioral specification?▼

To add a new rule to an Allium behavioral specification, you define the rule syntax within your domain model and validate the changes against the allium CLI to ensure no unreachable state transitions are created.

What is the best way to fix syntax and validation errors in .allium spec files?▼

Fixing syntax and validation errors in .allium spec files requires validating the behavioral specification against the Allium language reference to identify and correct structural issues before finalizing edits.

How do I translate vague system requirements into compliant Allium specs?▼

Translating vague requirements into compliant Allium specs involves restructuring implementation-focused requests into clear, behavior-focused specifications while pushing back on ambiguous domain modeling requests.

Can I refactor entities and triggers across multiple Allium spec files?▼

You can refactor entities, triggers, surfaces, and contracts across multiple Allium spec files by performing cross-file refactoring operations that maintain the integrity of your observable system behavior.

Why does my Allium spec have unreachable state transitions after editing?▼

Unreachable state transitions in an Allium spec occur when edits introduce invalid rules or missing required data values, which must be flagged and resolved using allium CLI tooling validation before finalizing.

Do I need the allium CLI to migrate specs to a new Allium language version?▼

Migrating specs to a new Allium language version requires validating the updated behavioral specification files against the allium CLI tooling or the Allium language reference to ensure full compliance.

Related Skills

Explore More Software Engineering Skills→
scottopellscottopell
1

distill

Extract domain entities, states, transitions, and boundaries into an Allium-style spec.

Community
Advanced
juxtjuxt
10

weed

Resolve divergences between Allium behavioral specification files and implementation code.

Official
Advanced
micfremicfre
3

bmild-arch

Document and validate backend architecture decisions with ADRs and API contracts.

Community
Advanced
scottopellscottopell
1

tend

Translate vague Allium requirements into precise .allium specifications.

Community
Advanced