# Working in Figma

## File and Structure Organization

Structure the Figma to have one Master Components file as a separate project. Each Brand will have its own project folder with the Market variations as separate foundations files.

<figure><img src="/files/SslufoGodaXS1hz6OWhG" alt=""><figcaption></figcaption></figure>

As you begin to design screens, use the master components that are connected to the foundations of the desired brand.&#x20;

<figure><img src="/files/k7ym1lwHampDSx5bmj48" alt=""><figcaption></figcaption></figure>

As we can swap foundation libraries, each brand can have their own pages built with the common components overwritten with their specific foundations library:

<figure><img src="/files/lhDosgztYs7E5q1wTqQm" alt=""><figcaption></figcaption></figure>

## Foundations

We create brand dedicated libraries with all supported tokens stored as styles.

<figure><img src="/files/DKCeNzLnGlGBUSGqQWcZ" alt=""><figcaption></figcaption></figure>

It is crucial to apply the same style names to all foundations libraries in order to be able to swap between them.

<figure><img src="/files/eYJwKjaunRXGn7EpH6aw" alt=""><figcaption></figcaption></figure>

We can also include interchangeable components for other customizable assets such us logotypes, illustrations or icons.

<figure><img src="/files/eTUTMsZWihg1dOQ0BHPO" alt=""><figcaption></figcaption></figure>

## Master Components

We create a common library to manage the components for all brands from one place.

<figure><img src="/files/MuoLGFLBw5EZ4AIiv5MC" alt=""><figcaption></figcaption></figure>

We apply the styles (tokens) to all our components.

<figure><img src="/files/eISRbExWbKDb4zBu7CCw" alt=""><figcaption></figcaption></figure>

It’s crucial to craft all master components with auto-layout in order to change styles without issues.

<figure><img src="/files/SKmSeKBbfkCGEXR4wJw5" alt=""><figcaption></figcaption></figure>


---

# 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://dsplaybook.farcostudio.com/part-2-the-process/documentation-3.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.
