> ## Documentation Index
> Fetch the complete documentation index at: https://docs.make-pretty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Review and improve a design system

> Look through what Pretty built, test it on a few slides, and fix what's off by asking Pretty in the design system's chat. A design system that matches your brand is what makes every deck come out right.

Pretty builds a design system from your files, but you know your brand best. Ten minutes of review
after the build pays off in every deck that follows: chats use the design system on every turn, so
a wrong colour or a missing font shows up everywhere, and a fix shows up everywhere too.

## Look through it

Open **Studio** in the [web editor](https://editor.make-pretty.com), click your design system, and
go through each section of its page.

| Section | What to check |
| - | - |
| **Colours** | Every colour is one of yours, and what it says each is for matches how your decks use it. |
| **Typography** | Every family your decks use is there, and the type styles match your decks. **Upload font** adds a missing family; a missing one renders in a fallback font. |
| **Masters and layouts** | It's your current template, its layouts look right, and the one new decks start from is the default. **Make default** changes it. |
| **Elements** | The elements Pretty reuses (chevrons, number badges, tables) are yours, not from a client deck or a one-off slide, and each says when to use it. |
| **References** | The instructions Pretty reads before it builds each kind of slide or element. Read them like a style guide. |

> [!TIP]
>
> The quickest check is a real one. Start a chat with the design system and ask for three slides
> you build all the time ("an agenda", "a two-column comparison", "a chart with a takeaway"). Put
> them next to one of your own decks: wrong colours, fonts or spacing point straight at what to fix.

## Fix it with Pretty

Click **Edit with Pretty**. A chat opens beside the page, already set up to change the design
system, and the page shows each change as soon as Pretty saves it.

Say what's wrong the way you'd tell a colleague:

* "Chart colours are navy, then grey, then light blue. Never use the orange."
* "Titles are 28 pt and always a full sentence that states the takeaway."
* "Use the two-column layout for comparisons, not the table."
* "The number badges are too big. Use the small ones from the Q3 deck."

Ask "what can I change here?" and Pretty explains.

> [!TIP]
>
> One change per message, and point at an example when you can: a slide number, a deck, or a
> screenshot of what's wrong. Then make the same test slide again to see the difference.

## Edit it yourself

Admins can also change parts by hand: upload a font under **Typography**, add or upload a master
under **Masters and layouts**, and add or edit an element's usage note under **Elements**. Members
can try changes on their own copy with **Make your own copy**, without affecting anyone else.

## Keep it current

* **New template?** Add it under **Masters and layouts**, then click **Update design to this
  master**. Built without a template? **Improve with your PowerPoint template** builds it again
  from yours.
* **One brand, one design system.** For a client or a sub-brand, create a separate design system
  rather than adding its files to yours. See [Create a design system](https://docs.make-pretty.com/design-systems/create.md).
* **Make it the default.** **Make default** in the design system's menu makes every new chat and
  deck start with it, so nobody has to remember to pick it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.