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

# Add skills and guardrails

Skills are instructions Figr follows while it designs. Use them for compliance rules, accessibility standards, anti-dark-pattern guidelines, or your team’s own way of working. Turn a skill on for your whole organisation and every project follows it, whoever is designing.

## Always on or when relevant

Each skill has a mode that decides when Figr uses it.

* **Always on:** Figr applies the skill to every request. Use it for rules that never bend.
  * “All text must meet WCAG AA contrast.”
  * “Never pre-select consent or marketing checkboxes.”
  * “Show fees before the confirm button, never after.”
* **When relevant:** Figr applies the skill only when the request matches it. Use it for rules that belong to one area of your product.
  * “When designing checkout, show the order total on every step.”
  * “When designing onboarding, keep it to three steps or fewer.”
  * “When designing for mobile, use bottom sheets instead of modals.”

## Create a skill

**1. Open Skills and create a new skill**

Give it a clear name, like **Payments compliance**, and a short description of what it covers.

![Screenshot 2026 10 21 At 2 41 58 AM](https://mintcdn.com/figr-1af7ae64/GFl9SXL01D1q0Z7d/images/Screenshot-2026-10-21-at-2.41.58-AM.png?fit=max\&auto=format\&n=GFl9SXL01D1q0Z7d\&q=85\&s=db5a63bb880928fa4d1ae6ad2d8d4599)

**2. Write the rules**

List each rule as a short, specific statement Figr can check a design against.

> [!TIP]
>
> Write rules you could check with a yes or no. “Fees are visible before confirm” works better than “be transparent about fees”.

**3. Choose the mode**

Pick **Always on** or **When relevant**.

![Screenshot 2026 10 21 At 2 42 47 AM](https://mintcdn.com/figr-1af7ae64/GFl9SXL01D1q0Z7d/images/Screenshot-2026-10-21-at-2.42.47-AM.png?fit=max\&auto=format\&n=GFl9SXL01D1q0Z7d\&q=85\&s=afcaa536f947ce4c55a50cf02d5d3176)

**4. Turn it on for your organisation**

Skills are enabled automatically org-wide, every team member can use or apply the skills you've created to their respective projects.

## Example: anti-dark-pattern rules for payments

A fintech team wanted every payment flow to be clear and honest, no matter who designed it. They added these rules as an **Always on** skill, enabled for the whole organisation:

* Payment details, fees and exchange rates always have strong visual hierarchy. They are never hidden behind a toggle, an accordion or small text.
* Every payment has an explicit confirmation step that shows the final amount.
* Toggles and defaults never pre-select the option that costs the user more.

![Image](https://mintcdn.com/figr-1af7ae64/MWugUlEIv8OG0sG0/images/image-32.png?fit=max\&auto=format\&n=MWugUlEIv8OG0sG0\&q=85\&s=6da6e7fa9908535117d6896baf520a8b)

Now every design Figr creates for the team follows these rules, without anyone having to repeat them in a prompt.


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