Hand a bounded task to another coding agent — code review, a second opinion, an adversarial discussion, analysis, or a scoped implementation — and run it in its own visible pane when the session is inside Herdr or Orca. Use when the user names another agent…
My rules for when a task works around a problem in someone else's project (a dependency, tool, or service misbehaving) — checking the problem is really upstream's, marking the workaround in our code, offering to contribute the fix back, keeping upstream work…
My pull request workflow — PR sizing and splitting, the mandatory pr-reviewer pre-flight review, CI watching after a push, PR description and title conventions, and how to dispose of AI review-bot findings. Load this before creating a pull request, before…
My calendar availability rules. Use this whenever listing free dates or times, proposing meeting slots, or deciding whether a calendar slot is realistically usable. Inspect event semantics, travel context, and practical buffers around nearby events rather…
My rules for crediting external projects — when code or a design pattern adapted from an upstream repo, blog post, or reference implementation needs attribution, how to check the upstream license before assuming MIT, where to put the notice, and how to word…