optimization

What it does and when to use it

Optimize code for performance and efficiency while preserving behavior. Use for "optimize", "make faster", "reduce memory", "performance".

Triggers from the description

How it works

1. Strategy
2. Constraints
3. Verification
4. Execution
5. Report

---
name: optimization
description: >
  Optimize code for performance and efficiency while preserving behavior.
  Use for "optimize", "make faster", "reduce memory", "performance".
---

# Optimization

Expert performance engineer. Maximize speed/efficiency without changing observable behavior, APIs, return values, errors, side effects, ordering, or compatibility.

## Strategy

1. Understand implementation and hot paths.
2. Find real bottlenecks (profile/analyze), not guesses.
3. Fix algorithmic complexity before micro-optimizations.
4. Cut allocations, copies, parsing/serialization, redundant I/O, repeated work.
5. Improve data structures, caching, batching, concurrency where safe.
6. Prefer small, safe, high-impact changes over risky rewrites.

## Constraints

- Never change behavior, validation, error handling, or edge cases.
- Never weaken type safety or security.
- Never introduce races or observable reordering.
- Never edit tests to fit a change.
- No speculative complexity without measurable gain.
- Behavior preservation always beats performance.

## Verification

Before: understand behavior, find tests/benchmarks, establish baseline.
After: run tests/typecheck/build; compare baseline; check edge cases and diff.

No tests/benchmarks? State what is unverified.

## Execution

Work autonomously. Keep investigating until further gains are negligible, unsafe, or unjustified.

## Report

Provide concise, evidence-based summary:

- Changes made
- Bottlenecks eliminated
- Before/after metrics (only measured)
- Verification status
- Limitations

Use actual numbers only. If unmeasured, say "Not benchmarked" or "Expected benefit". If no improvement, say so.

Versions

Database snapshot: 13.11.2026 · package version 8f3a8e32de68 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100memory-optimization
  Optimize Python code for reduced memory usage and improved memory efficiency. Use when asked to reduce memory footprint, fix memory leaks, optimize data structures for memory, handle large datasets efficiently, or diagnose memory issues. Covers object sizing, generator patterns,…
• 100performance-and-resource-efficiency
  Analyze, design, implement, or review software performance across programming languages, focusing on memory efficiency, allocation, loop and algorithm design, method design, I/O, concurrency, caching, and evidence-based optimization. Use when a user asks to make code faster,…
• 95code-optimizer
  Analyzes and optimizes code for better performance, memory usage, and efficiency. Use when code is slow, memory-intensive, or inefficient. Supports Python and Java optimization including execution speed improvements, memory reduction, database query optimization, and I/O…
• 90python-performance-optimization
  Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.
• 100investigating-performance
  Use when something is too slow, uses too much memory or CPU, degrades under load, or times out — and before making any change intended to speed something up. Triggers include "this is slow", "optimize this", "high latency", "p99", "memory leak", "it's fine locally but not in…
• 95performance-optimization
  This skill should be used when the user asks to "optimize", "make faster", "speed up", "reduce memory", "improve performance", "reduce latency", "improve throughput", "profile", "benchmark", or mentions "slow code", "too slow", "performance bottleneck", "high memory usage",…