.NET Performance Patterns

Scan C#/.NET code for performance anti-patterns and produce prioritized findings with concrete fixes. Patterns sourced from the official .NET performance blog series, distilled to customer-actionable guidance.

When to Use

• Reviewing C#/.NET code for performance optimization opportunities
• Auditing hot paths for allocation-heavy or inefficient patterns
• Systematic scan of a codebase for known anti-patterns before release
• Second-opinion analysis after manual performance review

When Not to Use

• Algorithmic complexity analysis — this skill targets API usage patterns, not algorithm design
• Code not on a hot path with no performance requirements — avoid premature optimization

Inputs

| Input | Required | Description |