authorlisted

# /mf:author — writing documents an agent will read A reference for any document an agent consumes: a skill, an `AGENTS.md` or `CLAUDE.md`, a file reached by a pointer from either. The packaging differs; the writing does not. The same levers make each one **predictable** — the agent taking the same _process_ every run, which is not the same as producing the same output. When the document is a skill, also read `references/skill-mechanics.md` for frontmatter, the invocation choice, and router skills. ## Context pointers A **context pointer** is a reference held in the agent's context that names some out-of-context material and encodes the condition for reaching it. A skill's `description` is one. A line in `AGENTS.md` naming a doc is the same object. The pointer's _wording_, not its target, decides when the agent reaches the material — and how reliably. A must-have target behind a weakly worded pointer is a **variance bug**: sharpen the wording first, and inline the material only if sharpening fails. A pointer does two jobs — state what the material is, and list the **branches** that should trigger reaching it (a branch is a distinct case the document handles, so different runs take different paths through it). Every word of an always-loaded pointer costs on every turn, so it earns harder pruning than the body: - **Front-load the leading word.** The pointer is where it does its triggering work. - **One trigger per branch.** Synonyms that rename a single branch are one bra