Instructions and interpretation
The challenge
One deliberately narrow task. Every experiment keeps its instructions and generation history.
Capybara on a hoverboard
capybara-hoverboard-v1
Build an animated capybara riding a hoverboard using only HTML, CSS, and JavaScript.
Deliver a single self-contained HTML file with all CSS and JavaScript inline. Do not use external libraries, external image assets, external fonts, or network requests. Inline SVG, CSS drawing, and canvas are allowed.
The result should visibly show a capybara riding a hoverboard, with animation that makes the scene feel alive. Do not include audio.
Return only the HTML source, without explanations or Markdown code fences.
SHA-256 e6b955ce7c23afabd2adf2115467e7b6c213ac2cab2a7596886ca71ad827fe1c
From pelicans to capybaras
Simon Willison's pelican-riding-a-bicycle experiments inspired this challenge. Our version asks models to animate a capybara on a hoverboard in a single HTML file.
Collection protocol
- Start a fresh conversation or request with no previous user conversation.
- Send the fixed prompt exactly once. Record known system instructions separately.
- Do not edit, retry, or repair a canonical one-shot output.
- Record provider, identifier, interface, timestamp, exposed settings, and known tool use. Leave unknown conditions unknown.
- Save the full response and extracted HTML before publication.
- Keep additional attempts as separate records in the same series. Publish all collected attempts or disclose incomplete publication.
Revised and tool-assisted examples require prominent labels and their full user-turn transcript. A changed instruction creates a new challenge version.
What this gallery cannot tell you
- One task cannot establish overall model quality.
- Individual runs can vary.
- Model aliases and chat products can change.
- Publication may not represent all possible attempts.
- Preview restrictions may affect behavior.
Preview policy restricted-html-v1
Derived previews are byte-for-byte copies of extracted UTF-8 HTML. They are served on a separate origin under an enforced HTTP Content Security Policy and an iframe sandbox. Originals remain downloadable plain text on the gallery origin.
Inline scripts and styles can run. External resources, fetch requests, nested frames, forms, popups, and top navigation are restricted. No frame messages are trusted.
Sandboxing is not absolute network or CPU isolation. Scripts may navigate their own frame or block a browser. Curator-reviewed execution is opt-in, and suspect outputs remain evidence with execution disabled.
SHA-256 protects recorded integrity. It does not prove authorship or scientific validity.