Component set best practices in Figma - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a component set in Figma?

A component set is a group of related components organized together to manage variations like states or sizes efficiently.

beginner

Why should you use descriptive naming for components in a set?

Descriptive names help you and your team quickly find and understand component variations, improving collaboration and reducing errors.

intermediate

How does organizing components into sets improve design consistency?

It ensures all variations share the same base style and updates apply across all related components, keeping the design uniform.

intermediate

What is the benefit of limiting the number of variants in a component set?

Limiting variants keeps the set manageable and easier to maintain, avoiding confusion and performance issues.

beginner

How can component sets improve collaboration in a team?

They provide a single source of truth for UI elements, making it easier for everyone to use consistent components and reduce duplicated work.

What is the main purpose of a component set in Figma?

A To write code automatically

B To create unrelated components in one file

C To export images faster

D To group related component variations together

Component sets group related variations like button states or sizes, making management easier.

Which naming style is best for components in a set?

A Random names

B Descriptive and consistent names

C Only numbers

D Very long sentences

Descriptive and consistent names help identify components quickly and reduce confusion.

What happens if you have too many variants in a component set?

A Performance may slow and management becomes harder

B Nothing changes

C Figma automatically deletes extras

D The set becomes easier to use

Too many variants can slow down Figma and make the set difficult to maintain.

How do component sets help maintain design consistency?

A By allowing different styles for each component

B By duplicating components often

C By sharing base styles across variants

D By ignoring design rules

Component sets share base styles so updates apply to all variants, keeping designs consistent.

Why are component sets important for team collaboration?

A They provide a single source of truth for UI elements

B They confuse team members

C They prevent sharing files

D They increase file size unnecessarily

Component sets ensure everyone uses the same components, improving teamwork and reducing duplicated effort.

Explain how organizing components into sets can improve your design workflow and consistency.

Think about how changes in one place affect all related components.

Describe best practices for naming and managing component sets in Figma.

Good naming and organization help your team find and use components easily.

Practice

1. What is the main purpose of a component set in Figma?

easy

A. To export images faster

B. To create unrelated components in one file

C. To group similar components with different states or versions

D. To add animations to components

Solution

1. Step 1: Understand component sets

   Component sets group similar components that have different states or versions, like buttons with different colors or sizes.

2. Step 2: Identify the main purpose

   This grouping helps keep designs consistent and easy to update across the project.

3. Final Answer:

   To group similar components with different states or versions -> Option C

4. Quick Check:

   Component sets = group similar components [OK]

Hint: Component sets group variants of one element type [OK]

Common Mistakes:

• Thinking component sets are for unrelated components
• Confusing component sets with export tools
• Assuming component sets add animations

2. Which of the following is the correct way to name variants inside a component set in Figma?

easy

A. Button1 and Button2

B. Primary-Hover and Primary-Default with dashes

C. HoverState and DefaultState without slashes

D. Primary / Hover and Primary / Default

Solution

1. Step 1: Understand variant naming conventions

   Figma recommends using clear variant names separated by slashes to indicate states, like "Primary / Hover".

2. Step 2: Compare options

   Options without slashes or with generic names like "Button1" are less clear and not best practice.

3. Final Answer:

   Primary / Hover and Primary / Default -> Option D

4. Quick Check:

   Use slashes for variant names [OK]

Hint: Use slashes to separate variant names clearly [OK]

Common Mistakes:

• Using generic names like Button1, Button2
• Not using slashes to separate variant states
• Using dashes instead of slashes

3. Given a component set with variants named "Size / Small", "Size / Medium", and "Size / Large", what happens if you add a new variant named "Color / Red" to the same set?

medium

A. It creates a new variant group unrelated to size, causing confusion

B. It merges with existing size variants automatically

C. It renames all variants to "Color / Red"

D. It deletes the previous size variants

Solution

1. Step 1: Understand variant grouping in component sets

   Variants in a set should focus on one property, like size or color, to keep sets clear.

2. Step 2: Analyze adding a different variant property

   Adding "Color / Red" to a size-focused set creates a new variant property, which can confuse the set's purpose.

3. Final Answer:

   It creates a new variant group unrelated to size, causing confusion -> Option A

4. Quick Check:

   Keep variant sets focused on one property [OK]

Hint: Keep variant sets focused on one property [OK]

Common Mistakes:

• Assuming variants merge automatically
• Thinking variants rename others
• Believing variants delete previous ones

4. You created a component set but notice that some variants have inconsistent naming like "Primary-Default" and "Primary / Hover". What is the best way to fix this?

medium

A. Rename all variants to use consistent slash-separated names

B. Delete the variant with the dash and recreate it

C. Ignore the inconsistency as it does not affect usage

D. Merge the variants into one component

Solution

1. Step 1: Identify naming inconsistency problem

   Inconsistent variant names cause confusion and make it harder to use the component set properly.

2. Step 2: Apply best practice for naming

   Renaming all variants to use consistent slash-separated names improves clarity and usability.

3. Final Answer:

   Rename all variants to use consistent slash-separated names -> Option A

4. Quick Check:

   Consistent naming improves component set clarity [OK]

Hint: Fix variant names to use consistent slashes [OK]

Common Mistakes:

• Deleting variants unnecessarily
• Ignoring naming inconsistencies
• Merging variants incorrectly

5. You have a button component set with variants for size (Small, Medium, Large) and state (Default, Hover, Disabled). What is the best practice to organize these variants in Figma?

hard

A. Create separate component sets for size and state variants

B. Use two variant properties named "Size" and "State" with clear values for each

C. Combine size and state into one variant property with all combinations

D. Use generic names like "Variant1", "Variant2" for all variants

Solution

1. Step 1: Understand variant properties in component sets

   Figma allows multiple variant properties to organize variants clearly, such as "Size" and "State".

2. Step 2: Apply best practice for organizing variants

   Using two variant properties with clear values keeps the set manageable and easy to use.

3. Final Answer:

   Use two variant properties named "Size" and "State" with clear values for each -> Option B

4. Quick Check:

   Use multiple variant properties for clarity [OK]

Hint: Use multiple variant properties for complex variants [OK]

Common Mistakes:

• Creating separate sets for related variants
• Combining all variants into one property
• Using unclear generic variant names