template

Use when asked to reflect or evaluate philosophically on a body of work ("wdyt", "what do you think philosophically", a retrospective), or when proactively stepping back after a long or winding piece of work. For producing a grounded, self-critical synthesis — not platitudes, a victory lap, or a list of lessons.

Use when asked to explain, walk through, or document how a file or function works. Produces a plain-English prose explanation of the logic grounded in the code's actual variable, method, field, and type names — in execution order, with the load-bearing "why"s and concrete end-to-end traces.

Use when starting feature work that needs isolation, when dispatching subagents that will edit code, or when managing existing worktrees. Teaches the repo's `bun run worktree:*` scripts that allocate isolated Postgres DBs, MinIO buckets, a Redis DB, and ports — not plain `git worktree add`.