> For the complete documentation index, see [llms.txt](https://docs.deepwork.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepwork.studio/teams-departments/deep-work-studio/roles/prototype-designer-1/designer-skill-tree/prototyping/secondary-screens.md). # Secondary Screens Typically you'll start the additional screens towards the end of the first day or on the second day of prototyping. With the decisions made above, and the level of detail applied to the first screen, creating the rest of the design should be much more straight forward. ### **1. Delegation** If there is another expert on the sprint, this is the stage to split the remaining tasks. For example, you may split the remaining screens to be designed. Hand over your main screen as the visual direction and explain how subsequent screens should be implemented. If there is a junior designer or someone with less visual fidelity, it may be necessary to design components but not details on the remaining screens before handing them over. ![In this Hummingbot prototype, I've created the first line of a table. In this case I've made it a component. An assistant can then copy the component and fill in the details to show other available markets.](/files/-MTk5upz3TGbRBWYA5KL) ### **2. Create all the Screens** Put all the screens together, prioritising getting the first version of them all. Use any remaining time to continuing iteration on the design. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.deepwork.studio/teams-departments/deep-work-studio/roles/prototype-designer-1/designer-skill-tree/prototyping/secondary-screens.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.