97
Gives Claude Code guidance for designing APIs, planning refactors, changing build and deploy setup, writing clean functions, and avoiding common correctness traps such as error handling and concurrency bugs.

Gives Claude Code guidance for designing APIs, planning refactors, changing build and deploy setup, writing clean functions, and avoiding common correctness traps such as error handling and concurrency bugs.
Use when designing or reviewing a public API, exported function signature, module boundary, exported type/interface, or any…
Use when considering, evaluating, or performing a refactor, restructure, cross-file rename, or cleanup
Use when writing, reviewing, or changing build scripts, CI workflows, deploy pipelines, repo setup, or evaluating a new…
Use when writing or reviewing functions, classes, naming, or non-trivial logic (≥3 lines)
Use when writing or reviewing error handling, floating-point math, concurrent code, remote calls, singletons/globals, hot-path…
Use when introducing, reviewing, or renaming a top-level type, table, or domain concept; or choosing where state lives (in-memory…
Use when writing or reviewing request handlers, RPCs, or background jobs for production; adding tracing, metrics, or…
Use when writing or reviewing code that parses user input, builds SQL/shell commands, handles secrets/credentials, hashes…
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 —…
Use when writing or reviewing tests, designing test data, naming a test, choosing what to assert, or writing test…
Use when starting any coding task — establishes the 97 trigger map so principles fire when relevant
Use when gathering or interpreting requirements, estimating effort, or communicating with stakeholders/customers about what to…
Is this you? Claim your profilePut a plugin at the top of Plugins, from $9