Skip to content

Entry Points ​

How you actually run the harness. Nothing here fires on its own until a part is installed. The manager copies the parts you pick into a target project's .claude/, or into ~/.claude for the global-only ones, and the commands, skills, workflows, and hooks become available from there. See Install Scopes for which parts go where and why.

The manager ​

One CLI, harness, registered by npm link from installer/. Run it bare in a terminal and you get a dashboard; run it with a subcommand and you go straight to that view.

SubcommandWhat it does
installPick parts and install them into this project. Opens as a reconcile when the project already has parts.
installsUpdate or remove the parts in one project.
projectsBrowse every project the harness landed in.
modulesThe catalogue, every module there is, expand one for its full sheet.
profileSaved part-selections, install one in a keypress.
globalsInstall and manage the global-only modules in ~/.claude.
localThe harness's own dev tools, install one into this repo.
externThe module bank, browse, download, update-check, install-status.
depsThe module dependency graph, and what installing a part would pull in.
noticesHeads up about this project, retired parts, shadowing copies, available updates, pending migrations.
migrateApply the def changes this project is behind on, a new requirement, a moved dest, a one-off fix.
cleanSweep this project's .claude for files no installed part claims, keep or remove each.
diffPreview what an update would change.
doctorOne health pass over a project, --fix resolves what it can.
statsA roll-up over the install registry, what earns its place.
hooksWhich hooks are wired into settings, and wire the unwired ones.
scriptsView a project's .nu tools, the SCRIPTS.md registry. --ignores manages what it skips.
archiveWalk a project's archive. Flag pruning candidates, --why one file, --retire / --unretire, and --clean to sweep.
contentInspect what a part actually ships.
configWhat each view does once it's finished.
runtimeWhere nushell comes from on this box, PATH or the bundled copy.
validateLint the parts def. Harness repo maintenance.
uninstallRemove the harness's traces outside its folder.

Commands, once their part is installed ​

CommandsPart
/lesson, /debriefmemory
/handoff, /unlockhooks
/map, /decision, /env, /term, /role, /scriptscontext
/lecture, /lecture-pdf, /lecturer, /lecture-indexchalk
/plan, /plan-map, /plan-reviewplanner
/find-todos, /find-todos-htmlfind-todos
/atlasatlas
/divergediverge
/wikiwiki
/carefulcareful
/sievesieve
/archivearchiver
/link-brainbrain

Skills, which fire on their own trigger phrases ​

skill-smith, brain, chalk, atlas, wiki, plan, diagram, find-todos, lesson-recall, finn-style-sweep, cpp-lua-bind, natvis-writer, profiler-zones, media-grab, task-anchor.

A skill fires when its description matches what you asked for, which makes that description the whole routing surface. A skill nobody reaches is a skill that does nothing, so the descriptions are written to claim their job rather than merely describe it, and a new one is checked against the phrasings that should and should not fire it before it ships.

Everything else ​

Entry pointKindHow it runs
researcher, todo-scout, wiki-page-writer, lecturerSubagentsFanned out by the skill that owns them, not invoked directly.
smart.workflow.js and its eight siblingsWorkflow toolInvoked through Claude Code's Workflow tool, composed one nesting level deep.
The stack packs (nu-lint.nu, msbuild.nu, ubt.nu, ahkv2-guard.nu, ...)Scripts and gatesRun on demand from your shell, or fire as post-edit gates once their settings fragment is merged.
Hooks (observers and gates)settings.json hooksFire at session lifecycle events once the pack's settings fragment is merged.
harness/scripts/Repo toolingMixed. Thirteen are installable parts picked under the scripts group and landing at .claude/scripts/, the rest are local modules or run only against this repo. See Repo Scripts.
~/.claude/telemetry/*.nuPost-hoc readersInstalled global by harness local, run on demand from any project. Nothing is wired to an event unless you wire it. See Telemetry.

The manager is the one thing you run first. Everything else becomes available in a project once its part is installed there.