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 well-structured and actionable with concrete before/after code examples and specific project standards, but the refinement workflow lacks a concrete verification checkpoint, leaving functionality-preservation as an assertion rather than a checkable step.
Suggestions
Add a concrete validation step to the Refinement Process — e.g., "Run the existing test suite" or "Diff against the original and confirm outputs match" — so "Ensure functionality remains unchanged" becomes a checkable checkpoint rather than an assertion.
Trim the opening "You are an expert code simplification specialist..." paragraph, which restates the description frontmatter and adds little actionable value.
Tighten the Refinement Process steps by pairing each action with a concrete artifact (e.g., "Identify: list modified files via git diff") so the workflow is executable rather than descriptive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean — direct bulleted principles and executable examples without explaining basic programming concepts Claude already knows — but the opening "You are an expert code simplification specialist..." paragraph restates the description and could be trimmed. | 4 / 5 |
Actionability | Concrete, executable TypeScript before/after examples and specific standards (ES modules, function keyword, explicit return types, avoid nested ternaries) give mostly executable guidance, though the process steps remain somewhat high-level. | 4 / 5 |
Workflow Clarity | The six-step Refinement Process is sequenced, but "Ensure all functionality remains unchanged" and "Verify the refined code is simpler" are abstract with no concrete validation checkpoint (e.g., run tests, review diff), so checkpoints are missing rather than explicit. | 3 / 5 |
Progressive Disclosure | A single, well-organized file with clear section headers (Refinement Principles, Refinement Process, Examples) and no nested references; it is slightly over 50 lines with inlined examples that could optionally be split out, keeping it just short of a 5. | 4 / 5 |
Total | 15 / 20 Passed |