Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, concise workflow with strong sequencing and an explicit validation step, but it repeatedly leans on STYLE_PRESETS.md for the actual CSS foundation and JS controller — a file that is not shipped in the bundle, which caps both actionability and progressive disclosure.
Suggestions
Ship STYLE_PRESETS.md in ./references/ (or inline its viewport-safe CSS foundation and deck-controller JS) so the core executable artifacts the body depends on actually exist.
Add at least one minimal complete HTML skeleton (inline CSS custom properties + keyboard/wheel/touch controller) so the Build step is copy-paste ready without the missing reference.
De-duplicate viewport-fit guidance (Non-Negotiables #2, Step 5, Implementation Requirements) into a single canonical block to tighten conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is directive and lean — lists, a density-limits table, and specific CSS/commands — without explaining HTML/CSS/JS concepts Claude already knows; not score 2 because there is no padded exposition, only mild reinforcement of the core viewport constraint. | 3 / 3 |
Actionability | Concrete specifics exist ("height: 100vh; height: 100dvh; overflow: hidden;", exact viewport test sizes, per-OS open commands, python-pptx), but the core executable artifacts — the viewport-safe CSS foundation and the deck controller class — are deferred to STYLE_PRESETS.md, which is absent from the bundle, so the body is not copy-paste ready. | 2 / 3 |
Workflow Clarity | A clear 7-step sequence (Detect → Discover Content → Discover Style → Build → Enforce Viewport Fit → Validate → Deliver) with an explicit validation checkpoint (step 6 viewport checks + browser automation) and a deliverable checklist; not score 2 because validation is explicit, not merely listed. | 3 / 3 |
Progressive Disclosure | Sections are well organized and references to STYLE_PRESETS.md are clearly signaled one level deep, but that referenced file is not present in the bundle (references/, scripts/, assets/ are empty), so the promised navigation is broken; not score 3 because a key referenced artifact is missing. | 2 / 3 |
Total | 10 / 12 Passed |