> For the complete documentation index, see [llms.txt](https://ask.flyp.space/learninghub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.flyp.space/learninghub/ask-flyp/design-packs/how-to-use-design-packs.md). # How to Use Design Packs Use design packs to aid your creative process. Choose from free packs and paid packs to level up your design process. Use design packs to aid your creative process. Choose from free packs and paid packs to level up your design process! Navigate to the studio and enter the packs section of your toolbox. Find your desired pack and press to purchase. Toggle to the purchased tab and press use on the Pack of interest. Select your template and add the Pack designs on to your template. Use the design features to enhance! If you want to learn more about how to use the design features, check out our tutorial here: [Design Feature Tutorial](/learninghub/ask-flyp/flyp-studio/how-to-use-design-features.md) {% 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://ask.flyp.space/learninghub/ask-flyp/design-packs/how-to-use-design-packs.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 `build a script that syncs our docs to a CMS` 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.