Replace the product name, logo, and brand colors

OUTCOMES

What this Prompt helps you deliver

Every major client presents one coherent brand
You retain an auditable inventory of brand assets

BEFORE YOU START

Before you start

The new product name, logo, and brand colors are decided
The local TabTin environment runs successfully

What AI should inspect first

apps/tabtin-electronapps/tabtin-www-nextapps/tabtin-iosapps/tabtin-androidpackages

READY TO RUN

Complete Prompt

Copy the complete Prompt with its execution and acceptance boundaries.

You are turning TabTin into my own product brand. I will provide the new name, short name, logo, icons, brand colors, company details, and domain. Begin with an inventory of every brand touchpoint; a repository-wide string replacement is not an acceptable approach.

Before you begin

Read AGENTS.md and inspect apps/tabtin-electron, apps/tabtin-www-next, apps/tabtin-ios, apps/tabtin-android, and packages. Search for current names, icons, bundle identifiers, package names, window titles, installer metadata, website metadata, and mobile assets. Separate visible branding from package identifiers, protocols, and compatibility identifiers. Explain the migration risk before changing anything that can affect upgrades, sign-in, signatures, or data paths.

Work to complete

Build a brand-asset matrix for Web, Electron, Windows/macOS installers, iOS, Android, email, and public sharing pages.
Produce safe sizes and formats from my source logo while preserving whitespace, transparency, and sharpness.
Apply the primary and supporting colors through existing design tokens, preserving contrast and TabTin’s flat, breathable visual language.
Update visible names, company details, titles, descriptions, app display names, and package metadata.
Keep compatibility layers for protocols, data directories, and signatures. When a change is necessary, provide a migration path.

Verification

Run the relevant Web and client type checks, builds, or platform compilers. Search for the old brand and classify legitimate technical references instead of blindly removing them. Inspect at least the homepage hero, sign-in, main window, About page, installer name, and mobile launch assets. Reject stretched icons, weak contrast, or mixed branding.

Final report

List changes by client, internal identifiers intentionally retained, build results, and signing or store materials still needed. Include a reusable brand-asset inventory for future upgrades. Do not commit or push unless I explicitly ask.