> For the complete documentation index, see [llms.txt](https://design.mirakl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://design.mirakl.com/design/patterns.md). # Patterns

			Cover image
Advanced selection	Allows users to make an informed selection of items with an editable restitution of data.		Advanced Selection Card.png	Advanced selection
	Configure options	Simplify user choices in configuring their settings.	configuration.png	Configure options
Deletion	Protect users from unintended consequences		critical-action-pattern-title-card.png	Deletion
Displaying data	Datalist or datatable, that is the question.		Displaying Data Card.png	Displaying data
	Displaying History	Tracking changes and progression over time.	timeline.png	Displaying history
Errors	Allows users to fix problems themselves through thoughtful messaging.		Errors Card.png	Errors
Forms	Allows users to submit or edit information.		Forms Card.png	Forms
Loading	Reduces load time frustration and makes the page feel more responsive.		Loading Card.png	Loading
	Progressive disclosure	Reveal gradually information to minimize cognitive load for a more intuitive design experience.	progressive-disclosure.png	Progressive disclosure

--- # 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://design.mirakl.com/design/patterns.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.