qualcomm Audit QUI Best Practices
Required Reference
Before reviewing covered QUI component usage, read the bundled references/component-rules.md reference.
Review Workflow
- Identify imports and JSX that match a target context in the reference.
- Treat every matching issue as a finding.
- Do not add findings for non-covered components, general design preferences, or code outside the shared reference.
Output
Lead with findings ordered by severity. Include file and line references for every actionable issue.
Use this shape:
Findings
- [P1] <component rule name>: <issue>. <file:line>
<what the component contract requires>
Open Questions
- \<only if needed\>
Residual Risk
- \<only if relevant\>
If there are no issues, say that clearly and include any remaining verification gaps.