Review For Engineering Taste

Use this skill for a taste review, not a correctness review.

The job is to spot small design decisions that individually look acceptable but collectively make a codebase slower to change, harder to trust, or easier to bloat. Focus on choices that create future drag: awkward boundaries, vague ownership, leaky abstractions, incidental complexity, and defensive structure added before it pays for itself.

If a concern looks repeatable, do not stop at the review comment. Run the structuralization checkpoint below so the developer can decide whether the pattern should become a project constraint, a lintcn rule, a brain note, or just a one-off fix.

Default Stance

• Review the shape of the solution before the syntax.
• Prefer questions that expose design tension over style comments.
• Look for decisions that will get copied.
• Favor the smallest cleanup that restores clarity.
• Be specific about why something is a slop risk.

Workflow