performance-optimization

1. Trigger Conditions

Invoke this skill as an opt-in gate before ship, or on-demand when a performance regression is detected.

Specific triggers:

• /perf slash command
• Phase 5a of /build-feature (user opt-in)
• Lighthouse score drops below 80 for a user-facing page
• Bundle size increases by more than 5% vs main branch
• User reports slow load times or jank

Do not invoke proactively on every feature. Performance work without a measurement baseline is guesswork.

2. Prerequisites

• A working implementation (feature complete)
• Ability to run the app locally or against a staging environment
• Bundle analyser available (npm run build -- --analyze or source-map-explorer)