A design bible documents critical user interface and user experience mistakes. It also records the rules created to fix these mistakes. This document helps prevent repeating past design errors.
By Pawan Nayar · from the LLOS AI Learning record
A design bible documents critical user interface and user experience mistakes.
It also records the rules created to fix these mistakes. This document helps prevent repeating past design errors.
A team creates a 'design bible' or 'mistake log'. This document tracks serious user interface and user experience errors. It explains what went wrong. The document also lists new rules established to correct these problems. A team refers to this log often to avoid making the same mistakes again.
A developer and a designer created a complex navigation menu. Users found it very confusing. The team added this mistake to their design bible. They then created a new rule: 'Navigation menus must have no more than five main items.' This rule prevents future complex menus.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
An AI model must always read a specific set of files. These files include 'mistakes_and_lessons.md'.
A developer must read specific API policy files before writing any code that makes external API calls. This prevents common mistakes.
A developer must estimate the token count of the AI model's output before making an API call. If the estimated output is more than 6000 tokens, the developer should split the request.
A developer must look for direct text changes. A developer must also look for code that creates file names or paths from parts.
A design bible documents critical user interface and user experience mistakes. It also records the rules created to fix these mistakes. This document helps prevent repeating past design errors.