harness compatibility layer — a BUILT-IN foundation module (ships in the
main jar, always present, gated by toggles) that exposes the SKILLS vis'
own project dir and other AI coding HARNESSES (Claude Code, pi, opencode, the agents
standard, …) leave on disk to the vis model. The sibling of the shell
layer's POSIX compat. Vis reads its OWN project-local skills from
.vis/skills (highest precedence).
SKILLS are DOCUMENTS, never a verb: the prompt lists every skill
name — description (cheap — always present) and the WHOLE SKILL.md is
one document in the doc/apropos corpus. apropos(pattern) filters skill
names and doc(name) prints one whole. Reading a skill has no session effect:
there is nothing to activate, nothing to re-read and no activation receipt.
The USER's /skill:<name> slash is that same document with a POINTER, never a
copy: it expands to one sentence naming the skill (plus the owning project
and any bundled resource paths, which the body does not carry) and leaves
fetching it to the model, which is the only party that knows whether the
text is still in front of it. No injected body means nothing to remember
between two /skill:<name>s: every skill surface is stateless.
Skills and commands have no user toggle; the layer is always active.
`harness` compatibility layer — a BUILT-IN foundation module (ships in the main jar, always present, gated by toggles) that exposes the SKILLS vis' own project dir and other AI coding HARNESSES (Claude Code, pi, opencode, the agents standard, …) leave on disk to the vis model. The sibling of the shell layer's POSIX compat. Vis reads its OWN project-local skills from `.vis/skills` (highest precedence). - SKILLS are DOCUMENTS, never a verb: the prompt lists every skill `name — description` (cheap — always present) and the WHOLE `SKILL.md` is one document in the `doc`/`apropos` corpus. `apropos(pattern)` filters skill names and `doc(name)` prints one whole. Reading a skill has no session effect: there is nothing to activate, nothing to re-read and no activation receipt. - The USER's `/skill:<name>` slash is that same document with a POINTER, never a copy: it expands to one sentence naming the skill (plus the owning project and any bundled resource paths, which the body does not carry) and leaves fetching it to the model, which is the only party that knows whether the text is still in front of it. No injected body means nothing to remember between two `/skill:<name>`s: every skill surface is stateless. Skills and commands have no user toggle; the layer is always active.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |