justjake

Use when investigating parser performance — which functions are hot, where allocations happen, whether a change actually helped. Runs a CPU profile of the parser hot loop and surfaces the report.

Use when code has parallel or semantically similar representations of the same data, state, or intent. Find unnecessary translation layers, choose one canonical model, and collapse adapters around it.

Use when code has parallel or semantically similar representations of the same data, state, or intent. Find unnecessary translation layers, choose one canonical model, and collapse adapters around it.

Use when designing, refactoring, or reviewing code where business/product rules, permissions, defaults, feature gates, configuration, orchestration, or user-facing choices may be mixed with reusable execution mechanisms, algorithms, adapters, data access, parsers, or other low-level primitives. Apply the Unix-inspired policy/mechanism separation: isolate what should happen from how it is carried out.