dotfiles

Review changes since a fixed point along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match the originating shape, revision description, issue, or PRD?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, revision, PR, working-copy changes, or asks to "review since X".

Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, terminals, commands, or communication with another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work.

Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces an interactive HTML page, a Notion page, or an interactive Obsidian vault note.

Session mode — coordinate only, delegate all actual work to background minion subagents

Interview-style session that aligns a plan with the existing domain vocabulary, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Transform a workflow description into affordance tables showing UI and Code affordances with their wiring. Use to map existing systems or design new ones from shaped parts.

TypeScript coding standards and design taste. Use when working on TypeScript or React/frontend code; when adding or changing domain models, modules, adapters, parsers, typed errors, async workflows, tests, TypeScript contracts, Cloudflare Workers/Durable Objects/Agents, or Effect code; for the user's naming, control-flow, and code-style conventions on any code in any language; or when another engineering skill needs the user's coding standards.

Execution and process principles for non-trivial engineering work, covering how to scope, sequence, delegate, and verify, independent of language or harness. Use when planning a change, sizing a diff, debugging, driving a long autonomous run, or deciding what "done" means. This is the process layer; code-design taste lives in the coding-standards skill.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Lay out planned work from a spec as empty jj revisions — one per stage — each carrying the stage's goal, a link to the spec, acceptance criteria, scope, files, and verification, plus a deviations log. Then execute each stage by filling its revision with the right workflow. Use when turning a spec into staged / phased / sliced work in a jj repo, when asked to plan implementation as jj revisions, or when working through such a plan.

Jujutsu (jj) version control commands and workflows. Use when performing version control operations, committing changes, managing branches/bookmarks, or syncing with remotes. Always use jj instead of git.

Create diagrams using Penrose — a constraint-based system that separates content from visual representation using three DSLs (domain, substance, style). Use when the user asks for set diagrams, graph layouts, geometry figures, architecture diagrams, entity-relationship diagrams, state machines, dependency graphs, or any relational diagram where automatic layout from constraints is valuable.

Capture what a finished task taught you so the next run does not relearn it. Use for "/reflect", "capture what we learned", "remember this for next time", or explicit requests to save a durable lesson. Routes the lesson into the memory system by default and escalates to a skill edit only when the lesson is a repeatable procedure.

Use this methodology when collaboratively shaping a solution with the user - iterating on problem definition (requirements) and solution options (shapes).

Standardize Python development using UV - a fast, unified package and project manager. Use when creating Python projects, managing dependencies, setting up virtual environments, installing Python versions, or optimizing Python workflows. Replaces pip, virtualenv, pyenv, poetry, and pipx with a single 10-100x faster tool.

Explain in clear, complete plain-English sentences — no shorthand, no padding

Run a fork-fanned tree search over jj revisions against a frozen judge — fan each frontier revision into divergent child attempts, score every child, keep the best as the new frontier, and harvest the winning path into a linear stack. Use when the winning approach is unknown and must be discovered by measured search (optimize a metric, explore many approaches in parallel, autoresearch-style overnight runs), as opposed to jj-plan's known, ordered stages.

Read the real source of an external project (a library, framework, dependency, or any GitHub repo) from a local clone kept under ~/.explorer/repos/<org>/<repo>. Use when you need to understand how external code actually works — an API's implementation, internals, or undocumented behavior — instead of guessing from docs, memory, or types. Clones new repos into the store and updates existing ones.

Record and manage code-review findings as durable, threaded comments anchored to file:line in a jj (Jujutsu) repository, using the jj-review CLI. Use when reviewing code in a jj repo and you want to leave review comments, reply to or resolve threads, query open comments as JSON, or track review rounds (baselines and interdiffs) instead of leaving findings only in chat.

(no description)

Programmatic hunk selection for jj (Jujutsu). Use when splitting commits, making partial commits, or selectively squashing changes without interactive UI.

Workflow for jujutsu (jj) megamerges — local-only octopus merges that integrate multiple working branches. Use when the user mentions megamerges, octopus merges, parallel branches, or when `jj log` shows a commit described `megamerge` or `@` has a merge in its ancestry.

Create per-feature copy-on-write workspaces from a directory, with native jj integration. Use when the user wants to spin up an isolated working copy to try something in parallel — especially in repos with heavy untracked state (node_modules, target/, .venv, build caches) that would be expensive to rebuild in a fresh `jj workspace add`. Triggers — "make a workspace", "branch but keep my build artifacts", "try X without disturbing current work", "spin up a disposable copy of this repo", or any mention of `pando` / `pd`.

Tmux terminal multiplexer commands and workflows. Use when managing tmux sessions, windows, panes, or capturing terminal output for debugging.