Every screen in this language answers one question — “Could the set at home decode it?”
The full bible for the broadcast page — 16 sections, authored end to end: color, typography, the signatures, components, motion, and voice.
No bible ships on our word. A blind agent rebuilt each screen from the bible alone and had to pass. Every gate is published.
You should be looking at your first lawful screen within fifteen minutes of checkout. Not a hope — a procedure. Put the bible in a folder, open your coding agent, and paste this:
Read ONLY the file BIBLE.md in this folder — no other reference, no other file. Build one screen: a service-status page for a small web app. Where my asks conflict with the bible, the bible wins — and handle the conflict the way the bible's own voice would.
Already shipped something? The bible restyles as readily as it builds — open your agent in your own repo, drop BIBLE.md at the root, and paste this instead:
Read ONLY the file BIBLE.md at the root of this repo — no other reference. Restyle one existing screen of this product to the bible's law — tokens, type, components, motion, voice. Where my current styles conflict with the bible, the bible wins — and handle the conflict the way the bible's own voice would.
Run the commission above. If your first screen doesn't come out lawful — if it breaks the bible's own printed rules — reply to the download email (or write howdy@designbible.ai) within 30 days. Full refund. You keep the bible.
Tested with Claude Code: every gate on the receipts wall was passed by Claude agents building blind, from the bible alone. The bible is plain text and stack-agnostic — the starter is Next.js, and the same law carries to Tailwind, Vite, or whatever you already run. The pledge covers whichever agent you use.