Content
61%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 delivers focused, well-structured conceptual guidance with illustrative code examples and no unnecessary padding. It is weaker on actionability and workflow clarity because the guidance is diagnostic/conceptual rather than a concrete executable procedure with explicit checkpoints.
Suggestions
Add a short, explicit procedure for applying the guidance (e.g., 1) locate rules coupled to a component, 2) mark as Domain Logic candidate, 3) extract into a UI-free domain module, 4) verify the module has no component/UI imports) with a validation checkpoint confirming the extracted domain code has zero UI dependencies.
Make at least one code example complete and copy-paste runnable (with imports/types) so the extraction pattern is unambiguous, rather than illustrative snippets.
Tighten the 'For some people... For others...' paragraph, which explains term ambiguity at a length that could be trimmed without losing the core directive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and focused on value-add term distinctions (Business Rules vs Domain Logic vs Presentation Logic vs UI Logic) plus a directive to stop using 'Business Logic'; it avoids explaining basics Claude already knows, with only minor instances of explanatory padding around the term ambiguity. | 4 / 5 |
Actionability | Provides concrete directives ('treat it as a Domain Logic candidate worth isolating') and illustrative tsx/ts snippets, but the code examples lack imports/types and are illustrative rather than copy-paste executable, and the identification/extraction procedure is left partly to judgment, matching the 'some concrete guidance but incomplete' anchor. | 3 / 5 |
Workflow Clarity | The content presents a logical progression of principles (distinguish by layer, identify candidates, isolate, don't confuse physical separation with layer separation) but is not a sequenced procedural workflow with explicit checkpoints; no destructive/batch operations are present so the validation cap does not apply. | 3 / 5 |
Progressive Disclosure | The body is a single self-contained document with clear section headers (Core Principle, Distinguish Them by Layer, Not Every Code Extraction Is Layer Separation) and no nested or buried references; no bundle files exist, and the ~75-line content is well-organized with only minor organization gaps. | 4 / 5 |
Total | 14 / 20 Passed |