Content
82%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 highly actionable, well-structured procedure: copy-paste-ready code for both flows, package tables, package-manager detection, a no-op pre-check, and a conservatively guarded cleanup step. The main gaps are token efficiency (repeated boilerplate between the two entry-file examples and unsectioned version pins) and the absence of a final verification step after wiring.
Suggestions
Collapse the two `main.tsx` examples: describe the Apps API variant as 'identical to the Classic `main.tsx` but without `<DuneAuthProvider>`' and show only the single differing JSX block, saving ~20 lines of repeated boilerplate.
Add a final verification step (e.g. 'start the dev server with the detected package manager and confirm `fusionOpenPlugin` opens the app inside Fusion with the authenticated client resolving') to close the workflow with a validation checkpoint.
Isolate version-sensitive details like `@cognite/app-sdk >= 0.5.1` into a single 'Version requirements' or 'Notes' line instead of restating them inline in both Step 1 and Step 4, making future version bumps a one-line edit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — decision tables, full code blocks, and one-line rationales ('base: "./" — required for Fusion iframe deployment') with no padding or explanation of concepts Claude already knows. It misses anchor 5 because the second `main.tsx` example repeats the classic-flow boilerplate nearly verbatim (could be 'same as Classic minus DuneAuthProvider'), and bare version pins ('@cognite/app-sdk >= 0.5.1', stated twice) are time-sensitive details not isolated in a versions/deprecated section. | 4 / 5 |
Actionability | Everything is executable: complete copy-paste-ready `main.tsx`/`App.tsx`/`vite.config.ts` blocks, package tables split runtime vs dev with the exact install commands per detected package manager ('pnpm add', 'npm install', 'yarn add', '-D / --save-dev'), and precise ordering constraints ('manifestCspPlugin() must be first'). | 5 / 5 |
Workflow Clarity | Steps 1–5 are clearly sequenced, and Step 1 is a real pre-flight checkpoint (detect an existing valid setup → no-op) with Step 5 guarded by 'If unsure, leave it and flag to the user' — appropriately cautious for a step that deletes code. It falls short of anchor 5 because there is no post-change validation (e.g. run the dev server / confirm the Fusion handshake) or error-recovery loop after wiring. | 4 / 5 |
Progressive Disclosure | The body is well-sectioned per step and per flow, and there are no broken or nested references (no bundle files exist, and none are linked). It does not reach anchor 5 because at ~185 lines covering two distinct flows, the per-flow code and vite details are prime candidates for a one-level-deep reference file rather than the under-50-line single-file case the exception rewards. | 4 / 5 |
Total | 17 / 20 Passed |