Performance Optimization

Use this skill when performance is the main concern. Measure first, optimize the confirmed bottleneck, and verify improvement without changing business behavior accidentally.

Operating Rules

• Do not optimize blindly. Capture a baseline or concrete symptom first.
• Read project docs, architecture notes, caching rules, database rules, design-system rules, and existing performance conventions.
• Preserve business logic and data correctness.
• Prefer low-risk local improvements before broad architecture changes.
• Treat caching as a contract: define invalidation, freshness, and user-specific data boundaries.
• Avoid adding dependencies or infrastructure unless measurement justifies them.
• If the issue is actually a bug or regression with unclear cause, switch to debugging-workflow.
• If the issue requires benchmarks, regression tests, or browser visual checks, coordinate with testing-verification.

Workflow

1. Define The Performance Claim