oribarilan

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when writing or reviewing request handlers, RPCs, or background jobs for production; adding tracing, metrics, or structured-log calls; or making diagnosability decisions

Use when designing or reviewing a public API, exported function signature, module boundary, exported type/interface, or any contract other code depends on

Use when implementing any feature or bugfix, before writing implementation code

Use when writing, reviewing, or changing build scripts, CI workflows, deploy pipelines, repo setup, or evaluating a new tool/dependency

Use when writing or reviewing error handling, floating-point math, concurrent code, remote calls, singletons/globals, hot-path data structures, or high-volume log statements

Use when writing or reviewing tests, designing test data, naming a test, choosing what to assert, or writing test helpers/mocks/fixtures

Use when gathering or interpreting requirements, estimating effort, or communicating with stakeholders/customers about what to build

Use when starting any coding task — establishes the 97 trigger map so principles fire when relevant

Use when about to commit, finish a task, open a PR, summarize work for the user, or when the user asks for a review or summary — NOT just on autonomous commits, which are rare in OpenCode usage

Use when considering, evaluating, or performing a refactor, restructure, cross-file rename, or cleanup

Use when writing or reviewing functions, classes, naming, or non-trivial logic (≥3 lines)