> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns.md).

# 4 Design patterns

Get started using design patterns

<figure><img src="https://1280346931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3hE0Uutsp0Izues1Vdfb%2Fuploads%2Fgit-blob-581550650aa4faf3e1d67c511c23bfbdaa3b24ff%2FHow%20our%20patterns%20work%203%20(1).png?alt=media" alt=""><figcaption><p>A diagram showing how the design patterns fit into the service patterns</p></figcaption></figure>

## **Considerations for choosing different patterns**

### **Step-by-step guide to help you pick the right patterns for your service:**

* [Identify Service Needs](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.1-user-centred-design.md): use the [GovStack playbook](/implementation-playbook/0.9.0/govstack-implementation-playbook/adopt-govstack/design-and-delivery/user-journeys.md) to understand the key interactions in your service.
* Map the user journey: Break down the user journey into phases like registration, information collection, appointments, feedback, and messaging. Identify the steps users take in each flow. [Consider the technology choices available to you](/overview/23q4/govstack-ui-ux-guidelines/3-service-design-good-practice-guidelines/3.4-technology-choices.md).
* Choose user flows: Identify the patterns (task-focused page types) needed for each part of your user journey.
* Select page templates: User flow patterns often include several page templates. Start with existing patterns for user flows. For unique requirements, you may need to mix and match individual templates.


---

# 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://specs.govstack.global/overview/23q4/govstack-ui-ux-guidelines/4-design-patterns.md?ask=<question>&goal=<user_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.