update-branding

Rebranding Atomic CRM requires updating dual-theme logo assets across five screens and synchronizing the app title in the in-app header, browser tab, and PWA manifest. This skill automates those updates to ensure consistent branding without missing hardcoded values.

Your Atomic CRM title update may not show due to runtime configuration shadowing that prevents code changes from rendering. The app title is hardcoded in three separate locations, requiring synchronized updates to the header, browser tab, and PWA manifest.

Updating light and dark mode logos during CRM rebranding requires handling separate dual-theme logo variants that render correctly across desktop and mobile headers, as well as all authentication pages, to prevent stale branding and unprofessional user experiences.

You can regenerate the full set of 34 favicon and PWA app icons to match new CRM branding. This optional step ensures visual consistency across browser tabs and mobile installations when white-labeling the application for a client.

The best way to white-label Atomic CRM is to replace the default logo with a client wordmark and update the app title to match the client's brand name. This ensures every user touchpoint displays correct branding across themes, headers, and authentication screens.

Common pitfalls when updating CRM branding assets include swapping light and dark logo files, missing hardcoded title values in multiple source files, and encountering runtime configuration shadowing that hides code changes from rendering properly across screens.