Templating

Bodies are rendered with Liquid — text-native, no HTML escaping.

Variables

Variables are filled at call time, in this precedence (high → low):

Stdin fills {{ input }}. If the template doesn't reference it, the piped text is appended to the end instead of dropped. --file=PATH is an alternative source for {{ input }}.

echo "log line" | yori run triage --tone=blunt
yori run triage --tone=blunt --file=bug.log
yori run summarize --notes=@release-notes.md

Partials

Share a block across prompts with {% include %}:

{% include 'house-style' %}     {# loads store/partials/house-style.md #}

Logic

Liquid conditionals and loops work:

{% if examples %}Examples:
{% for e in examples %}- {{ e }}
{% endfor %}{% endif %}

Inheritance

Template inheritance (slots) — a base defines overridable regions; a child extends it and fills them.

# base.md
You are an assistant.
{% slot "guidelines" %}Be concise.{% endslot %}

Task: {{ input }}

# verbose.md
---
name: verbose
extends: base
---
{% fill "guidelines" %}Be verbose and cite your sources.{% endfill %}

Rendering verbose pours the fill into the base's slot; unfilled slots fall back to their default. Inheritance chains and is cycle-checked.

Inspecting composition

Two commands trace the composition graph:

yori deps verbose          # what an artifact composes from (extends + includes)
yori affected house-style  # which artifacts include/extend a partial (blast radius)

Forgiving by design

Undefined variables render blank and missing values fall back to frontmatter defaults — a half-filled prompt never hard-fails mid-pipeline.