ChatGPT Prompts for SaaS Web Designers: Build a Design System Naming Convention During a Brand Identity Project

You are a senior product design systems specialist with 8 years of experience building naming conventions and brand identity systems for SaaS companies. Help me build a design system naming convention so I can produce more consistent work across our brand identity project. My situation: - SaaS product type: [B2B tool / B2C app / internal tooling / developer platform / other] - Current naming problem: [e.g., "the same button has four different names in Figma, code, and Jira" / "new designers cannot guess where to find anything"] - Team size: [just me / 2-4 designers / 5+ designers] - Tools in use: [Figma / Storybook / Tailwind / custom token system / other] - Brand identity stage: [building from scratch / mid-project / updating an existing system] - Biggest consistency failure right now: [describe one specific example] - Developer involvement: [none yet / some collaboration / fully embedded in the design process] Deliver: 1. Naming Formula — a simple, memorable convention formula (e.g., [category]-[component]-[variant]-[state]) with examples from your product type 2. Category Taxonomy — a list of the top-level categories your naming system needs, with a plain-language definition of what belongs in each 3. Before and After Examples — five real-world component names rewritten using the new convention so the team can see the difference immediately 4. Naming Decision Guide — a one-page flowchart that helps any team member name a new component correctly without asking a senior designer 5. Token Naming Alignment — how to make sure design token names (colours, spacing, typography) follow the same logic as component names so there are no contradictions 6. Figma Library Setup Instructions — step-by-step instructions for organising your Figma file so the naming convention is reflected in how components are stored and searched 7. Team Adoption Checklist — a short checklist for getting the whole team using the new convention within two weeks, including how to handle the transition from old names 8. Naming Review Process — a lightweight process for approving new component names before they are added to the system, so the convention stays clean as the product grows **Write the naming convention for the newest person on the team — if they can follow it without explanation, it is working.**