Content
86%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 well-structured, actionable audit workflow that correctly delegates detailed rules to a single reference file and gates its only destructive action behind user confirmation. Minor redundancy in severity definitions and a missing pre-report verification step keep it just short of perfect.
Suggestions
Consolidate the severity definitions: keep them only in the '## Severity' section and reference it from the report-format template to remove the duplicated inline definition.
Add an explicit verification step before reporting, e.g. 'Re-read each flagged line against the matching rule in design-rules.md to confirm it is a true violation, not a false positive.'
Optionally note that findings should be grouped by file before producing the report, making the multi-file batch output easier to scan.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence (no explanation of F#, DaisyUI, or design concepts), but severity definitions appear twice — once in the report-format summary template and again in the '## Severity' section — which could be trimmed. | 4 / 5 |
Actionability | Provides a copy-paste-ready command ('git diff --name-only HEAD~3 -- ...'), specific file paths to read (references/design-rules.md, src/Client/DesignSystem.fs), an enumerated 8-category checklist, and a concrete report-format template with an example table row. | 5 / 5 |
Workflow Clarity | A clear 6-step numbered sequence (identify files, load rules, read DesignSystem.fs, check each file, report, offer to fix) with the destructive auto-fix gated behind explicit user confirmation; the only gap is no explicit false-positive verification checkpoint before reporting findings. | 4 / 5 |
Progressive Disclosure | The body is a concise overview that delegates the full rule set to a real, one-level-deep reference ('Read references/design-rules.md for the full rule set'), keeping the workflow and report format inline — content is appropriately split and easy to navigate. | 5 / 5 |
Total | 18 / 20 Passed |