# Why do Design Patterns help with the application's organization?

The design patterns will help in the structure of your application, because they will serve in the construction of the application, leaving the code leaner, clean and organized, that is, it will be more practical to correct errors and implement new functionalities resulting in a greater longevity application. See the examples of some patterns we recommend

### Architecture Pattern

{% content-ref url="/pages/-L\_mnKMKjQVVMqRqIBZE" %}
[MVC Architecture Pattern](/documentation/guides/app-architecture/suggested-design-patterns/mvc.md)
{% endcontent-ref %}

### Style management pattern

{% content-ref url="/pages/-L\_mnHQn3bY3olIbGVu4" %}
[Template Pattern](/documentation/guides/app-architecture/suggested-design-patterns/builder.md)
{% endcontent-ref %}

### Structural pattern

{% content-ref url="/pages/-L\_mnPd7phTXslbzFmSP" %}
[Data Persistence: DAO Pattern.](/documentation/guides/app-architecture/suggested-design-patterns/dao.md)
{% endcontent-ref %}


---

# 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://learn.totalcross.com/documentation/guides/app-architecture/suggested-design-patterns.md?ask=<question>
```

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.