herdr-worker-profile

Read and apply Courier architecture decision records. Use when planning, reviewing, or implementing changes with architecture, infrastructure, interface, routing, or cross-service impact.

Enforces the Linear proof boundary for planning, implementation, review, readiness, and merge. Use for multi-surface work, ownership or plan changes, exact-head evidence, Scope Review, or moving a ticket to Done.

Canonical git protocol for AI Code Flow: pre-flight checks, branch naming, worktree isolation for parallel multi-ticket waves, WIP commits, squash-before-PR, push, failure recovery. Load before any git operation.

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

Read before implementation or test work to choose a task-appropriate verification loop.

Courier TypeScript standards for style, error handling, async work, imports, and tests. Use before writing or reviewing TypeScript in backend, services, or related repos.

Scoped single-writer implementation and verification.