Content
28%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 structured but dominated by generic boilerplate and abstract principles with no executable code, concrete examples, or a real workflow. Its single external reference is dangling, which undermines progressive disclosure. It reads more as a topic outline than actionable expert guidance.
Suggestions
Replace generic Instructions/Use-when boilerplate with a concise Quick start containing a copy-paste-ready PHP example (e.g. a generator processing a large dataset, an SPL structure usage).
Turn the Approach principles into a concrete, sequenced workflow with explicit validation checkpoints (e.g. profile -> optimize -> re-measure) instead of an unsequenced list.
Either create resources/implementation-playbook.md with the detailed examples or remove the dangling reference; if keeping it, use a path that matches an actual bundle directory.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Noticeably padded with boilerplate that adds nothing Claude does not already know ("Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes") and circular use/don't-use sections ("Working on php pro tasks", "unrelated to php pro"); not 1 because the Focus Areas list does carry some signal, but several sections are unnecessary. | 2 / 5 |
Actionability | Only high-level hints with no concrete code, commands, or executable examples ("Use generators for large datasets", "Start with built-in PHP functions before writing custom implementations"); it describes principles rather than instructing, and the one detailed reference points to a non-existent file. | 2 / 5 |
Workflow Clarity | The Approach list (1-8) is a set of principles rather than a sequenced workflow, with no validation checkpoints or feedback loops; steps are poorly defined as a process. It is above 1 because items are at least enumerated, but gaps are substantial. | 2 / 5 |
Progressive Disclosure | Has organized sections and a signaled one-level reference ("open resources/implementation-playbook.md"), but the referenced file does not exist and the path uses "resources" rather than any present bundle directory, leaving navigation broken; some structure but the reference is not reliably usable. | 3 / 5 |
Total | 9 / 20 Passed |