Main Figma Rules
π¨ Main Figma Rules
To ensure clarity, consistency, and collaboration in all design files, ADR Studio Management follows strict Figma file organization guidelines.
1. π§± Structure & Grouping
β
Group elements logically β avoid excessive grouping, but ensure components that belong together are grouped (e.g., buttons within a card).
β
Use self-readable labels β avoid names like Group287387292. Use clear names like Button/Primary, Card/ProductInfo, Nav/Header.
β
Frame everything properly β avoid unframed elements floating around the canvas.
2. π· Naming Conventions
β Follow a structured naming system for layers and components:
Component Type / Variant β e.g.,
Button / Primary,InputField / ActivePage Section / Element β e.g.,
Homepage / Hero,Dashboard / Sidebar
β
Use PascalCase or camelCase for consistency:
Good:
MainButton,mainButtonAvoid:
main button,MAIN BUTTON
3. π Page Order & Organization
β Order pages in a clear, top-down hierarchy:
π‘ Guidelines & Components
π Design System
π Homepage
π Dashboard
π± Mobile Screens
π§ Prototypes & Flows
β Use separators between sections:
Prefix with emojis (π) or
---for clarity
4. π§Ύ Macro Labels & Readability
β Use macro labels to visually separate file sections:
Add a βAnnotationsβ frame with explanation of file structure
Use big, clear text for headers (e.g.,
SECTION HEADERabove groups)
5. π§© Components & Variants
β Use Figma components and variants instead of duplicating β Always apply Auto Layout for responsive and scalable designs
6. π¬ Comments & Documentation
β Add Figma comments to explain:
Interactions
Logic
Navigation expectations
β Create a page titled Design Guidelines for deeper documentation
7. π§Ή Version Control & Cleanup
β Regularly clean up:
Unused layers
Old pages
Redundant components
β Use version naming convention:
e.g.,
π Dashboard (v1.2)Archive older versions in a dedicated folder
π Key Takeaways from the Structure
π Top Sections:
π‘ Guidelines & Components β General rules, typography, UI basics
π Design System β Reusable buttons, inputs, modals
π§± Core Design Pages:
π Homepage β Landing pages
π Dashboard β Key content/data
π± Mobile Screens β Mobile/responsive
π§ Prototypes & Flows β Clickable flows, UX paths
π¦ Extra Sections for Structure:
β Separator β β Use to visually split old/new
π Additional Pages (v1.2) β Updated versions
π Archive (Old Versions) β Organized legacy content
Last updated