> For the complete documentation index, see [llms.txt](https://docs.madrix.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.madrix.dev/hands-on-tutorials/2.-quick-prompts.md).

# 2. Quick prompts

Use this page to request **quick changes** to an already generated app. Paste **one prompt at a time**. Validate in Preview. Repeat.

{% hint style="info" %}
Want to improve the quality of requests? See [Prompt tips](/hands-on-tutorials/1.-prompt-tips.md).\
Want complete templates by domain? Use [Prompt Templates](/hands-on-tutorials/4.-prompt-templates.md).
{% endhint %}

### Placeholders (replace before sending)

* `{{Entidade}}`: name of the entity (e.g.: `Contract`).
* `{{novoCampo}}`: name of the field (e.g.: `signatureDate`).
* `{{NomeRelatorio}}`: name of the report.
* `{{evento}}`: name of the event (e.g.: `order.created`).
* `{{campo}}`: field used for search.
* `{{texto|numero|data|moeda|boolean|enum}}`: choose a type.

### UI and identity

<details>

<summary>Add languages</summary>

```
Add support for the following languages: pt-BR and en-US.
```

</details>

<details>

<summary>Customize visual identity (theme)</summary>

```
Update the app's visual identity.
Set primary color: #0EA5E9.
Set secondary color: #111827.
```

</details>

<details>

<summary>Background image on the login screen</summary>

```
On the login screen, add a background image.
Requirements:
- Responsive (desktop and mobile).
- Maintain contrast and form legibility.
- Do not impact the authentication flow.
```

</details>

### Security and permissions

<details>

<summary>Add roles and permissions (RBAC)</summary>

```
Implement RBAC with these roles:
- Admin: full access.
- Manager: sees everything for the team.
- Operator: creates/edits only records they created.
- Reader: read-only.

Rules:
- Operator cannot delete.
- Manager can reassign the responsible user.
- Create a simple screen for managing roles/permissions (Admin only).
```

</details>

### Structure (modules, entities and lists)

<details>

<summary>Add a module + menus</summary>

```
Create a new module called: Contracts.
Add menus and minimal screens (list + create/edit + detail) for the module.
```

</details>

<details>

<summary>Add field to an entity (with validation + UI)</summary>

```
In the {{Entidade}} entity, add the field {{novoCampo}}.
Type: {{texto|numero|data|moeda|boolean|enum}}.
Rules:
- Required.
- Minimum/maximum value: {{if applicable}}.
Update the forms and list to display the field.
```

</details>

<details>

<summary>Add query/filter (list)</summary>

```
In the {{Entidade}} list, add filters:
- status (multi-select)
- period (start and end date)
Add search by {{campo}}.
```

</details>

### Rules and reports

<details>

<summary>Business rule (status workflow)</summary>

```
For {{Entidade}}, implement a status workflow.
Enum: New | In Progress | Review | Completed.
Allowed transitions:
- New -> In Progress
- In Progress -> Review
- Review -> Completed
Block any transition outside this order.
Record change history (author + date/time + fromStatus + toStatus).
```

</details>

<details>

<summary>Simple report (with filters)</summary>

```
Create a report called: {{NomeRelatorio}}.
Metric: {{e.g.: total by status, total by month, top 10}}.
Filters: period and status.
Display on a basic dashboard.
```

</details>

### Integrations

<details>

<summary>Integration (webhook + log + reprocess)</summary>

```
Add an integration via webhook to the event: {{evento}}.
Requirements:
- Endpoint configurable by environment (Dev/Staging/Prod).
- Log payload, status and errors.
- Allow reprocessing of failed events (Admin only).
```

</details>

{% hint style="warning" %}
Avoid requesting “everything” in a single prompt. If the scope grows, break it into 3–5 changes.
{% endhint %}


---

# 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.madrix.dev/hands-on-tutorials/2.-quick-prompts.md?ask=<question>&goal=<endgoal>
```

`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.