code-review-mitsuhiko

First decide whether this is product code, library code, or mixed. The right review standard changes with that call.

Steps

1. State Context call: Product / Library / Mixed.
2. Apply the matching lens below, then the cross-cutting checks.
3. Produce findings first, ordered by severity.

Product Lens

• Does this solve a real user problem now?
• Could a dumb working version ship faster and validate the need?
• Is this abstraction, dependency, or extension point justified by a second real use case?
• If debt is accepted, is there a concrete refactor trigger?

Flag: speculative flexibility, invisible elegance, non-bottleneck optimization, and generic frameworks for one feature.