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.
A lean, highly actionable body that defers detail appropriately to a single rules file and external docs, with excellent progressive disclosure. The main weaknesses are the missing post-fix verification step and a small amount of repetition around the read-the-rules directive.
Suggestions
Add a validation step after fix=true, e.g. '5. Run typecheck/build and exercise the affected views to confirm no state was lost in the migration' — the batch delete-and-rewire of state currently has no checkpoint.
Include one minimal executable snippet (a co-located search-params.ts + useQueryState usage) so the fix pattern is copy-paste ready rather than fully deferred to the external rules file.
State the read-the-rules-file directive once (e.g. in Steps only) instead of three times across Context, References, and Steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense, project-specific guidance that assumes Claude's competence (no explanation of nuqs, React Query, or Zustand) with load-bearing caveats. Minor trims possible: the directive to read '.claude/rules/sim-url-state.md' appears three times (Context, References, Steps) and fix specifics repeat between the anti-pattern list and the Steps section. | 4 / 5 |
Actionability | Names exact APIs and replacements ('useQueryState/useQueryStates bound to a search-params.ts', 'sort via createSortParams + useUrlSort, search via useDebouncedSearchSetter', 'delete the replaced state + sync effects'). Not 5: no code/commands, and the actual wiring patterns and decision table are deferred to the external rules file, leaving minor gaps. | 4 / 5 |
Workflow Clarity | A clear 4-step sequence (read rules/docs → analyze scope → decide correct home → apply or propose fixes), but fix=true performs batch, destructive edits (deleting state and sync effects across a scope) with no validation or verification step such as running a typecheck/build afterwards — capped at 3 per the batch-operations rule. | 3 / 5 |
Progressive Disclosure | Well-organized sections (Context, References, Anti-patterns, Steps) with clearly signaled, one-level-deep references — each reference is annotated with exactly what it contains (decision framework, parsers, options, server-side cache). No nesting, no buried pointers, and no bundle bloat. | 5 / 5 |
Total | 16 / 20 Passed |