
Linear issue tracker — use for orgs whose `orgs.<org>.issues` is "linear" in chezmoi data
Fetch credentials and API keys. Use when a skill needs an API token, password, or other secret.
Push approval protocol, branch naming, merge request descriptions, and post-push CI watching
Slack Web API for messaging, search, and channel management
PagerDuty REST API for incidents, on-call schedules, and escalation policies
Figma REST API for reading design files, components, and assets
Manage dotfiles via chezmoi — apply safely, destroy files, manage LaunchAgents and externals, config and template gotchas
Stacked branch management via git-spice
Zoom meeting captions — file locations and format
macOS dictation custom vocabulary — sync knowledge base names and terms to the system spelling dictionary
macOS Reminders via remindctl CLI
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
Confluence REST API for wiki pages, spaces, and search
OpenCode agent runtime — manage sessions, dispatch tasks, answer waiting questions, repair DB issues, and reset diffs
Semantic commit format and pre-commit checks
Investigate production issues using logs, traces, and errors — how to triage, correlate signals, and know when to escalate.
PTY sessions for long-running processes, interactive input, signal sending (Ctrl+C), and live output tailing — use instead of bash when the process can't be run to completion synchronously
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.
Google Workspace CLI for email, docs, drive, and sheets
QA verification with Firefox DevTools browser automation — load when a diff touches UI, views, or user-facing flows and needs functional verification before committing
HTTPie-compatible HTTP client for REST API calls
GitHub CLI — source control, CI, code review, and issues for OSS and personal repos
Energy and spoon check — come up for air, see what needs attention without breaking focus
Query Elasticsearch logs, APM traces, and errors — index patterns, field names, auth setup, and time-range syntax
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.
Research people, decisions, and context across meetings, chat, email, and the knowledge base
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.
Address review feedback on your own merge request — resolve threads fixed by a commit, reply to threads you are not addressing
Self-review your own diff before committing or pushing — multi-pass review of the changes you're about to ship.
Search and query meeting transcripts, summaries, and knowledge base
GraphQL client for querying and mutating GraphQL APIs
Post-recording cleanup for minutes — wait for processing, update title from calendar, identify speakers, re-ingest knowledge base, add action items to reminders. Privacy-sensitive — use a local model only.
Route issue management to the right tracker based on GitHub org — Linear for work, GitHub Issues for OSS and personal repos
Use when facing a decision, unclear or recurring problem, system behavior question, communication challenge, or when generating novel solutions — loads structured thinking frameworks
Write product artifacts clearly — tickets, PRDs, project updates, and architecture decision records
Create and update .opencode/context-log.md to preserve issue context and checkpoint history across compaction and session handoffs
Present a plan and wait for user approval before implementing — load when a change spans multiple files or involves design decisions
Read and write documentation — Google Docs via gws CLI and Confluence via confluence CLI. Covers gotchas for both.
Strict TDD loop — red/green/refactor must be followed for every code change, no exceptions