> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/ux-laws-principles/behaviour/jakobs-law.md). # Jakob's Law Users prefer your site to work the same way as all the other sites they already know. Users spend most of their time on other sites. This means that users prefer your site to work the same way as all the other sites they already know. Design for patterns for which users are accustomed. Jakob's law suggests people are more comfortable and familiar with things they've encountered before. It means that when you're designing something, like a website or an app, it's a good idea to stick to familiar and common design patterns. People tend to prefer things that work in ways they're used to, so following established design conventions can make your product easier to use because it feels familiar to users. It's like following the road everyone else takes instead of creating a new, confusing path. #### Further Viewing {% embed url="" %} {% embed url="" %} #### Further Reading {% embed url="" %} {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/behaviour/jakobs-law.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.