notque/vexjoy-agent

Essays and writing behind this toolkit live at vexjoy.com.
VexJoy Agent connects plain-English requests to specialist agents, skills, and workflows. /do selects the knowledge and tools needed for your task. Hooks enforce specific checks, and scripts handle repeatable work.
The aim is to give capable models useful domain knowledge without making you learn the toolkit's catalog.
43 agents, 62 skills, 78 hooks, 151 scripts. Agents carry domain knowledge, skills provide reusable methods, hooks enforce selected checks, and scripts handle repeatable plumbing.
Works across Claude Code (/do), Codex ($do), Factory (/do), Reasonix (/do).
What It Looks Like
The router pairs a Go agent with a debugging skill, then follows the task through verification and delivery.
The Pipeline
/d — Jev-Powered Router
/d requires TypeSafe's Jev. Jev classifies the
request, checks that the selected route preserves the requested outcome, and
then dispatches the agent, skill, and pipeline.
Intent preservation is production behavior: /d restates the requested
outcome and gates dispatch on a Jev receipt for that exact proposed intent,
preventing an agent from quietly expanding an apple into an orchard.
Choose either transport:
JEV_TRANSPORT=auto is the default. It prefers Vercel when
AI_GATEWAY_API_KEY is set, then uses the direct API when only
TYPESAFE_API_KEY is set. An explicit transport never silently switches to
the other one. The TypeSafe MCP plugin is not required for /d.
Intent-alignment judgments are recorded in learning.db without raw request
text. Receipts keep the Jev judge model separate from the executing agent's
configured model and effort level. View proposed-intent difference rates by
agent profile, judge model, and transport:
Example:
Anti-Rationalization
Checks require evidence rather than confidence.
| Agent Says | What Happens |
|---|---|
| "Code looks correct, skip tests" | Exit gate requires test output. Blocked. |
| "Trivial change, no verification" | Hook blocks completion without evidence. |
| "Similar to before" | Skill demands case-specific proof. |
| "User is in a hurry" | Protocol overrides time pressure. |
| "I'm confident" | Gate demands exit code, not assertion. |
Hooks run at configured events. Skills state what to verify; blocking hooks enforce the checks they cover. Coverage depends on the runtime and tool path.
Knowledge Work Is First-Class
The content engine researches, drafts in a calibrated voice, checks 397 writing patterns, and adapts finished pieces for each platform. /html produces a self-contained report, deck, prototype, chart, or diagram.
It Proves Its Own Changes
Toolkit changes use direct review and relevant checks. Model comparisons can settle specific uncertainties; they are not required for every edit. PHILOSOPHY.md explains the validation policy.
The automated nightly evolution loop (/evolve, writes to evolution-reports/) ran regularly through mid-May 2026. It is currently dormant; recent evidence has come from manual PRs instead.
Installation
Installs into ~/.claude/ and into ~/.codex/, ~/.factory/, ~/.hermes/, and ~/.reasonix/ when the runtime command is on PATH or its home directory exists. install.sh wraps the vexinstall engine (scripts/vexinstall/). Each SessionStart in the repo re-syncs through the same engine. Symlinks (default in a git checkout) follow git pull; --copy gives a stable snapshot.
| Flag | Effect |
|---|---|
| --dry-run | Print the plan; write nothing |
| --target | Only claude, codex, factory, hermes, reasonix, or all |
| --no-takeover | Leave old unowned copies in place (default: move them to trash and replace) |