How E-commerce Design Leads Can Build a Naming Convention When Presenting a Design Concept Using ChatGPT

You are a senior design systems lead with 12 years of experience building design system naming conventions and client presentation frameworks for e-commerce design teams where a poorly named component library is the hidden cause of scope creep — because clients request changes to "the button" without understanding that the design system has 14 button variants, each with a specific purpose, and every change to the conceptual "button" actually requires a decision about which of the 14 variants is in scope. Help me build a design system naming convention so I can reduce scope creep and create a naming architecture that makes scope boundaries visible to clients during a design concept presentation without requiring a design system education session before every client meeting. My situation: - E-commerce client type and project scope: [e.g., "a mid-market fashion e-commerce brand — the design project covers a new product listing page, a checkout flow, and a homepage redesign, with a Figma component library of 120 components serving all three deliverables"] - Scope creep pattern: [e.g., "the client is requesting changes to the primary CTA button on the checkout flow after approval, not realizing that the checkout CTA button and the product listing page CTA button are the same component in the design system — a change to one will cascade to all 14 instances across the project unless the scope is explicitly defined"] - Current naming system: [e.g., "components are named by appearance — large-blue-button, small-grey-card, hero-banner-desktop — giving the client no indication that changing the large-blue-button on checkout affects the same component on the product listing page"] - Client presentation format: [e.g., "a weekly Figma prototype review call — the client clicks through a prototype, makes change requests verbally, and the design lead notes them without a structured scope assessment"] - Design brief clarity problem: [e.g., "the design brief approved at project start defined pages and layouts but not components — the client approved the checkout flow design without understanding that the CTA button on that page is a shared component with 13 other uses across the project"] - Team implementation impact: [e.g., "the design team of 4 spends an average of 3 hours per week on undocumented scope changes that were not included in the project estimate — annualized, this is 156 hours of uncompensated work across the team"] - Naming convention adoption requirement: [e.g., "the naming convention must work in Figma's component naming system, be understandable to a client with no design background in a 5-minute overview, and be adoptable by the 4-person team within one sprint"] Deliver: 1. A design system naming convention framework — a four-part naming structure for each component covering the component category (layout, navigation, interactive, or content), the component function (what the component does in the user flow), the component scope (which pages or flows it appears on), and the variant (the specific appearance or state), with a completed example for each of the five most common e-commerce component types 2. A scope visibility naming approach — a specific naming decision that makes the shared-component status visible to a non-designer client during a Figma review, covering the naming prefix that signals a global component (affecting all pages), a flow component (affecting one checkout or product flow), and a page component (appearing only on one page type), with the explanation to give a client who asks what the prefix means 3. A client-facing component glossary — a one-page document listing the 20 most important components in the project with their naming convention name and a plain-English description of what each component is and where it appears, formatted for a client to reference during a design review call without requiring design vocabulary 4. A scope change assessment process — a structured response for when a client requests a change to a named component, covering the 3-question assessment (how many instances does this change affect, are all affected instances in the approved project scope, and does the client understand the cascade effect), the change request documentation format, and the scope boundary email template for changes that fall outside the approved scope 5. A Figma component rename process — a step-by-step protocol for the 4-person design team to rename the current 120 components without breaking prototype links, covering the rename order (rename leaf components before parent components), the version control commit message format, and the QA check after renaming to confirm no broken links in the prototype 6. A design concept presentation script for scope introduction — a 5-minute segment to add to the weekly Figma review call, covering the three naming prefixes and what they mean for scope, the three examples of how a client change request cascades through the component library, and the one question the design lead asks before processing any change request ("would you like to see all the places this change would apply before we confirm it?") 7. A scope change log template — a shared Figma comment or Google Sheet the design lead maintains throughout the project, recording each change request with the date, the component name and scope impact, the client's understanding of the cascade effect (confirmed or not confirmed), and the decision (in scope, new scope, or deferred), producing an audit trail that protects the design team if a scope dispute arises at project close 8. A naming convention adoption sprint plan — a one-sprint implementation plan for the 4-person design team, covering the team alignment session on the naming framework (90 minutes), the component audit to identify the 20 highest-priority components for renaming (4 hours), the renaming sprint (6 hours across the team), and the client glossary production (2 hours), producing a fully renamed component library and a client-ready glossary within one 2-week sprint **Write every naming convention component and presentation script assuming the design lead is managing a client who is both engaged and scope-challenged — every naming decision must make the business consequence of a cascade change visible in the component name itself, and every client communication tool must give the design lead a professional way to surface scope boundaries without making the client feel restricted or penalized for making reasonable requests.**