Gearset

This rule flags Apex code and metadata that do not follow consistent or standardized naming conventions across the org. While names may technically work, inconsistency in how classes, methods, fields, or other elements are named leads to confusion, poor developer experience, and increased risk of errors. ​

Clayton classifies this as a Warning because inconsistent naming doesn’t break functionality, but it undermines the clarity, structure, and maintainability of your codebase especially in collaborative or fast-scaling teams.

Reduces readability - making code harder to navigate and understand.

Slows down development - as teams spend time deciphering naming intent.

Leads to duplication - when developers unknowingly recreate similar objects or logic.

Impacts collaboration - especially across admins, developers, and architects

Makes onboarding harder - as naming patterns don’t clearly reflect purpose or context.

- Reduces readability - making code harder to navigate and understand.
- Slows down development - as teams spend time deciphering naming intent.
- Leads to duplication - when developers unknowingly recreate similar objects or logic.
- Impacts collaboration - especially across admins, developers, and architects
- Makes onboarding harder - as naming patterns don’t clearly reflect purpose or context.

Standard naming acts as a contract across the team it communicates structure, intent, and ownership.

 Code Reviews flags inconsistently named:

Apex Classes and Triggers – e.g., mixing <code>CamelCase</code>, <code>snake_case</code>, or abbreviations.

Methods – unclear names like <code>process1()</code> or overly generic names like <code>doStuff()</code>.

Test Classes – not using the <code>_Test</code> suffix or not matching the class they support.

Variables – using shorthand, unclear prefixes, or inconsistent casing.

Custom Fields &amp; Objects – missing suffixes like <code>__c</code>, using unclear abbreviations, or inconsistent word order.

Aura Properties – mismatched with their bound templates or controllers.

- Apex Classes and Triggers – e.g., mixing <code>CamelCase</code>, <code>snake_case</code>, or abbreviations.
- Methods – unclear names like <code>process1()</code> or overly generic names like <code>doStuff()</code>.
- Test Classes – not using the <code>_Test</code> suffix or not matching the class they support.
- Variables – using shorthand, unclear prefixes, or inconsistent casing.
- Custom Fields &amp; Objects – missing suffixes like <code>__c</code>, using unclear abbreviations, or inconsistent word order.
- Aura Properties – mismatched with their bound templates or controllers.

 Establish and enforce naming conventions across:

Apex - use <code>PascalCase</code> for class names (<code>AccountService</code>), <code>camelCase</code> for variables and methods (<code>calculateDiscount</code>).

Custom Metadata - use full words and consistent suffixes (<code>Renewal_Status__c</code>).

Test Classes - match the target class name and append <code>_Test</code> (<code>AccountService_Test</code>).

Triggers - use <code>ObjectTrigger</code> format (<code>AccountTrigger</code>).

Objects - use descriptive names with consistent prefixing for custom apps or modules.

- Apex - use <code>PascalCase</code> for class names (<code>AccountService</code>), <code>camelCase</code> for variables and methods (<code>calculateDiscount</code>).
- Custom Metadata - use full words and consistent suffixes (<code>Renewal_Status__c</code>).
- Test Classes - match the target class name and append <code>_Test</code> (<code>AccountService_Test</code>).
- Triggers - use <code>ObjectTrigger</code> format (<code>AccountTrigger</code>).
- Objects - use descriptive names with consistent prefixing for custom apps or modules.

Use naming patterns that clearly indicate purpose, object, and action.

 Consistent naming conventions reduce confusion and help your codebase scale with your team. Apply clear, standardized naming across all elements to improve readability, reduce duplication, and make collaboration smoother. Code Reviews flags inconsistencies as a Warning to promote a clean, well-structured Salesforce environment.

Inconsistent Naming Conventions

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

Inconsistent Naming Conventions

Overview

Why this matters

What Triggers This Rule

Recommended approach

Summary