> 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/getting-started/welcome-to-roma/design-principles.md).

# Design principles

Roma, our design system with its guiding principles, is a lever to help us achieve our goal of building the most robust, high-speed, and reliable ecommerce platform.

> *“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”*
>
> *Antoine de Saint-Exupéry.*

## KISS (Keep it Simple, Stupid)

We want to make it easy for our users. Do not add steps when they're not necessary; remove pages and reduce the number of clicks. **Make it light, period.**

## Make it inclusive <a href="#id-25c56b" id="id-25c56b"></a>

No matter who they are, where they are, or what platform they’re using we want to offer our users the best user experience possible. A localized and accessible experience is at the core of what we do.

## Make it conversational&#x20;

Provide an immersive experience where the information goes between the platform and the users.

## Build trust <a href="#id-0862b9" id="id-0862b9"></a>

Running businesses relying on ‌Mirakl technology. We must provide a seamless and frictionless experience, supported by a robust technology with no downtime, without bugs & fast.

## Focus on efficiency

Mirakl experiences should help people achieve their goals quickly, accurately, and with less effort. We focus on speed and simplicity, but we value productivity even more.

## Build for real people

Our products are designed to fulfill the needs of our users, not our own. \
This involves a deep understanding of our users' desires and requirements, allowing us to deliver optimal solutions.&#x20;

We commit to create tangible business value for our customers through innovation while addressing their challenges. We assess the performance of our launches and continue refining them until we meet our success criteria.

## Inspired by data <a href="#id-53aed4" id="id-53aed4"></a>

Where relevant, we will build smart, data-driven features to allow business teams to learn quickly and operate efficiently.

## Build a Minimum Loveable Product <a href="#id-27a7aa" id="id-27a7aa"></a>

Of course, we want to build quickly and fail fast, but we also don't want to put too much burden on the user's side. A Minimum Loveable Product (MLP) is an initial offering that users love from the start.


---

# 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/getting-started/welcome-to-roma/design-principles.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.
