A long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts.
NewMaintained
Automatic
◆Frontend / UI pack
Last verified 8/2/2026
What it changes
Passed 6 of 22 test cases with the skill, and 17 of 22 without it.
Without skill75%
With skill25%
Checks it passed that the model alone missed
The artifact tag uses the identifier attribute rather than slug.
The CSS max-width for the article container is set between 680px and 720px.
The CSS max-width constraint on the main article body is set between 680px and 720px.
and 4 more in the full report
3 fixed8 passed either way3 still failing8 broke
Pass-rate lift
-50 pp
Tokens
+20%
Agent turns
0%
Response time
+11%
Model gemini-3.6-flashMeasured 8/2/2026v111 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
I need a comprehensive, magazine-style article on the future of generative design in modern software development. Please generate a complete, standalone HTML page containing the full article layout. Wrap the HTML result in an `<artifact>` tag with identifier, type, and title attributes. Provide exactly one sentence before the artifact tag and put nothing at all after it.
What was checked, without and with the skill
Checked
Without skill
With skill
The CSS max-width for the article container is set between 680px and 720px.
Missed
Passed
The pull quote CSS styling uses the logical property border-inline-start rather than border-left.
Missed
Passed
The pull quote, hero, body, headline, or related grid elements include data-od-id attributes.
Missed
Passed
case-01 · gemini-3.6-flash · 8/2/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md50 linessingle file
Blog Post Skill
Produce a single long-form article page — editorial layout, no chrome.
Workflow
Read the active DESIGN.md (injected above). Lean into the typography
tokens — long-form is 70% type, 20% image, 10% chrome.
Pick the topic from the brief and write a real article — at least 600
words across 4–6 H2 sections. No lorem ipsum.
Sections, in order:
Masthead — small wordmark + 4–6 nav links, plain.
Article header — category eyebrow, headline (display token, large),
deck (1–2 sentence subhead), author name + role + date.
Hero image — a 16:9 placeholder block using a DS-tinted gradient or
solid fill (no external images). Add a 1-line caption underneath.
Body — alternating prose paragraphs with at least:
1 pull quote (large display type, accent rule on the inline-start edge so the layout flips correctly under dir="rtl").
1 figure (image placeholder + caption).
1 list (numbered or bulleted).
1 inline blockquote.
Author footer — author avatar (initials in a circle), bio paragraph.
Related — 3 cards linking to other posts. Each card: tiny image
block, title, 1-line excerpt, date.
Write a single HTML document:
<!doctype html> through </html>, CSS inline.
Article body uses the DS body font, centered, max-width per DS layout
rule (typically 680–720px).
Drop caps (first-letter) only if the DS mood is editorial / serif —
skip on tech-y DSes.
data-od-id on the headline, hero, body, pull quote, related grid.
Self-check:
Type hierarchy is unambiguous — H1 is clearly the headline; H2s are
section dividers; pull quotes do not compete with H1.
Line length 60–75 chars for body prose.
Accent appears at most twice (eyebrow + pull-quote rule, or one link).
The page reads like a magazine, not a marketing landing.