Content
92%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 a strong, actionable integration guide with a clear sequenced workflow, executable examples, and well-organized progressive disclosure into three real reference files. The main improvement would be de-duplicating the version-pinning rationale that recurs across several sections.
Suggestions
State the @cognite/reveal 4.36.0 pinning rationale once in Dependencies and reference it from Critical Rules and the Verification Checklist rather than re-explaining it in each.
Tighten the Prerequisites bullet contrasting @cognite/dune vs @cognite/app-sdk; the legacy --classic scaffolds detail is tangential to the core integration task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and assumes Claude's competence, but the @cognite/reveal 4.36.0-vs-4.35.3 pinning rationale is restated across the Dependencies table, the note below it, Critical Rules, and the Verification Checklist, which could be consolidated. | 4 / 5 |
Actionability | Fully executable guidance: a complete copy-paste TSX controller example, a concrete pnpm install command, exact package versions, and specific vite.config dedupe entries cover the common cases. | 5 / 5 |
Workflow Clarity | A clearly ordered 9-step Integration Workflow with an explicit typecheck/build validation step (step 9) and a dedicated Verification Checklist providing a feedback checkpoint; not a destructive/batch context so no cap applies. | 5 / 5 |
Progressive Disclosure | Well-structured overview with one-level-deep, clearly signaled references to real bundle files (csp-and-fixes.md, implementation.md, vite-config.md), each linked contextually with a description of what it contains. | 5 / 5 |
Total | 19 / 20 Passed |