Most guidelines end up as a PDF nobody opens. How we write rules short enough to remember and clear enough to follow. The goal is not a beautiful document; it is a team that makes the same good decision without asking.

Every guideline should answer a question someone actually asks: which colour for a button, how big a headline can get, when to use photography. If a page does not answer a real question, it does not belong in the document.

We collect those questions in the first week of every project, then build the guidelines around them instead of around the assets.

“A rule nobody can remember is just a suggestion with a page number.”

— Prisma Studio

02 — Keep every rule to one line

Short rules survive. Long rules get skimmed, misread and quietly ignored. In practice that means:

  • One sentence per rule, with one example next to it
  • Do and don’t pairs instead of paragraphs of explanation
  • Tokens and templates linked straight from the page
  • A single owner who keeps the document current