Liking cljdoc? Tell your friends :D

com.blockether.vis.ext.foundation-harness.core

harness compatibility extension — a DROPPABLE classpath plug-in (drop the jar, drop the feature) that exposes the AGENTS and 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).

Two bare verbs (bound like cat/rg via :ext.engine/builtin? true):

  • SKILLS are PROGRESSIVE: the prompt lists every skill name — description (cheap — always present while :vis/harness-skills is ON), and skill(name) loads the FULL SKILL.md + its bundled resource PATHS on demand so the model spends tokens only on the one it uses.

  • AGENTS are an ALIAS to sub_loop: agent(name, prompt) runs the named agent as a CHILD loop whose system prompt IS that agent's markdown body, on its declared model. Gated by :vis/harness-agents.

This layer OWNS its toggles — registered here, not in core — so dropping the jar drops the toggles. :owner :vis :group :tools parks them in Settings → Feature Toggles beside the shell toggle. Each verb gates on its OWN toggle (the extension activates if EITHER is on), so they switch independently.

`harness` compatibility extension — a DROPPABLE classpath plug-in (drop the
jar, drop the feature) that exposes the AGENTS and 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).

Two bare verbs (bound like cat/rg via `:ext.engine/builtin? true`):

- SKILLS are PROGRESSIVE: the prompt lists every skill `name — description`
  (cheap — always present while `:vis/harness-skills` is ON), and
  `skill(name)` loads the FULL `SKILL.md` + its bundled resource PATHS on
  demand so the model spends tokens only on the one it uses.

- AGENTS are an ALIAS to `sub_loop`: `agent(name, prompt)` runs the named
  agent as a CHILD loop whose system prompt IS that agent's markdown body,
  on its declared model. Gated by `:vis/harness-agents`.

This layer OWNS its toggles — registered here, not in core — so dropping the
jar drops the toggles. `:owner :vis :group :tools` parks them in Settings →
Feature Toggles beside the shell toggle. Each verb gates on its OWN toggle
(the extension activates if EITHER is on), so they switch independently.
raw docstring

com.blockether.vis.ext.foundation-harness.discovery

Cross-HARNESS discovery of agents + skills — the sibling of the shell layer's POSIX compat, for the agent/skill definitions vis' OWN project dir and OTHER AI coding harnesses (Claude Code, pi, opencode, the agents standard, …) leave on disk.

An AGENT is a markdown file with YAML-ish --- frontmatter (name, description, model, tools) + a body that IS a system prompt. A SKILL is a SKILL.md (same frontmatter, name+description) in its own directory, alongside bundled resource files.

Discovery is PURE except for the directory scan: parse-frontmatter, parse-agent, parse-skill-meta, and dedup-by-name take strings and are unit-tested without the filesystem; the discover-* fns walk the known source roots. Precedence is source ORDER, first-name-wins (vis project-local > other harnesses' project > user > plugin; Vis and Claude before pi/agents/opencode).

Cross-HARNESS discovery of agents + skills — the sibling of the shell
layer's POSIX compat, for the agent/skill definitions vis' OWN project dir
and OTHER AI coding harnesses (Claude Code, pi, opencode, the agents
standard, …) leave on disk.

An AGENT is a markdown file with YAML-ish `---` frontmatter
(`name`, `description`, `model`, `tools`) + a body that IS a system
prompt. A SKILL is a `SKILL.md` (same frontmatter, name+description) in
its own directory, alongside bundled resource files.

Discovery is PURE except for the directory scan: `parse-frontmatter`,
`parse-agent`, `parse-skill-meta`, and `dedup-by-name` take strings and
are unit-tested without the filesystem; the `discover-*` fns walk the
known source roots. Precedence is source ORDER, first-name-wins
(vis project-local > other harnesses' project > user > plugin; Vis and
Claude before pi/agents/opencode).
raw docstring

cljdoc builds & hosts documentation for Clojure/Script libraries

Keyboard shortcuts
Ctrl+kJump to recent docs
Move to previous article
Move to next article
Ctrl+/Jump to the search field
× close