> For the complete documentation index, see [llms.txt](https://docs.urbit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.urbit.org/hoon/rune.md).

# Runes

Reference documentation for Hoon's rune expressions organized by family.

Documentation for Hoon's rune expressions.

## Non-Rune Expressions <a href="#non-rune-expressions" id="non-rune-expressions"></a>

* [Constants](/hoon/rune/constants.md) - Hoon uses runes to form expressions, but not all expressions have runes in them. First, we have constant expressions (and also expressions that would be constant, but that they allow for interpolations).
* [Limbs and Wings](/hoon/limbs.md) - Limb and wing expressions also lack runes.
* [`--`, `==` (Terminators)](/hoon/rune/terminators.md) - Digraphs used to terminate expressions.

## Runes Proper <a href="#runes-proper" id="runes-proper"></a>

* [`| bar` (Cores)](/hoon/rune/bar.md) - Produce cores.
* [`$ buc` (Structures)](/hoon/rune/buc.md) - Define custom types.
* [`% cen` (Calls)](/hoon/rune/cen.md) - Make function calls.
* [`: col` (Cells)](/hoon/rune/col.md) - Produce cells.
* [`. dot` (Nock)](/hoon/rune/dot.md) - Carry out Nock operations in Hoon.
* [`/ fas` (Imports)](/hoon/rune/fas.md) - Import files.
* [`^ ket` (Casts)](/hoon/rune/ket.md) - Adjust types without violating type constraints.
* [`+ lus` (Arms)](/hoon/rune/lus.md) - Define arms in a core.
* [`; mic` (Make)](/hoon/rune/mic.md) - Miscellaneous useful macros.
* [`~ sig` (Hints)](/hoon/rune/sig.md) - Use Nock 11 to pass non-semantic info to the interpreter.
* [`= tis` (Subject Modification)](/hoon/rune/tis.md) - Modify the subject.
* [`? wut` (Conditionals)](/hoon/rune/wut.md) - Branch on conditionals.
* [`! zap` (wild)](/hoon/rune/zap.md) - Expressions that don't fit anywhere else go here.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.urbit.org/hoon/rune.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.