1# Audit output template
2 
3## Intent
4 
5Use this structure when reporting SwiftUI performance findings so the user can quickly see the symptom, evidence, likely cause, and next validation step.
6 
7## Template
8 
9```markdown
10## Summary
11 
12[One short paragraph on the most likely bottleneck and whether the conclusion is code-backed or trace-backed.]
13 
14## Findings
15 
161. [Issue title]
17   - Symptom: [what the user sees]
18   - Likely cause: [root cause]
19   - Evidence: [code reference or profiling evidence]
20   - Fix: [specific change]
21   - Validation: [what to measure after the fix]
22 
232. [Issue title]
24   - Symptom: ...
25   - Likely cause: ...
26   - Evidence: ...
27   - Fix: ...
28   - Validation: ...
29 
30## Metrics
31 
32| Metric | Before | After | Notes |
33| --- | --- | --- | --- |
34| CPU | [value] | [value] | [note] |
35| Frame drops / hitching | [value] | [value] | [note] |
36| Memory peak | [value] | [value] | [note] |
37 
38## Next step
39 
40[One concrete next action: apply a fix, capture a better trace, or validate on device.]
41```
42 
43## Notes
44 
45- Order findings by impact, not by file order.
46- Say explicitly when a conclusion is still a hypothesis.
47- If no metrics are available, omit the table and say what should be measured next.
48