Appearance
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.
| Subcommand | What it does |
|---|---|
install | Pick parts and install them into this project. Opens as a reconcile when the project already has parts. |
installs | Update or remove the parts in one project. |
projects | Browse every project the harness landed in. |
modules | The catalogue, every module there is, expand one for its full sheet. |
profile | Saved part-selections, install one in a keypress. |
globals | Install and manage the global-only modules in ~/.claude. |
local | The harness's own dev tools, install one into this repo. |
extern | The module bank, browse, download, update-check, install-status. |
deps | The module dependency graph, and what installing a part would pull in. |
notices | Heads up about this project, retired parts, shadowing copies, available updates, pending migrations. |
migrate | Apply the def changes this project is behind on, a new requirement, a moved dest, a one-off fix. |
clean | Sweep this project's .claude for files no installed part claims, keep or remove each. |
diff | Preview what an update would change. |
doctor | One health pass over a project, --fix resolves what it can. |
stats | A roll-up over the install registry, what earns its place. |
hooks | Which hooks are wired into settings, and wire the unwired ones. |
scripts | View a project's .nu tools, the SCRIPTS.md registry. --ignores manages what it skips. |
archive | Walk a project's archive. Flag pruning candidates, --why one file, --retire / --unretire, and --clean to sweep. |
content | Inspect what a part actually ships. |
config | What each view does once it's finished. |
runtime | Where nushell comes from on this box, PATH or the bundled copy. |
validate | Lint the parts def. Harness repo maintenance. |
uninstall | Remove the harness's traces outside its folder. |
Commands, once their part is installed
| Commands | Part |
|---|---|
/lesson, /debrief | memory |
/handoff, /unlock | hooks |
/map, /decision, /env, /term, /role, /scripts | context |
/lecture, /lecture-pdf, /lecturer, /lecture-index | chalk |
/plan, /plan-map, /plan-review | planner |
/find-todos, /find-todos-html | find-todos |
/atlas | atlas |
/diverge | diverge |
/wiki | wiki |
/careful | careful |
/sieve | sieve |
/archive | archiver |
/link-brain | brain |
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 point | Kind | How it runs |
|---|---|---|
researcher, todo-scout, wiki-page-writer, lecturer | Subagents | Fanned out by the skill that owns them, not invoked directly. |
smart.workflow.js and its eight siblings | Workflow tool | Invoked 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 gates | Run on demand from your shell, or fire as post-edit gates once their settings fragment is merged. |
| Hooks (observers and gates) | settings.json hooks | Fire at session lifecycle events once the pack's settings fragment is merged. |
harness/scripts/ | Repo tooling | Mixed. 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/*.nu | Post-hoc readers | Installed 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.