A structured framework for managing Figma design files, ensuring scalability, traceability, and clarity across the design workflow.

Overview

This guide defines how our Figma design files are structured, named, and versioned across the Design System, Exploration, and Final Design files.

It ensures consistency between designers, reduces friction during handoffs, and creates a clear path between Figma → Jira → delivery.

Project Layers

File(s) Purpose Primary Owner
🧩 Design System Library Central source of truth for components, tokens, and patterns. Product Designer
🎨 Exploration Files In-progress design work for new features or iterations. Product Designer,
UX Designer,
UI Production Designer
 Final Designs Reviewed, approved, and ready-for-handoff designs. Product Designer

1. Design System Library

File: [ Link to Figma design system file ]

Page Naming:

00. Overview

01. Tokens & Styles

02. Components

03. Patterns

04. Templates

Component Naming Convention:

Category / Subcategory / State

Examples:

Button / Primary / Default

Form / Input / Error

Card / User / Compact