aiw-performance-profilinglisted

# Performance Profiling and Latency Coverage Rules for writing automated performance and UI-state-transition tests before deferring to manual verification. ## Related Workflow Sections This skill works alongside these workflow sections. Consult them when writing performance tests: - **Non-Functional Dimensions**: defines when automated coverage must be attempted before manual verification. - **aiw-testing**: general test construction rules. This skill covers the performance-specific subset. - **aiw-verification**: owns the rule for adding observability when automated tests cannot reach the runtime path. This skill covers the pre-commit automated-test side of that evidence. - **aiw-failure-analysis**: owns ad-hoc diagnostics added during a post-failure audit. This skill covers automated performance coverage written before completion, not diagnostics added after a contradicted "done" claim. ## When This Skill Applies The description names the broad triggers. Add these to what counts: - Introducing or modifying caching, memoisation, debouncing, or throttling. - Converting a synchronous path to asynchronous or vice versa. - Any path where latency or throughput is a stated requirement. Platform-specific paths that commonly trigger this skill: UI state transitions, reactive subscriptions, view-layer rerenders, manual state resets, session invalidation, and UI decorators or wrappers that affect render frequency. The trigger list is project-agnostic; treat platform examples a