JetBrains/intellij-community / .claude/skills/compose-ui
compose-ui
VerifiedWrite or audit Compose Desktop UI state, effects, and boundaries.
audit/references/reporting-guidance.md
View on GitHub# Audit Reporting Guidance
Use this reference when preparing the final report for a Compose UI audit, especially for no-finding audits, severity
assignment, evidence rules, or optional scoring.
## No-Finding / Low-Finding Audits
An audit can state that the code looks healthy and call out these positive patterns:
- One presenter-owned screen state is collected at the screen/root boundary.
- local hover/focus/text-field/expanded state that is purely visual
- Composables delegate persistence, file pickers, URI opening, and presenter-owned actions through callbacks.
- stable lazy-list keys and useful `contentType`
- `LaunchedEffect(Unit)` used only for one-shot focus/scroll setup with no changing captures
When no serious issues are found, return a short report with confidence/limits and low-priority polish only.
## Severity Guide
- **Critical** covers likely broken behavior, data loss, app-state desync, runaway work, a crash, or an architectural
boundary breach that can spread.
- **High:** repeated pattern that risks correctness/performance or blocks maintainability.
- **Medium:** localized smell with clear cleanup value.
- **Low:** style/API polish that should be fixed opportunistically.
## Evidence Rules
- Cite concrete file paths and line numbers where possible.
- Prefer 2-4 representative examples for systemic findings.
- Do not infer runtime problems from a grep hit alone.
- Do not double-count one root cause across categories.
- Separate Compose runtime/architecture findings from Jewel component-choice findings.
- Distinguish "found no evidence" from "proved absent".
- When recommending a fix, name the destination layer: presenter/coordinator, state holder, composition, or interop
helper.
## Scoring If Explicitly Requested
| Category | Suggested weight |
|---|---:|
| Boundary and state ownership | 30% |
| Desktop lifecycle and flow collection | 20% |
| Effects and coroutine usage | 20% |
| Lazy lists and recomposition | 15% |
| Modifier/API shape and interop seams | 15% |
Label scoring as heuristic, not a measured runtime benchmark.
## Final Recommendation Style
- Say whether the surface is broadly healthy, needs targeted cleanup, or is risky.
- List the top three fixes first.
- State confidence and what you did not inspect.
- Point to the likely owner layer: presenter/coordinator, state holder, or composition.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |