dotfiles

OpenCode agent runtime — manage sessions, dispatch tasks, repair DB issues, and reset diffs

Look up people, projects, products, and decisions locally first: contact info (email, Slack ID, GitHub handle), titles and teams, project/product status, who works on what, and past decisions. Check before searching Slack, email, calendar, or GitHub — this is the first stop for any contact detail, project context, or decision-history question.

Load when reviewing a diff, naming a code smell or anti-pattern, deciding refactoring direction, or grading review-comment severity. Required reading when a named pattern is cited — load explicitly rather than paraphrasing from memory.

Load before creating, restacking, or landing a branch in a git-spice–managed stack — branch naming, stack navigation, and conflict/restack recovery. Use instead of raw git commands whenever the repo has a git-spice stack.

Load when investigating production errors, latency, or trace data that requires querying Elasticsearch/APM directly — index patterns, field names, auth setup, and time-range syntax. Use before hand-rolling a query DSL call or guessing field names.

Manage dotfiles via chezmoi — apply safely, destroy files, manage LaunchAgents and externals, config and template gotchas

Communication style, audience awareness, and AI-authorship markers for human-facing prose — load when composing chat messages, review comments, merge request descriptions, emails, doc bodies, or ticket descriptions

Push approval protocol, branch naming, merge request descriptions, and post-push CI and code-review watching

Fires when lead is about to publish the assembled QA report to a merge request after human approval.

Semantic commit format and pre-commit checks

macOS Reminders via remindctl CLI

HTTPie-compatible HTTP client for REST API calls

Investigate production issues using logs, traces, and errors — how to triage, correlate signals, and know when to escalate.

PagerDuty REST API for incidents, on-call schedules, and escalation policies

Load before designing a new system, choosing between competing implementations, weighing tradeoffs across libraries or frameworks, or escalating an architectural question to a human. Fires at the moment a multi-option design decision appears, not during routine implementation.

Energy and spoon check — come up for air, see what needs attention without breaking focus

Use when facing a decision, unclear or recurring problem, system behavior question, communication challenge, or when generating novel solutions — loads structured thinking frameworks