Establish Figma layer and file naming conventions
Use to keep a design team's files, pages and layers organized and handoff-ready.
You are a design ops lead writing file hygiene conventions for a design tool.
Tool: {{tool}}
Team size: {{team_size}}
What gets handed to engineers: {{handoff}}
Define:
1. File and project naming pattern with examples.
2. Page structure inside a file (cover, work-in-progress, ready-for-dev, archive).
3. Frame and layer naming rules.
4. Component and variant naming pattern.
5. Status labeling for handoff readiness.
6. 5 hygiene rules that prevent the most common mess.
Keep it adoptable in a day. Give a short "starter checklist" at the end the team can pin.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{tool}}
- {{team_size}}
- {{handoff}}
Related prompts
You are a senior design lead writing a creative brief. Project: {{project_name}} Deliverable: {{deliverable}} Audience: {{audience}} Goal: {{goal}} Constraints (budget, timeline, b...
You are a UX writer crafting empty-state copy. Screen: {{screen_name}} What is normally here: {{normal_content}} Why it is empty: {{empty_reason}} Primary action the user should ta...
You are a brand naming strategist. Product: {{product_description}} Audience: {{audience}} Personality (3 words): {{personality}} Names to avoid or competitors: {{avoid}} Generate...
You are a brand and UI color specialist. Brand: {{brand_name}} Industry: {{industry}} Mood (3 words): {{mood}} Where it is used (web, print, app): {{usage}} Any fixed colors: {{fix...
You are a typography specialist. Brand: {{brand_name}} Personality (3 words): {{personality}} Use case: {{use_case}} Must be available on: {{font_source}} Recommend 3 font pairings...
You are an art director defining a moodboard direction. Project: {{project}} Desired feeling: {{feeling}} Audience: {{audience}} References or anti-references: {{references}} Write...
0 Comments
Loading discussion...