Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A high-quality, expert-level audit skill: every category pairs concrete, version-aware rules with a mandatory, verified reference file, and the Modifier.Node example is fully executable. Main weaknesses are moderate redundancy (repeated MANDATORY declarations, a trailing IMPORTANT restatement) and inlining of detailed scope-guard rules that belong in the references.
Suggestions
Consolidate the per-category 'MANDATORY: read references/... before flagging' blocks into the single global 'Mandatory Reference Read' workflow step, since each category heading already links its reference file.
Add an explicit final workflow step for verifying fixes (e.g., 'confirm improvements with Macrobenchmark or JankStats before reporting') to close the validation gap in the audit workflow.
Move the long @Stable/@Immutable scope-guard sub-bullets into references/state-and-stability.md, keeping only the decision rule inline, to slim the body toward a true overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is densely packed with expert, version-specific guidance (Compose 1.13 computedStateOf, Strong Skipping trade-offs, snapshot read overhead) and wastes no tokens on basics Claude already knows, fitting the 'efficient; minor instances that could be trimmed' anchor. The 6x repeated 'MANDATORY ... MUST read' blocks (redundant with the workflow's global mandate) and the trailing '<br />' / 'IMPORTANT' restatement keep it below 5. | 4 / 5 |
Actionability | Guidance is fully concrete and executable: exact APIs (Modifier.graphicsLayer, drawWithCache, Path.rewind(), MutableLongSet, packInts), version gates (Compose 1.13+, < 1.12), specific replacement patterns ('contentType = { _, item -> item.type }', 'mutableStateOf(list, neverEqualPolicy())'), and a complete copy-paste-ready Kotlin Modifier.Node migration example covering the common cases. | 5 / 5 |
Workflow Clarity | A clear sequence is present (foundational prerequisites -> exhaustive scan of all 7 categories 'rather than stopping after the first issue found' -> mandatory reference read before flagging or editing), with the read-before-flag gate acting as an explicit checkpoint. Not 5 because verification (benchmarking) is only mentioned inside individual rules rather than as an explicit final validation step with a feedback loop. | 4 / 5 |
Progressive Disclosure | Seven well-organized categories each link to a real bundle file (all referenced paths verified to exist in references/), one level deep with strong 'read before flagging' signaling. Not 5 because the body itself inlines substantial rule detail (e.g., multi-line @Stable/@Immutable scope-guard bullets) that a purer overview-plus-references split would move into the reference files. | 4 / 5 |
Total | 17 / 20 Passed |