@sous-io/sous 0.1.0

package/shared-prompts/skills/sous-skills/about-agent-skills/examples/about-something.md

@@ -0,0 +1,45 @@
+# Example: Topical Skill (`about-*`)
+
+```markdown
+---
+name: about-deployments
+description: >
+  YOU MUST load this skill when working with deployments, deployment config, or when
+  the user mentions "deploy". Covers what a deployment is, how they work in this
+  project, and where deployment configuration lives.
+user-invocable: false
+---
+
+# Abstract
+
+This "topical skill" provides information about a specific concept: deployments.
+
+## About Deployments
+
+A deployment is the process of publishing a built application to a target environment.
+In this project, deployments are managed via the `deploy/` directory and driven by
+scripts in `deploy/scripts/`.
+
+Deployments target three environments: `staging`, `production`, and `preview`. Each
+has its own configuration file under `deploy/config/`.
+
+## Reference Files
+
+- [references/environments.md](references/environments.md) — per-environment config
+  options, required env vars, and access requirements
+- [references/rollback.md](references/rollback.md) — rollback procedures and known
+  failure modes
+
+# Other Skills
+
+## Action Skills
+
+Action skills for deployments will have "deploy" in their name. Find the appropriate
+action skill for what you want to do. If no appropriate action skill exists, ask the
+user whether one should be created before continuing.
+
+## Related Skills
+
+You MUST load `about-infrastructure` for network and hosting context relevant to
+deployments.
+```

package/shared-prompts/skills/sous-skills/about-agent-skills/examples/do-something.md

@@ -0,0 +1,33 @@
+# Example: Action Skill (Command)
+
+```markdown
+---
+name: deploy
+description: >
+  YOU MUST use this skill when deploying the application. Do not use for rollbacks —
+  those follow a different process.
+disable-model-invocation: true
+---
+
+# Abstract
+
+This "action skill" (command) performs a specific operation: deploying the application
+to a target environment.
+
+A deployment publishes the built application to a hosting environment. This project
+supports three environments: `staging`, `production`, and `preview`.
+
+## Deploying
+
+The agent performing this work MUST load `about-deployments`. Then run the deploy
+script for the target environment:
+
+```bash
+bash ${CLAUDE_SKILL_DIR}/../../deploy/scripts/deploy.sh $ARGUMENTS
+```
+
+# Related Skills
+
+You MUST load `about-deployments` for environment config, required env vars, and
+access requirements.
+```

package/shared-prompts/skills/sous-skills/about-agent-skills/references/advanced-patterns.md

@@ -0,0 +1,87 @@
+# Advanced Patterns
+
+## Dynamic Context Injection
+
+The `` !`command` `` syntax runs a shell command before skill content is sent to Claude.
+The output replaces the placeholder — Claude receives the rendered result, not the command.
+
+```yaml
+---
+name: pr-summary
+context: fork
+agent: Explore
+allowed-tools: Bash(gh *)
+---
+
+## Pull request context
+- Diff: !`gh pr diff`
+- Comments: !`gh pr view --comments`
+- Changed files: !`gh pr diff --name-only`
+
+## Task
+Summarize this pull request...
+```
+
+Execution order: each `` !`command` `` runs first, output is inserted, then Claude sees
+the fully-rendered prompt. This is preprocessing, not something Claude executes.
+
+## Subagent Execution (`context: fork`)
+
+Add `context: fork` to run the skill in an isolated subagent. The skill content becomes
+the subagent's prompt. It does not have access to the current conversation history.
+
+```yaml
+---
+name: deep-research
+context: fork
+agent: Explore
+---
+
+Research $ARGUMENTS thoroughly:
+1. Find relevant files using Glob and Grep
+2. Read and analyze the code
+3. Summarize findings with specific file references
+```
+
+The `agent` field selects the subagent configuration:
+- `Explore` — read-only tools optimized for codebase exploration
+- `Plan` — planning-oriented execution
+- `general-purpose` — default; full tool access
+- Any custom agent defined in `.claude/agents/`
+
+Results are summarized and returned to the main conversation.
+
+> Only use `context: fork` for skills with explicit task instructions. Skills containing
+> only reference guidelines (e.g. "use these conventions") will return without meaningful
+> output — the subagent has no actionable task.
+
+## Restricting Tool Access (`allowed-tools`)
+
+Limit which tools Claude can use when a skill is active. Granted without per-use approval.
+
+```yaml
+---
+name: safe-reader
+allowed-tools: Read, Grep, Glob
+---
+```
+
+Syntax supports wildcards: `Bash(gh *)` permits only `gh` subcommands via Bash.
+
+## Supporting Files
+
+Keep `SKILL.md` under ~500 lines. Move detailed reference material to separate files
+and reference them from the skill body so Claude knows when to load them.
+
+```
+my-skill/
+├── SKILL.md             # Overview, navigation, fundamental instructions
+├── references/          # Deep-dive docs — loaded when needed, not always
+│   └── api-spec.md
+├── examples/            # Example outputs showing expected format
+└── scripts/             # Executable scripts; referenced via $CLAUDE_SKILL_DIR
+    └── validate.sh
+```
+
+Scripts are executed, not read into context. Reference them in `SKILL.md` with the
+full path using `${CLAUDE_SKILL_DIR}/scripts/validate.sh`.

package/shared-prompts/skills/sous-skills/about-agent-skills/references/commands.md

@@ -0,0 +1,46 @@
+# Commands Reference
+
+A **command** is a user-invocable action skill that represents an intentional,
+user-initiated workflow. The user explicitly triggers it with `/skill-name`.
+
+## Key Properties
+
+- Set `disable-model-invocation: true`. This removes the skill from Claude's context
+  entirely — it loads only when the user invokes it. See `frontmatter.md` for the
+  invocation matrix.
+- Because the model never sees the description, write it for humans, not for Claude.
+  It appears in the `/` autocomplete menu. Plain, informative language is appropriate —
+  strong trigger language ("YOU MUST") is unnecessary and out of place.
+- Commands do not require an `# Abstract` section. Include one only if useful context
+  is genuinely needed. Headings are optional in general — use them only if the content
+  is complex enough to warrant structure.
+
+## Arguments
+
+Commands often accept arguments (e.g. `/deploy staging`). When they do:
+
+1. Use `$ARGUMENTS` (or `$0`, `$1`, etc.) in the skill body where the arguments should
+   be substituted. See `substitutions.md` for full syntax.
+2. Add an `argument-hint` field to frontmatter — it appears in autocomplete next to the
+   command name.
+
+```yaml
+---
+name: deploy
+description: Deploy the application to a target environment.
+argument-hint: "[environment]"
+disable-model-invocation: true
+---
+
+Deploy to the $0 environment.
+```
+
+If `$ARGUMENTS` is not present in the body but arguments are passed, Claude Code
+appends them automatically as `ARGUMENTS: <value>`.
+
+## When to Omit `disable-model-invocation`
+
+Not every command needs `disable-model-invocation: true`. If it makes sense for Claude
+to invoke the command autonomously on the user's behalf (e.g. a lightweight helper with
+no side effects), omit the flag. Use judgement — the defining question is whether the
+action should require explicit user intent.

package/shared-prompts/skills/sous-skills/about-agent-skills/references/frontmatter.md

@@ -0,0 +1,25 @@
+# Frontmatter Reference
+
+All fields are optional, though `description` is strongly recommended.
+`name` defaults to the directory name if omitted.
+
+| Field                      | Description |
+|:---------------------------|:------------|
+| `name`                     | Slash-command name. Lowercase letters, numbers, hyphens (max 64 chars). Defaults to directory name. |
+| `description`              | When to invoke this skill. Used by Claude for auto-invocation. Falls back to first paragraph of content. |
+| `argument-hint`            | Hint shown in autocomplete. Example: `[issue-number]` or `[filename] [format]`. |
+| `disable-model-invocation` | `true` — user-only invocation. Description removed from Claude's context entirely. Use for side-effect workflows. Default: `false`. |
+| `user-invocable`           | `false` — hides from `/` menu; only Claude can invoke. Use for background knowledge. Default: `true`. |
+| `allowed-tools`            | Tools Claude may use without per-use approval when this skill is active. Example: `Read, Grep, Glob`. |
+| `model`                    | Model to use when this skill is active. |
+| `context`                  | `fork` — run the skill in an isolated subagent. Skill content becomes the subagent prompt. |
+| `agent`                    | Subagent type when `context: fork` is set. Options: `Explore`, `Plan`, `general-purpose`, or any custom agent in `.claude/agents/`. Defaults to `general-purpose`. |
+| `hooks`                    | Hooks scoped to this skill's lifecycle. |
+
+## Invocation Matrix
+
+| Frontmatter                      | User can invoke | Claude can invoke | When loaded into context                                      |
+|:---------------------------------|:----------------|:------------------|:--------------------------------------------------------------|
+| (default)                        | Yes             | Yes               | Description always in context; full skill loads on invocation |
+| `disable-model-invocation: true` | Yes             | No                | Not in context at all; loads only when user invokes           |
+| `user-invocable: false`          | No              | Yes               | Description always in context; full skill loads on invocation |

package/shared-prompts/skills/sous-skills/about-agent-skills/references/substitutions.md

@@ -0,0 +1,50 @@
+# String Substitutions
+
+Skills support dynamic substitution in the skill body content.
+
+## Argument Substitutions
+
+| Variable        | Description |
+|:----------------|:------------|
+| `$ARGUMENTS`    | All arguments passed when invoking the skill. If not present in content, arguments are appended as `ARGUMENTS: <value>`. |
+| `$ARGUMENTS[N]` | A specific argument by 0-based index. `$ARGUMENTS[0]` is the first argument. |
+| `$N`            | Shorthand for `$ARGUMENTS[N]`. `$0` = first argument, `$1` = second, etc. |
+
+### Example
+
+```yaml
+---
+name: migrate-component
+description: Migrate a component from one framework to another
+---
+
+Migrate the $0 component from $1 to $2.
+Preserve all existing behavior and tests.
+```
+
+Running `/migrate-component SearchBar React Vue` substitutes `SearchBar`, `React`, `Vue`.
+
+If arguments are passed but `$ARGUMENTS` (or `$N`) is not present in the content,
+Claude Code appends `ARGUMENTS: <value>` to the end of the skill content automatically.
+
+## Session and Path Substitutions
+
+| Variable               | Description |
+|:-----------------------|:------------|
+| `${CLAUDE_SESSION_ID}` | The current session ID. Useful for logging or creating session-specific files. |
+| `${CLAUDE_SKILL_DIR}`  | Absolute path to the skill's directory. Use to reference bundled scripts or files regardless of current working directory. |
+
+### Example using `$CLAUDE_SKILL_DIR`
+
+```yaml
+---
+name: run-check
+allowed-tools: Bash
+---
+
+Run the validation script:
+
+```bash
+bash ${CLAUDE_SKILL_DIR}/scripts/validate.sh
+```
+```

package/shared-prompts/skills/sous-skills/about-liquid-templates/SKILL.tpl.md

@@ -0,0 +1,268 @@
+---
+name: about-liquid-templates
+description: >
+  YOU MUST load this skill when working with .tpl. files, deciding whether a file
+  needs .tpl. naming, writing LiquidJS syntax in templates, or using custom tags or
+  filters. Covers the .tpl. convention, LiquidJS syntax, custom tags, custom filters,
+  and a live dump of all variables available in this project.
+user-invocable: false
+---
+
+# About Liquid Templates
+
+Files in this project with `.tpl.` in their filename are processed through LiquidJS
+at compile time. The `.tpl.` segment is stripped from the output filename.
+
+## The `.tpl.` Convention
+
+| Source file          | Processed? | Output file       |
+|----------------------|------------|-------------------|
+| `SKILL.md`           | No         | `SKILL.md`        |
+| `SKILL.tpl.md`       | Yes        | `SKILL.md`        |
+| `config.tpl.sh`      | Yes        | `config.sh`       |
+| `README.md`          | No         | `README.md`       |
+
+**`SKILL.md` for any skill compiled by sous must always be `SKILL.tpl.md`** — the
+required `## Source for this Skill` footer cannot be rendered without LiquidJS
+processing. See `about-agent-skills` for the full rule.
+
+For all other files, use `.tpl.` only when the file genuinely needs variable
+substitution, partials, or conditionals. Static files are copied verbatim — faster
+and safer.
+
+## Two Syntaxes — Do Not Mix
+
+Sous uses two different variable syntaxes at two different stages. Using the wrong one in
+the wrong place silently produces the literal text instead of a value.
+
+| Syntax | Where it belongs | Resolved by |
+|--------|------------------|-------------|
+| {% raw %}`${varName}`{% endraw %} | `_vars` blocks and target paths in a sous **config** file | sous, during config load |
+| {% raw %}`{{ varName }}`{% endraw %} | the body of a `.tpl.` **template** file | LiquidJS, at render time |
+
+The one crossover is `@`-include paths, which accept {% raw %}`${var}`{% endraw %}
+substitution because the include processor runs before LiquidJS (see below).
+
+## Syntax
+
+Output a variable:
+
+{% raw %}
+```
+{{ varName }}
+```
+{% endraw %}
+
+Conditionals:
+
+{% raw %}
+```
+{% if tool == "claude" %}
+  ...
+{% elsif tool == "codex" %}
+  ...
+{% else %}
+  ...
+{% endif %}
+```
+{% endraw %}
+
+Loops:
+
+{% raw %}
+```
+{% for item in items %}{{ item }}{% endfor %}
+```
+{% endraw %}
+
+Assign a variable:
+
+{% raw %}
+```
+{% assign name = "value" %}
+```
+{% endraw %}
+
+Include another file at render time (path **relative to the template file's directory**):
+
+{% raw %}
+```
+{% render "path/to/partial.md" %}
+```
+{% endraw %}
+
+`render` resolves paths relative to the template file. For files outside that tree, use
+a path **alias** (`@~sous-shared/...`, `@~project/...`, or a user-defined alias) or a
+`@`-prefixed `${var}` path — the same alias resolution as `@include` (see below) works in
+`render` too.
+
+To prevent template sequences from being processed in a code example, wrap the block in
+`raw` / `endraw` tag blocks. These blocks cannot be nested: the first `endraw`
+encountered closes the block, so a nested pair leaks its remainder into the output. Use
+one pair per code example rather than one large wrapper.
+
+## `@include` for Cross-Directory Files
+
+The `@path` syntax is processed by the build system before LiquidJS runs. It includes
+a file's content inline. Write `@` immediately followed by a `.md` path on its own line
+with nothing else on that line.
+
+`@include` works in both `.tpl.` and plain `.md` files. Included content is subject to
+LiquidJS rendering if the parent file is a `.tpl.` (so a Liquid tag inside the included
+file runs in the parent's render pass).
+
+The engine sets both `strictVariables: false` and `strictFilters: false`. An undefined
+variable renders as an empty string, and an **unknown filter silently no-ops**, passing
+its input through unchanged. Neither mistake raises an error, so a typo in a variable or
+filter name shows up only as missing or unfiltered output.
+
+### Gotcha: `@include` fires inside fenced code blocks
+
+The `@include` processor runs on the raw file content *before* LiquidJS and has no
+markdown awareness whatsoever — it matches any line that is nothing but an `@`-prefixed
+`.md` path. A fenced code block does not protect it: an `@path.md` line inside triple
+backticks is still executed and replaced with the file's content. There is no escape
+syntax. To show an `@`-path as an example, put something else on the line (indent it,
+prefix it with a word, or wrap it in backticks inline).
+
+### Path forms
+
+A `@`-path may be any of:
+
+- **Relative** to the including file: `@sections/intro.md` (traverse up with `../`).
+- **Variable-substituted**: `@${sousRootPath}/shared-prompts/x.md` — `${var}` is
+  substituted before resolving; if the result is absolute it is used directly.
+- **Aliased**: `@<alias>/rest.md`, where the first segment names a registered alias.
+
+### Path aliases
+
+The first path segment, up to the first `/` or `:` (both separators work — `@a/b.md`
+≡ `@a:b.md`), is matched against the alias registry. Built-in aliases are reserved and
+always begin with `~`:
+
+- `@~sous-shared/...` → the Sous CLI's `shared-prompts` directory (skills, memories,
+  `_partials`, etc.). Example: `@~sous-shared/_partials/resume-task.md`.
+- `@~project/...` → the consuming project's root.
+
+Projects register their own aliases in settings via an `_aliases` block (root and/or
+project level); names may **not** start with `~` (reserved). An alias value is a string
+or an array of strings (each may use `${var}`):
+
+```
+_aliases: { myDocs: "${projectRoot}/docs", shared: ["${a}", "${b}"] }
+```
+
+### Resolution order
+
+For each `@`-path, candidates are tried in order and the **first that exists on disk
+wins**; if none exist, the build errors listing every path tried:
+
+1. Each base of the matched alias, in order (project `_aliases` are tried before root,
+   before built-in bases of the same name).
+2. The path resolved **relative to the including file** — using the *full* path
+   including the alias segment. So an alias miss can fall through to a real relative
+   directory of the same name, letting an alias **augment** a local directory.
+
+## Custom Tags
+
+**`showVars`** — dumps all variables currently in scope as a fenced JSON block.
+Useful during development to see exactly what variables are available at a given point
+in a template. Remove before finalizing.
+
+**`getFiles`** — globs files under a root directory and assigns the resulting array to a
+template variable. It renders nothing; present the results yourself with a `for` loop.
+Each entry has `path`, `dir`, `relPath`, and `name`. `include`/`exclude` take
+comma-separated glob patterns matched relative to `root`, and attribute values may be
+quoted strings or scope variables. The optional `import="<exportName>"` dynamically
+imports each file and attaches that export to the entry (files that fail to import, or
+that lack the export, are dropped) — this is how a manifest of scripts reads its own
+metadata:
+
+{% raw %}
+```
+{% getFiles tasks root=scriptsDir include="*.mjs" import="meta" %}
+{% for t in tasks %}
+### {{ t.meta.name }}
+- Script: `{{ t.path }}`
+{% endfor %}
+```
+{% endraw %}
+
+**`listFiles`** — the convenience counterpart to `getFiles`: it globs and renders a
+markdown bullet list of file names inline, with no loop needed. Add `relative="true"` to
+render paths relative to the root instead of bare file names:
+
+{% raw %}
+```
+{% listFiles root=scriptsDir include="*.mjs" %}
+```
+{% endraw %}
+
+**`exportScalarVarsJs`** — emits every in-scope scalar variable (string, finite number,
+boolean) as an ES module default export, keys sorted. Objects, arrays, `null` and
+non-finite numbers are skipped. Use it to compile a settings module that runtime code
+imports, rather than re-deriving project configuration:
+
+{% raw %}
+```
+{% exportScalarVarsJs %}
+```
+{% endraw %}
+
+## Custom Filters
+
+**`bulletList`** — converts an array variable to a markdown bullet list:
+
+{% raw %}
+```
+{{ tags | bulletList }}
+```
+{% endraw %}
+
+Output (if `tags` is `["a", "b", "c"]`):
+```
+- a
+- b
+- c
+```
+
+Given a non-array value, `bulletList` returns it as a plain string with no bullet.
+
+## Authoring Guidelines
+
+Templates (`.tpl.*` files) must be **maximally reusable**. A well-written template
+can be copied between projects or shared across teams without edits — only the
+project's variables change.
+
+**Rules:**
+
+1. **Never hard-code values that could differ between projects.** If a value comes
+   from project configuration (board IDs, project keys, sprint IDs, URLs, user info),
+   use a variable. When no suitable variable exists, add one to the project's sous
+   config file (the file that defines the project's `_vars`).
+2. **Guard project-specific blocks with conditionals.** If a section only applies when
+   a variable is set, wrap it in {% raw %}`{% if varName %} ... {% endif %}`{% endraw %} so the
+   block disappears cleanly for projects that don't define it.
+3. **Prefer derived variables over raw values.** Example: `ticketPrefix` is derived
+   from `jiraProjectKey` — templates use `ticketPrefix` so they stay correct if the
+   key changes.
+4. **Test portability mentally.** Before finalizing a template, ask: "If I compiled
+   this for a different project with different settings, would the output still make
+   sense?" If not, parameterize the varying part.
+
+## Reference Files
+
+- [liquid-filters.md](references/liquid-filters.md) — complete standard LiquidJS filter catalogue (string, array, number, date, default)
+
+## Available Variables
+
+The following variables are in scope at compile time in this project:
+
+{% showVars %}
+
+## Source for this Skill
+
+This skill was pulled from the `sous` project's "shared skills" library. It was compiled from a template and
+the output file should not be edited directly.
+
+- Source Path: {{ sousTemplatePath }}

package/shared-prompts/skills/sous-skills/about-liquid-templates/references/liquid-filters.md

@@ -0,0 +1,82 @@
+# LiquidJS Built-in Filters
+
+Standard filters available in all `.tpl.` files. Chained with `|`.
+
+## String
+
+| Filter | Description | Example |
+|:-------|:------------|:--------|
+| `upcase` | Uppercase | `{{ "hello" | upcase }}` → `HELLO` |
+| `downcase` | Lowercase | `{{ "HELLO" | downcase }}` → `hello` |
+| `capitalize` | First char uppercase | `{{ "hello world" | capitalize }}` → `Hello world` |
+| `strip` | Remove leading/trailing whitespace | `{{ "  hi  " | strip }}` → `hi` |
+| `lstrip` | Remove leading whitespace | |
+| `rstrip` | Remove trailing whitespace | |
+| `strip_newlines` | Remove all newlines | |
+| `strip_html` | Remove HTML tags | |
+| `escape` | HTML-escape `<`, `>`, `&`, `"` | |
+| `url_encode` | Percent-encode a URL string | |
+| `url_decode` | Decode a percent-encoded string | |
+| `append` | Append a string | `{{ "foo" | append: "bar" }}` → `foobar` |
+| `prepend` | Prepend a string | `{{ "bar" | prepend: "foo" }}` → `foobar` |
+| `replace` | Replace all occurrences | `{{ "aabbcc" | replace: "b", "x" }}` → `aaxxcc` |
+| `replace_first` | Replace first occurrence | |
+| `remove` | Remove all occurrences | `{{ "aabbcc" | remove: "b" }}` → `aacc` |
+| `remove_first` | Remove first occurrence | |
+| `truncate` | Truncate to N chars (adds `...`) | `{{ "hello world" | truncate: 7 }}` → `hell...` |
+| `truncatewords` | Truncate to N words | `{{ "one two three" | truncatewords: 2 }}` → `one two...` |
+| `split` | Split string into array | `{{ "a,b,c" | split: "," }}` → `["a","b","c"]` |
+| `newline_to_br` | Replace `\n` with `<br>` | |
+
+## Array
+
+| Filter | Description | Example |
+|:-------|:------------|:--------|
+| `join` | Join array with separator | `{{ arr | join: ", " }}` |
+| `first` | First element | `{{ arr | first }}` |
+| `last` | Last element | `{{ arr | last }}` |
+| `reverse` | Reverse order | |
+| `sort` | Sort ascending (case-sensitive) | |
+| `sort_natural` | Sort ascending (case-insensitive) | |
+| `uniq` | Remove duplicates | |
+| `compact` | Remove nil/falsy values | |
+| `map` | Extract a property from each object | `{{ items | map: "name" }}` |
+| `where` | Filter objects by property value | `{{ items | where: "active", true }}` |
+| `concat` | Concatenate two arrays | `{{ arr1 | concat: arr2 }}` |
+| `slice` | Extract a sub-array | `{{ arr | slice: 1, 3 }}` |
+| `size` | Length of string or array | `{{ arr | size }}` |
+| `push` | Append element to array | |
+| `pop` | Remove last element | |
+| `shift` | Remove first element | |
+| `unshift` | Prepend element to array | |
+
+## Number
+
+| Filter | Description | Example |
+|:-------|:------------|:--------|
+| `plus` | Add | `{{ 4 | plus: 2 }}` → `6` |
+| `minus` | Subtract | `{{ 4 | minus: 2 }}` → `2` |
+| `times` | Multiply | `{{ 4 | times: 2 }}` → `8` |
+| `divided_by` | Divide | `{{ 10 | divided_by: 2 }}` → `5` |
+| `modulo` | Modulus | `{{ 10 | modulo: 3 }}` → `1` |
+| `abs` | Absolute value | `{{ -4 | abs }}` → `4` |
+| `ceil` | Round up | `{{ 4.1 | ceil }}` → `5` |
+| `floor` | Round down | `{{ 4.9 | floor }}` → `4` |
+| `round` | Round to nearest (or N decimal places) | `{{ 4.567 | round: 2 }}` → `4.57` |
+| `at_least` | Clamp to minimum | `{{ 3 | at_least: 5 }}` → `5` |
+| `at_most` | Clamp to maximum | `{{ 7 | at_most: 5 }}` → `5` |
+
+## Other
+
+| Filter | Description | Example |
+|:-------|:------------|:--------|
+| `default` | Fallback if nil/empty/false | `{{ val | default: "n/a" }}` |
+| `date` | Format a date | `{{ "now" | date: "%Y-%m-%d" }}` |
+| `size` | Length of string or array | `{{ "hello" | size }}` → `5` |
+| `json` | Serialize to JSON string | `{{ obj | json }}` |
+
+## Sous Custom Filters
+
+| Filter | Description |
+|:-------|:------------|
+| `bulletList` | Convert array to markdown bullet list (`- item` per line) |