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.
The body is a strong, actionability-first reference: fully executable examples for every scenario, Satori-specific gotchas (no default fonts, flex-only layout, no grid), and clear section organization. Weakest spots are mild redundancy in the 'Key Patterns' section and the absence of any progressive-disclosure split despite the CSS reference list being a natural candidate for a separate file.
Suggestions
Trim the 'Key Patterns' section to points not already stated earlier (e.g. keep only the decision rules like 'use next/og in Next.js' and '1200×630 is standard') to reduce repetition.
Move the CSS supported/not-supported lists into a references/ file (e.g. references/css-support.md) and link to it, so the main file stays a lean overview and progressive disclosure improves.
Add a short 'Which approach should I use?' decision list near the top (Next.js convention file vs. route handler vs. standalone Satori) to make the workflow sequence explicit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly dense, Satori-specific facts and executable code with no padding about concepts Claude already knows. Minor trimming is possible: 'Key Patterns' restates points already made ('display: flex everywhere', 'load fonts explicitly', '1200×630'), and the two Next.js sections overlap, which keeps it at anchor 4 rather than 5. | 4 / 5 |
Actionability | Every section ships copy-paste-ready, executable code: install commands, a full edge route handler, a convention-based opengraph-image.tsx file, a standalone satori() call with font config, edge-runtime font fetching, URL parameter extraction, and img usage. This matches anchor 5 — fully executable examples covering the common cases. | 5 / 5 |
Workflow Clarity | Content is organized by scenario (Next.js route → convention files → standalone) with an explicit decision rule ('Use next/og in Next.js projects'), and no destructive or batch operations exist so the validation cap does not apply. It sits below anchor 5 only because there is no explicit up-front 'pick your path' sequencing; the reader assembles the flow from section order. | 4 / 5 |
Progressive Disclosure | The body references no bundle files (references/, scripts/, assets/ are absent) and everything is inline with well-signaled, well-organized sections plus one-level-deep external links under 'Official Resources'. It matches anchor 4 (good structure, minor organization gaps): the ~25-line CSS supported/not-supported reference list is the main content that could arguably live in a separate reference file, preventing a 5. | 4 / 5 |
Total | 17 / 20 Passed |