po4yka/RIPDPI / .agents/skills/compose
compose
VerifiedJetpack Compose API guidance (state, modifiers, navigation, theming) plus a scored RIPDPI audit. Use for generic Compose API questions or an audit. Not for RIPDPI conventions (see android-compose-patterns).
references/report-template.md
View on GitHub# Report Template
When the user requests a persistent audit artifact, write it to their chosen path or `build/reports/compose/compose-audit-<YYYY-MM-DD>.md` using this structure.
**Citation rule:** every finding (Critical Findings *and* per-category Evidence bullets) must include a `References:` line with at least one URL pointing to the official documentation rule the code violates. Use the URLs in `references/canonical-sources.md` and `references/scoring.md`. A finding without a citation should not appear in the report — that's the credibility lever this audit relies on.
```markdown
# Jetpack Compose Audit Report
Target: [repo path or module path]
Date: [YYYY-MM-DD]
Scope: [modules or directories audited]
Excluded from scoring: [paths or globs treated as samples / tests / previews]
Confidence: [High | Medium | Low]
Overall Score: [X/100]
Design system: RipDpiThemeTokens (custom wrapper over MaterialTheme) -- see `.agents/skills/material-3/` for design scoring
## Scorecard
| Category | Score | Weight | Status | Notes |
|----------|-------|--------|--------|-------|
| Performance | X/10 | 35% | [fail / needs work / solid / excellent] | [short note] |
| State management | X/10 | 25% | [fail / needs work / solid / excellent] | [short note] |
| Side effects | X/10 | 20% | [fail / needs work / solid / excellent] | [short note] |
| Composable API quality | X/10 | 20% | [fail / needs work / solid / excellent] | [short note] |
## Critical Findings
List the most important findings first. Each finding should include:
- severity
- why it matters
- 2-4 concrete file examples
- the likely fix direction
Example format:
1. **Performance: repeated expensive work happens inside composition**
- Why it matters: [brief reason]
- Evidence: `path/a.kt:42`, `path/b.kt:117`
- Fix direction: [brief recommendation]
- References: <https://developer.android.com/develop/ui/compose/performance/bestpractices>
## Category Details
### Performance — [X/10]
**What is working**
- [positive evidence]
**What is hurting the score**
- [problem 1]
- [problem 2]
**Evidence**
- `path/to/file1.kt:LL` — [brief reason] · References: <https://developer.android.com/...>
- `path/to/file2.kt:LL` — [brief reason] · References: <https://developer.android.com/...>
### State Management — [X/10]
**What is working**
- [positive evidence]
**What is hurting the score**
- [problem 1]
- [problem 2]
**Evidence**
- `path/to/file1.kt:LL` — [brief reason] · References: <https://developer.android.com/...>
- `path/to/file2.kt:LL` — [brief reason] · References: <https://developer.android.com/...>
### Side Effects — [X/10]
**What is working**
- [positive evidence]
**What is hurting the score**
- [problem 1]
- [problem 2]
**Evidence**
- `path/to/file1.kt:LL` — [brief reason] · References: <https://developer.android.com/...>
- `path/to/file2.kt:LL` — [brief reason] · References: <https://developer.android.com/...>
### Composable API Quality — [X/10]
**What is working**
- [positive evidence]
**What is hurting the score**
- [problem 1]
- [problem 2]
**Evidence**
- `path/to/file1.kt:LL` — [brief reason] · References: <https://developer.android.com/...>
- `path/to/file2.kt:LL` — [brief reason] · References: <https://developer.android.com/...>
## Prioritized Fixes
1. [Highest leverage fix]
2. [Second fix]
3. [Third fix]
4. [Optional follow-up]
## Known Open Items
Cross-reference against `.agents/skills/compose-performance/SKILL.md` quick-wins checklist.
Items listed here are tracked debt, not new findings:
- [item from compose-performance quick-wins, if still open]
## Notes And Limits
- [state if only part of the repo was audited]
- [state if confidence is medium/low]
- [state if some categories had limited surface area]
- Weight choice: [default 35/25/20/20, or note any deviation and why]
- Renormalization: [list any N/A categories and the renormalized weights]
- Compiler diagnostics used: [yes / no — link to the Compose Compiler reports if generated; "no" means stability claims are inferred from source, not measured]
## Suggested Follow-Up
- Run `material-3` audit if the repo also shows likely design-system or Material 3 problems.
```
## Tone
- Keep the tone strict and direct.
- Avoid filler praise.
- Give credit only where the codebase actually demonstrates good patterns.
- Prefer a few strong findings over dozens of weak bullets.
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: 471k | 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: 471k | 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: 471k | 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 |