Accelint Ts Performance

What it does

This skill, Accelint Ts Performance, systematically analyzes TypeScript codebases to identify performance bottlenecks. It combines an audit workflow with expert-level optimization patterns specifically focused on runtime performance. The tool highlights potential anti-patterns and provides suggestions for improvement, but emphasizes that users should carefully evaluate trade-offs before applying any optimizations. This is distinct from general best practices; use the accelint-ts-best-practices skill for those concerns.

When to use it

• When optimizing JavaScript/TypeScript codebases for runtime performance.
• To identify potential performance anti-patterns in utility functions, formatters, parsers, and validators.
• Before making significant changes or deployments where performance is critical.

Key capabilities

• Static analysis of TypeScript code to detect performance bottlenecks.
• Identification of common performance anti-patterns.
• Reporting of potential optimizations with expected gains.
• Emphasis on algorithmic complexity analysis (e.g., identifying O(n²) operations).
• Highlights trade-offs associated with different optimization techniques.

Example prompts

• "Analyze this TypeScript code for performance bottlenecks: [paste code here]"
• "What are the potential performance anti-patterns in this function? [paste code here]"
• "Suggest optimizations for improving the runtime performance of this module. [paste code here]"

Tips & gotchas

• Audit all code: Don't skip auditing seemingly simple functions, as they may be called frequently.
• Prioritize algorithmic improvements: Focus on fixing inefficient algorithms (e.g., changing O(n²) to O(n)) before micro-optimizations.
• Verify correctness: Thoroughly test optimized code, especially edge cases, to avoid introducing performance bugs.