> For the complete documentation index, see [llms.txt](https://docs.ur.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ur.app/design/readme.md). # Design for UR partners Design and UX guidance for partners building on UR. This section helps you present UR's account inside your product and design your co-branded card. It is written for designers and frontend developers. UR provides a real financial account, not just a wallet: the account layer your users live financially on. The multi-currency card complements the account; it is not the primary product. These guidelines help you position UR correctly, structure your account screens, and design the flows your users will follow. ### User experience How to position UR's account and card, structure your account screens, and design the account creation, KYC, card, and money movement flows. Start with [Introduction](/design/user-experience/introduction.md) for what UR provides and what it is not. ### Cards The artwork specification for your physical and virtual card. See [Co-branded debit card design](/design/cards/co-branded-debit-card-design.md) to download the template, customize your card, and submit it for approval. --- # 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://docs.ur.app/design/readme.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.