Content
68%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 a tight, highly actionable rulebook: concrete code patterns, explicit ordering conventions, and quantitative thresholds, with supporting rationale properly moved to a one-level-deep reference file. The main weaknesses are the absence of a validation/verification step in the workflow (no build-or-test checkpoint for a behavior-preserving refactor) and minor redundancy between the guidelines, workflow, and notes sections.
Suggestions
Add an explicit verification step to the workflow, e.g. '8. Verify: build the project and run existing tests to confirm behavior and layout are unchanged.'
Trim the 'Notes' section, which restates guidelines already covered, and drop the duplicated header snippet from the 'Avoid' example in section 3.
Promote the 'references/mv-patterns.md' pointer into its own clearly labeled section with a markdown link describing what the reader will find there.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Prescriptive bullets and Prefer/Avoid code pairs with no padding about concepts Claude already knows — every section is actionable guidance. Minor trims are possible (the 'Avoid' example in section 3 repeats the header VStack snippet from the 'Prefer' example, and 'Notes' largely restates earlier guidelines), which keeps it below anchor 5. | 4 / 5 |
Actionability | Concrete, syntactically valid Swift throughout: the '_viewModel = State(initialValue: SomeViewModel(dependency:))' init pattern, the '.task(id: searchText)' reload example, an explicit property-ordering list, and hard thresholds ('~300 lines', 'iOS 17+'). Minor gaps — helpers like 'FilterChip' and 'documentsListContent' are referenced but not defined, so examples are not fully copy-paste ready. | 4 / 5 |
Workflow Clarity | The 7-step Workflow is clearly sequenced but has no validation checkpoint: there is no 'build/test to confirm behavior is unchanged' step, and step 7 ('Keep behavior intact') is a constraint rather than a check. Sequence present, checkpoints missing matches anchor 3; not 4 because the only checkpoint is implicit. | 3 / 5 |
Progressive Disclosure | Well-sectioned body with rationale correctly offloaded to 'references/mv-patterns.md', which exists in the bundle and is one level deep. The reference is a single bare path on the last line of 'Notes' rather than a clearly signaled dedicated section — a minor organization gap that keeps it below anchor 5. | 4 / 5 |
Total | 15 / 20 Passed |