update-branding

Update Atomic CRM logos and titles across themes, screens, and PWA files.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/yaresimeonthomas/-kate-crm --skill update-branding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-branding
Source: https://github.com/yaresimeonthomas/-kate-crm/tree/main/.claude/skills/update-branding
Command: npx skills add https://github.com/yaresimeonthomas/-kate-crm --skill update-branding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually updating the Atomic CRM logo and title across multiple hardcoded locations and light/dark theme variants leads to inconsistent branding, with stale assets or text left behind in hard-to-find files.

Core Features & Use Cases

  • Cross-theme logo management: Handles both light and dark mode logo variants across all 5 screens (desktop header, mobile header, login, signup, confirmation pages).
  • Full title consistency: Updates the app title in all 3 hardcoded locations (header, browser tab, PWA manifest) to avoid mismatched branding.
  • Optional favicon/PWA support: Can regenerate the full set of 34 favicon and PWA app icons if requested, instead of requiring manual edits to individual files.
  • Use Case: A company that has customized Atomic CRM for their internal sales team can use this skill to quickly replace the default Atomic CRM wordmark with their own company logo and update the app name to match their internal product naming, with no leftover stale branding.

Quick Start

Use the update-branding skill to replace the default Atomic CRM logo with your custom wordmark and update the app title to your product name.

Frequently Asked Questions about update-branding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rebrand the logo and app title in Atomic CRM without missing hardcoded locations?

To rebrand Atomic CRM, update the logo across light and dark theme variants on all 5 screens, and change the title in the header, browser tab, and PWA manifest to ensure full branding consistency and eliminate stale assets.

Why does my CRM logo look wrong in dark mode after a manual rebrand?

Manual CRM logo updates often miss dark mode variants, causing rendering issues. Consistent branding requires replacing both light and dark mode logo assets across all screens, including desktop, mobile, login, signup, and confirmation pages.

How do I update the PWA manifest and browser tab title for a customized CRM?

Updating the PWA manifest and browser tab title requires modifying the app title in all 3 hardcoded locations within the CRM. This ensures the browser tab, PWA installation, and header text match your customized product name.

Can I regenerate the full favicon and PWA icon set during a CRM rebrand?

Yes, you can regenerate the full set of 34 favicon and PWA app icons during a CRM rebrand. This optional step automates icon creation instead of requiring manual edits to individual image files.

Does localStorage affect CRM branding overrides after a rebrand?

Yes, localStorage-stored branding overrides can shadow default CRM configuration. Proper handling ensures new logo and title updates display correctly by clearing or managing stale locally stored branding data.