Content
77%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 highly actionable with a complete hero component, concrete class tables, and a well-sequenced workflow with validation. Its main weakness is progressive disclosure: it inlines reference-style content and never links to the four existing reference files or the scaffolder script that accompany it.
Suggestions
Replace the inlined Design Style Reference, Copy Frameworks, and SEO Checklist sections with concise summaries that point to references/copy-frameworks.md, references/seo-checklist.md, and references/landing-page-patterns.md, surfacing the existing bundle files.
Reference scripts/landing_page_scaffolder.py in the Generation Workflow (e.g., step 7) so Claude knows it can scaffold components instead of hand-writing each one.
Trim the introductory paragraph and the 'Not lorem ipsum — actual copy that converts' line to remove content that duplicates the frontmatter description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient reference material (style table, copy frameworks, component example, checklists), but the intro repeats the description and 'Not lorem ipsum — actual copy that converts' is marketing fluff that could be trimmed. Not a 5 due to these minor instances of padding; not a 3 because the bulk earns its tokens. | 4 / 5 |
Actionability | Provides a copy-paste-ready Hero component and exact Tailwind class sets, array shapes, and a JSON-LD injection snippet, but other section patterns (features, pricing, testimonials) are prose rather than full code and rely on undefined shadcn components (<Button>, <Accordion>). Mostly executable with minor gaps, so 4 rather than 5. | 4 / 5 |
Workflow Clarity | The 'Generation Workflow' is a clearly sequenced 7-step process with an explicit validation checkpoint (step 6 'Validate against SEO Checklist') and a feedback loop ('Fix any gaps inline — do not skip items'), matching the anchor for explicit validation and error-recovery loops. | 5 / 5 |
Progressive Disclosure | Section structure is present, but content that belongs in separate files (Design Style Reference table, Copy Frameworks, SEO Checklist) is inlined while the four existing reference files (conversion-patterns.md, copy-frameworks.md, landing-page-patterns.md, seo-checklist.md) and the scaffolder script are never referenced or signaled. Fits 'some structure, references not signaled, content that should be separate is inline'; not a 2 because structure is reasonable, not a 4 because the bundle files are entirely unsurfaced. | 3 / 5 |
Total | 16 / 20 Passed |