tend

Translate user requests into well-formed Allium specifications.

5|4|Updated Mar 10, 2026

Search Tags:#specification #validation #clarification #refactor #syntax-check #tend #allium

Ready to run

npx skills add https://github.com/editor-code-assistant/eca-plugins --skill tend-editor-code-assistant

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tend
Source: https://github.com/editor-code-assistant/eca-plugins/tree/main/plugins/allium/skills/tend
Command: npx skills add https://github.com/editor-code-assistant/eca-plugins --skill tend-editor-code-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tend the Allium garden. You are responsible for the health and integrity of allium specification files. You are senior, opinionated and precise. When a request is vague, you push back and ask probing questions rather than guessing.

Core Features & Use Cases

Translate user requests into well-formed Allium specifications (entities, variants, rules, triggers, surfaces, and contracts).
Maintain health and integrity of allium files, warning on vagueness and asking clarifying questions.
Validate syntax with the allium CLI when available and guide safe refactors.
Cross-file renames/refactors and fix syntax issues in allium files.

Quick Start

Provide a high-level request describing the desired spec change, and I will translate it into a well-formed Allium specification.

Frequently Asked Questions about tend

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

FAQPage Schema

How do I validate Allium specification syntax before refactoring entities and rules?▼

Validate Allium specification syntax by running the allium CLI to check entity, rule, and trigger files. This ensures structural integrity before cross-file refactors, catching syntax errors proactively during migration or editing.

What is the best way to translate vague requirements into well-formed Allium specifications?▼

Translating vague requirements into Allium specifications requires probing clarifying questions rather than guessing. A senior, opinionated approach pushes back on ambiguous requests to ensure entities, variants, surfaces, and contracts are defined precisely.

How do I safely rename and refactor Allium spec files across multiple contracts and triggers?▼

Cross-file renames and refactors in Allium specifications should be guided by syntax validation and language reference checks. This ensures that changes to entities, variants, and rules maintain health and integrity across all dependent contract files.

When do I need to migrate Allium specifications and what integrity checks apply?▼

Allium specification migration is needed when creating, editing, or refactoring entities, rules, triggers, surfaces, and contracts. Integrity checks involve syntax validation with the allium CLI and clarifying questions for vague requirements.

Does the allium CLI support syntax validation for newly created entity and surface specifications?▼

The allium CLI supports syntax validation for newly created entity and surface specifications. Running CLI validation checks ensures that generated spec files are well-formed and maintain overall garden health before integration.