Content
73%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 strong body: excellent workflow sequencing with validation feedback loops, good executable examples, and a well-organized progressive disclosure structure. The main drags are token padding (keyword list, persona/footer, version pins) and a broken cross-reference inside one bundle file.
Suggestions
Delete the 'Knowledge Reference' section — it only enumerates technologies Claude already knows and adds no actionable value.
Trim the persona intro sentence and author footer, and move version pins like 'Apollo Federation 2.5+' into a dedicated versioning or deprecation note.
Fix the broken cross-reference in migration-from-rest.md: 'federation-guide.md' should be 'federation.md'.
Add the exact composition-check command to workflow step 3 so the validation checkpoint is directly executable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean checklists and code, but padded with a 'Knowledge Reference' keyword dump ("Apollo Server, Apollo Federation 2.5+, GraphQL SDL, DataLoader, GraphQL Subscriptions, WebSocket, Redis pub/sub, schema composition...") that names technologies Claude already knows, a persona intro ("Senior GraphQL architect specializing in..."), an author/footer section, and version pins ("Apollo Federation 2.5+" twice) placed outside any deprecation/version note. | 3 / 5 |
Actionability | Concrete, executable examples cover the common cases (federation SDL, DataLoader context setup with ordering comment, createComplexityRule validation config), but "Run schema composition check" names no command (e.g., rover supergraph compose) and the DataLoader example is a fragment without surrounding setup. | 4 / 5 |
Workflow Clarity | Six clearly sequenced steps with explicit validation checkpoints and error-recovery feedback loops: "If composition fails: review entity @key directives, check for missing or mismatched type definitions across subgraphs, resolve any @external field inconsistencies, then re-run composition" and "If complexity threshold is exceeded: identify the highest-cost fields, add pagination limits, restructure nested queries, or raise the threshold with documented justification". | 5 / 5 |
Progressive Disclosure | The body is a clean overview with a reference table pairing each of six real files with a 'Load When' condition, all one level deep. However, migration-from-rest.md cross-references 'graphql-architect/references/federation-guide.md', which does not exist (the actual file is federation.md), creating a minor navigation gap. | 4 / 5 |
Total | 16 / 20 Passed |