Content
46%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-organized and token-efficient with clear use/skip conditions, but it fails on its core job: instructions are abstract directives with no executable specifics, and progressive disclosure is broken — the sole referenced file does not exist while all actual bundle files are unreferenced and undiscoverable. Fixing the reference paths and grounding the instructions in the real reference/asset files is the highest-impact change.
Suggestions
Fix the broken reference: replace the nonexistent "resources/implementation-playbook.md" with the real bundle paths and enumerate them in the Resources section (references/ef-core-best-practices.md, references/dapper-patterns.md, assets/repository-template.cs.template, assets/service-template.cs.template).
Ground the Instructions in concrete, per-task guidance, e.g., "For data access: prefer Dapper for hot paths (see dapper-patterns.md) and scaffold repositories from assets/repository-template.cs.template; configure with IOptions + validation."
Add explicit validation checkpoints to the workflow, e.g., "Run dotnet build and the unit/integration test suite after changes; verify EF Core queries with logging before considering the task done."
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — short bullet lists with no explanation of concepts Claude already knows. Two minor issues keep it from a 5: the description sentence is repeated verbatim under the H1, and the time-sensitive "(2024/2025)" / "modern best practices" dating is not isolated in a deprecation or versioning section, which the guidelines penalize. | 4 / 5 |
Actionability | The Instructions are high-level directives — "Define architecture boundaries, modules, and layering", "Apply DI, async patterns, and resilience strategies" — with no concrete steps, commands, or code for any of the named technologies. This matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute'; it avoids a 1 only because specific technology names (DI, Redis, EF Core, Dapper, IOptions) give actionable starting points. | 2 / 5 |
Workflow Clarity | The four instruction bullets imply a rough lifecycle sequence (define boundaries → apply patterns → validate data access → add tests/observability), and validation is mentioned, but there are no explicit checkpoints, commands, or feedback loops (e.g., build/test/verify steps). This is 'steps listed but checkpoints missing or implicit', above the poorly-defined-steps level of 2 but below the explicit-validation level of 4. | 3 / 5 |
Progressive Disclosure | Scored against the actual bundle: the body's only reference, "resources/implementation-playbook.md", does not exist (there is no resources/ directory), while the four real bundle files — references/dapper-patterns.md, references/ef-core-best-practices.md, assets/repository-template.cs.template, assets/service-template.cs.template — are never mentioned. Navigation to the detailed content is impossible via a broken path plus undiscoverable files, matching 'minimal structure ... references buried'; it is not a 1 because the body itself has clear sections and is not a monolithic wall of text. | 2 / 5 |
Total | 11 / 20 Passed |