The prompt library

The prompt library is the public half of the studio's method: every piece kriyaworks ships is published alongside the exact production prompt that made it — versioned, copyable and free to run. This guide covers how to read a production prompt and how to run one yourself without flattening it into a one-liner.

Where prompts live

Each shipped piece on the work page carries a prompt chip linking to its production prompt. Blog posts embed theirs where the writing refers to one. The library itself goes live with launch — until then, work-page slots are labeled placeholders, and the chips say so rather than linking to prompts that don't exist yet.

Anatomy of a production prompt

• Version header — number, date, and a one-line reason for the latest revision.
• Constraints — the register, composition and refusals: what the piece must never do.
• Tokens — palette values, type families, spacing logic, named exactly.
• References — what the prompt triangulates against, credited.
• Hand-finishing notes — what changed after generation, so the record stays truthful.

Running one

Copy the full text into your agent or model of choice and run it as-is first — before adapting anything, see what the prompt actually produces, and expect a neighbour of the original rather than a clone. Generation is only the first stage of the pipeline that made the shipped piece, and the prompt's hand-finishing notes tell you what the remaining stages contributed.

Adapting one honestly

The right way to adapt a production prompt is to swap the tokens and keep the discipline. Change the palette values to your brand's, the type to your families, the references to your taste — and leave the constraint block intact, because the refusals are where the quality lives. A prompt stripped of its constraints isn't an adaptation; it's a different, worse prompt wearing the same clothes.