# Website Designer ## **Responsibilities** * Understand the collaborative vision of the website * Create a visual prototype, which can act as the basis for a user test. It needs to look indistinguishable from a real product and have a flawless user experience, aimed at visualising the main intentions of the team. * Guide the team's decisions to create a cohesive user journey and usable information architecture. * In case the client doesn't have a set visual identity or Sytelguide, your task will also be to create a matching visual identity, which will make the product appealing. Projects follow a set (but flexible) process to manage expectations and produce high-quality results for the client team. Please familiarize yourself with our principles and general prototyping guidelines: {% content-ref url="/pages/Rf9LtTzAxVOE21ezMUrk" %} [Prototyping Principles](/tools/prototyping-principles.md) {% endcontent-ref %} {% hint style="info" %} Check out this [medium article](https://medium.com/deep-work-studio/how-to-prototype-anything-in-one-day-3d81a7f68e10) by Andrej Berlin on *how to prototype anything in one day* for ease of reference. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.deepwork.studio/teams-departments/deep-work-studio/roles/prototype-designer-1.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.