proof·of·prompt

← all exhibits

EXH-00sample entry — swap with a real artifact

Proof of Prompt

The site you are reading. One prompt set the goal and the quality bar; the stack, design language, and every shader line followed from it.

  • astro
  • webgl
  • design-system
A field of dots resolving from sparse blue noise into solid amber, left to right
Model
Claude (Fable 5)
Iterations
1
Time to ship
6h
Shipped
Jul 3, 2026

source ↗

The prompt · verbatim

You are a senior developer and designer building a frontend showcase site. I will give you goals and a quality bar, not step-by-step instructions — the "how" is yours to decide.

CONTEXT: I am a solo developer. This site exists to establish my credibility. The method: publish attractive artifacts I have built, together with the exact prompts that produced them. The landing page itself is evidence — the site is the portfolio.

QUALITY BAR: developer and builder audiences should react with "one person built this?". Use current frontend techniques generously but with taste — scroll-driven animation, view transitions, a WebGL hero, cursor-reactive elements, kinetic type. Flashy but never tacky: developers read overproduction as a credibility hit.

YOUR FREEDOMS: choose the stack (anything statically deployable), propose and own the design language, decide which effects belong where. I judge results.

GUARDRAILS: static deploy on Cloudflare. Performance cannot collapse — progressive loading, lazy everything, good Lighthouse. Visitors must be able to read and copy each artifact's prompt. One showcase entry = one file. Perfect mobile. Respect prefers-reduced-motion.

Why it works

This entry is the site’s own receipt. The brief above is the real one — condensed, not embellished.

  • Goal, not steps. The prompt fixes the destination (credibility with a developer audience) and the constraints (static, fast, accessible), then explicitly hands over the how. Models do their best work when the quality bar is sharp and the path is open.
  • The audience is named. “Developers read overproduction as a credibility hit” is one sentence, but it eliminated an entire class of bad design decisions before they happened.
  • Guardrails are testable. Lighthouse, reduced-motion, one-entry-one-file — every constraint can be verified, so the result can be honestly judged.