Content
72%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.
The body is admirably concise and well-structured with a real, one-level-deep reference holding executable code, but it relies on the bundle for actionability and lacks an explicit test-writing workflow with validation checkpoints.
Suggestions
Add a short inline runnable snippet (e.g. a MainDispatcherRule + runTest ViewModel test skeleton) so the body is actionable without opening the reference.
Provide a brief sequenced workflow for writing a test (arrange state → run under runTest/MainDispatcherRule → assert via composeTestRule.onNodeWithTag) with a verification/checkpoint step.
Make the reference link more prominent and labeled (e.g. 'See [Test Rules](references/implementation.md) for runnable MainDispatcherRule and Compose/Hilt rule scaffolding.') to strengthen navigation signaling.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — short bulleted scope/library/isolation lists with no padding or explanations of concepts Claude already knows; every line earns its place. | 5 / 5 |
Actionability | The body names tools (runTest, MainDispatcherRule, createAndroidComposeRule, @TestInstallIn) but the concrete executable code lives in the bundled reference; inline guidance is high-level hints rather than copy-paste-ready examples. | 3 / 5 |
Workflow Clarity | Guidelines are organized by test type with anti-patterns, but there is no sequenced workflow nor validation/verification checkpoint for what are batch/risky test-setup operations; sequence is implied rather than explicit. | 3 / 5 |
Progressive Disclosure | A clear overview structure (Unit/UI/Anti-Patterns/References) with one well-signaled one-level-deep reference to references/implementation.md that exists and holds the executable code; minor gap is that the single link is somewhat buried at the end. | 4 / 5 |
Total | 15 / 20 Passed |