Design system file structure in Figma - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Core Components in Design Systems

Which folder in a design system file structure typically contains reusable UI elements like buttons, inputs, and icons?

A Assets

B Documentation

C Tokens

D Components

💡 Hint

Think about where you would find building blocks used repeatedly in designs.

The Components folder holds reusable UI elements such as buttons, inputs, and icons that designers use across projects.

❓ data_modeling

intermediate

Organizing Color Tokens in a Design System

In a design system file structure, where should color tokens be stored for easy maintenance and consistency?

A Assets folder

B Components folder

C Tokens folder

D Documentation folder

💡 Hint

Think about where you keep values that define styles like colors and fonts.

Color tokens are stored in the Tokens folder to centralize style values for consistency and easy updates.

❓ visualization

advanced

Visualizing a Design System File Structure

Which of the following diagrams best represents a clear and scalable design system file structure?

Figma

Root/
├── Tokens/
│   ├── Colors
│   ├── Typography
│   └── Spacing
├── Components/
│   ├── Buttons
│   ├── Forms
│   └── Icons
├── Assets/
│   ├── Images
│   └── Logos
└── Documentation/
    ├── Guidelines
    └── Usage

A

Root/
├── Tokens/
│   ├── Colors
│   ├── Typography
│   └── Spacing
├── Components/
│   ├── Buttons
│   ├── Forms
│   └── Icons
├── Assets/
│   ├── Images
│   └── Logos
└── Documentation/
    ├── Guidelines
    └── Usage

B

Root/
├── Documentation/
│   ├── Buttons
│   ├── Colors
│   └── Typography
├── Components/
│   └── Icons
└── Tokens/

C

Root/
├── Assets/
│   ├── Buttons
│   ├── Colors
│   └── Icons
├── Tokens/
│   └── Typography
└── Docs/

D

Root/
├── Components/
│   ├── Colors
│   └── Buttons
├── Tokens/
│   └── Typography
└── Docs/

💡 Hint

Look for a structure that separates tokens, components, assets, and documentation clearly.

Option A shows a well-organized, scalable file structure separating tokens, components, assets, and documentation clearly.

🔧 Formula Fix

advanced

Identifying a Problem in Design System File Structure

Which option shows a problematic design system file structure that could cause confusion or maintenance issues?

A

Root/
├── Components/
│   ├── Buttons
│   ├── Colors
│   └── Typography
├── Tokens/
└── Docs/

B

Root/
├── Tokens/
│   ├── Colors
│   └── Typography
├── Components/
│   ├── Buttons
│   └── Icons
└── Documentation/

C

Root/
├── Tokens/
│   ├── Colors
│   ├── Typography
│   └── Spacing
├── Components/
│   ├── Buttons
│   ├── Forms
│   └── Icons
└── Documentation/

D

Root/
├── Assets/
│   ├── Images
│   └── Logos
├── Tokens/
├── Components/
└── Documentation/

💡 Hint

Look for folders mixing unrelated items that should be separated.

Option A incorrectly places color and typography tokens inside the Components folder, mixing style values with UI elements, which can cause confusion and maintenance issues.

🎯 Scenario

expert

Scaling a Design System File Structure for Multiple Platforms

You need to organize a design system file structure that supports web, iOS, and Android platforms with shared and platform-specific components. Which structure best supports scalability and clarity?

A

Root/
├── Web/
│   ├── Tokens/
│   └── Components/
├── iOS/
│   ├── Tokens/
│   └── Components/
├── Android/
│   ├── Tokens/
│   └── Components/
└── Documentation/

B

Root/
├── Tokens/
├── Components/
│   ├── Shared/
│   ├── Web/
│   ├── iOS/
│   └── Android/
└── Documentation/

C

Root/
├── Tokens/
│   ├── Web/
│   ├── iOS/
│   └── Android/
├── Components/
└── Documentation/

D

Root/
├── Components/
│   ├── Buttons
│   ├── Inputs
│   └── Icons
├── Tokens/
└── Documentation/

💡 Hint

Consider how to separate shared and platform-specific parts clearly.

Option B organizes components into shared and platform-specific folders under Components, keeping tokens centralized and documentation separate, which supports scalability and clarity.

Practice

1. Why is it important to use numbered folders in a Figma design system file structure?

easy

A. To keep folders organized and maintain a clear order

B. To make the file size smaller

C. To automatically update components

D. To change the color scheme of the design system

Solution

1. Step 1: Understand the purpose of numbered folders

   Numbered folders help keep files in a specific order, making it easier to find and manage items.

2. Step 2: Relate to design system organization

   In a design system, clear order prevents confusion and speeds up work by grouping related items logically.

3. Final Answer:

   To keep folders organized and maintain a clear order -> Option A

4. Quick Check:

   Numbered folders = clear order [OK]

Hint: Number folders to keep things tidy and easy to find [OK]

Common Mistakes:

• Thinking numbering changes file size
• Assuming numbering updates components automatically
• Confusing numbering with design style changes

2. Which of the following is the correct way to name a folder for color styles in a design system file?

easy

A. ColorStyles

B. Colors 01

C. 01 Colors

D. Styles-Colors

Solution

1. Step 1: Check naming conventions for order

   Numbering folders at the start (like '01 Colors') ensures they appear in the correct order.

2. Step 2: Compare options

   01 Colors starts with a number and a clear name, which is best practice for organization.

3. Final Answer:

   01 Colors -> Option C

4. Quick Check:

   Number first, then name = correct folder naming [OK]

Hint: Start folder names with numbers for order [OK]

Common Mistakes:

• Putting numbers after names causing sorting issues
• Using unclear or combined words without spaces
• Skipping numbering and losing order

3. Given a design system file with folders named 01 Colors, 02 Components, and 03 Documentation, what will be the order of these folders in Figma's sidebar?

medium

A. Colors, Components, Documentation

B. Colors, Documentation, Components

C. Components, Documentation, Colors

D. Documentation, Components, Colors

Solution

1. Step 1: Understand folder numbering effect

   Folders with numbers at the start sort in ascending order by those numbers.

2. Step 2: Apply numbering to folder names

   01 Colors comes first, then 02 Components, then 03 Documentation.

3. Final Answer:

   Colors, Components, Documentation -> Option A

4. Quick Check:

   Number order = Colors, Components, Documentation [OK]

Hint: Folders sort by leading numbers ascending [OK]

Common Mistakes:

• Ignoring numbers and sorting alphabetically
• Mixing folder order randomly
• Assuming Figma sorts by last word

4. You notice your design system file has folders named Colors, Components, and Documentation without numbers, but they appear in random order. How can you fix this?

medium

A. Rename folders to all uppercase letters

B. Add numbers at the start of each folder name like 01 Colors

C. Delete and recreate folders in the correct order

D. Change folder colors to match their content

Solution

1. Step 1: Identify cause of random order

   Without numbers, folders sort alphabetically, which may not match desired order.

2. Step 2: Apply numbering to enforce order

   Adding numbers like '01 Colors' forces folders to appear in that numeric order.

3. Final Answer:

   Add numbers at the start of each folder name like 01 Colors -> Option B

4. Quick Check:

   Numbering folders fixes order [OK]

Hint: Number folders to fix random order [OK]

Common Mistakes:

• Thinking uppercase changes order
• Deleting folders wastes work
• Changing colors does not affect order

5. You want to create a design system file structure that separates colors, typography, components, and documentation clearly. Which folder structure below follows best practices?

hard

A. 01 Components
02 Colors
03 Docs
04 Typography

B. Colors
Typography
Components
Docs

C. Components
Colors
Docs
Typography

D. 01 Colors
02 Typography
03 Components
04 Documentation

Solution

1. Step 1: Check for numbering and clear folder names

   01 Colors 02 Typography 03 Components 04 Documentation uses numbers to keep order and full descriptive folder names.

2. Step 2: Verify grouping of related items

   Colors, Typography, Components, and Documentation are grouped separately and clearly.

3. Final Answer:

   01 Colors 02 Typography 03 Components 04 Documentation -> Option D

4. Quick Check:

   Numbered, clear folders = best practice [OK]

Hint: Number and name folders clearly for easy use [OK]

Common Mistakes:

• Skipping numbering causing disorder
• Using unclear or abbreviated folder names
• Mixing unrelated items in one folder