06-reference

indydevdan setup hook install maintain

Sat Apr 18 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·reference ·source: IndyDevDan YouTube ·by IndyDevDan
indydevdanclaude-codesetup-hookinstall-scriptmaintenance-scriptjust-runneragentic-codebaseonboardinghooksslash-commandsagent-sandboxesdeterministic-plus-agenticyear-of-trust

IndyDevDan — One Prompt Every AGENTIC Codebase Should Have

Why this is in the vault

This is Dan’s January 26 video introducing the new Claude Code setup hook (lifecycle event that fires on --init and --maintenance flags) and pairing it with just as a command runner and a /install slash command that runs both deterministic scripts and an agentic prompt. It’s vault-worthy not because the hook itself is novel — Dan himself says “this is just a script, this is not that interesting” — but because the pattern is the cleanest expression yet of the “deterministic-plus-agentic” combination Dan has been building toward all year. Three reasons:

  1. Concrete codification of the year-of-trust thesis. Dan’s 2026 framing video (same ingestion cycle, 2026-04-19-indydevdan-top-2-percent-plan-2026.md) names “trust” as the unifying primitive for 2026. This video shows the first concrete worked example of how you build trust into a codebase: a deterministic hook (predictable execution) wrapped by an agentic prompt (intelligent oversight) wrapped by a just command (repeatable interface). It’s the year-of-trust thesis materialized at the codebase level.
  2. “Living document that executes” is the cleanest one-line summary of the harness-era shift. Dan’s closing line — “what you get here is a living document that executes” — is a more memorable restatement of the same architecture Cobus Greyling, Harrison Chase, Akshay Pachaar, and Thariq have been describing under different names (harness era, AI-developer-workflows, agent-harness anatomy, session management). The vault now has multiple independent voices converging on the claim that the right unit of work is “natural-language process spec that runs deterministically when it can and agentically when it must.” Dan’s setup-hook example is the smallest reproducible artifact of that architecture.
  3. Direct mapping to RDCO’s onboarding problem for new skills/cron jobs. RDCO has 60+ skills, multiple cron jobs, and a Mac Mini always-on agent — but no /install or /maintenance pattern. When a skill breaks, the founder or Ray has to debug from memory. When a new MCP is added, env-var checking is ad hoc. Dan’s pattern (just-file as launchpad + setup-hook as deterministic bootstrap + /install slash command as agentic validator) is directly applicable to the RDCO ops repo.

Core argument

Great teams onboard new engineers in one command. The age of agents lets every team be a great team. The argument has three layers:

  1. The setup hook is a Claude Code primitive most engineers haven’t noticed. It runs before sessions start (you trigger it via claude --init or claude --maintenance). It doesn’t appear in the lifecycle diagram. It’s “use this for operations you do not want to run on every session like installing dependencies, running migrations, or periodic maintenance tasks.”
  2. The hook alone is uninteresting — it’s just a script. The pattern is interesting. The pattern is: deterministic script (does the install/maintenance work) + structured logging (writes results to a known location) + agentic prompt (reads the log, validates, reports, optionally goes interactive). The agentic layer adds: documentation generation, error resolution via natural language, common-issue YAML blocks the agent reads, and human-in-the-loop branches for ambiguous decisions.
  3. just is the right launchpad for this pattern. A single file that lists every command your team or your agents will run. New engineer types just, sees every workflow, picks one, runs it. Dan introduces /install and /install-hil (human-in-the-loop) as the two canonical commands — one for sandboxes/CI, one for new-engineer onboarding.

The trust frame: the pattern lets you pre-encode common failure modes (“if the database is corrupt, clear and rerun”) so the agent handles them deterministically the second and third time. Each new engineer’s failure becomes one more entry in the prompt, and the prompt becomes a living document that executes.

Cross-reference to Mintfi’s “Standard for LM Executables” (Jan 15): Dan flags that he isn’t the only one converging here — Mintfi proposed a standard. Dan’s stance is “we don’t need a standard, just the idea.” That’s a healthy stance: the value is the pattern, not the spec.

Mapping against Ray Data Co

Open follow-ups