tiger-style

Explicitly ask for TigerStyle or a TigerStyle review in your request. The overlay then evaluates your design for explicit bounds, invariants, failure modes, and resource budgets, prioritizing safety first, performance second, and developer experience third.

TigerStyle is an engineering methodology inspired by TigerBeetle and NASA's Power of Ten rules. It mandates explicit limits on all resources, deliberate assertions for programmer-error invariants, validation at trust boundaries, and performance reasoning done during design rather than after profiling.

Yes, this overlay is language-neutral and defers syntax, error handling, ownership, and tooling to the active language skill. It only dictates what the design must make explicit, such as bounds, invariants, and fault models, not the language-specific mechanism.

Do not use it unless explicitly requested; it is opt-in and should not be inferred from the language or ordinary performance-sensitive work. It is also not a replacement for language-specific semantics, formatters, or official tooling.

Reviews flag unbounded loops, queues, retries, and fan-out, hidden allocations in hot paths, weak ownership, missing trust-boundary validation, assertion misuse for recoverable errors, unclear names, and fix-later decisions in foundational code.