| name | rebranding-strategy |
| description | When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection. |
| metadata | {"version":"1.0.1"} |
Strategy: Rebranding
Guides rebranding execution: domain change, 301 redirects, migration checklist, and communication (social media, internal). Plan for months, not days or weeks. See domain-selection for initial domain choice; domain-architecture for domain structure decisions; multi-domain-brand-seo when multiple domains coexist.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand and product info.
Identify:
- Scope: Full rebrand (name, domain, identity) vs partial (logo, messaging only)
- Domain change: Yes or no; old → new mapping
- Timeline: Target launch date; typical 4–12 weeks
- Channels: Website, social, product UI, directories, email
Rebranding Timeline (Typical)
