rebranding-strategy▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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)
| Phase | Duration | Focus |
|---|---|---|
| Audit & plan | Weeks 1–2 | Brand audit; inventory touchpoints; migration plan |
| Prepare | Weeks 2–6 | New assets; redirect mapping; staging; backup |
| Pre-launch | Week 6–8 | Internal announcement; social handle check; teasers |
| Launch | Week 8+ | Go live; 301 redirects; multi-channel announcement |
| Post-launch | 2–4 weeks | Monitor search, traffic; fix 404s; iterate |
Principle: Plan for months. Avoid changing domain and major structure in one migration—split into smaller migrations when possible.
301 Redirect Best Practices
| Practice | Purpose |
|---|---|
| 1:1 mapping | Each old URL → most relevant new URL; never redirect all to homepage |
| 301 (permanent) | Use 301, not 302; 302 does not fully transfer SEO equity |
| No chains/loops | Old URL → final destination directly; avoid A→B→C |
| Redirect mapping sheet | Document every old→new mapping; prevents ~80% of migration failures |
| Don't block in robots.txt | Redirected URLs should not be disallowed |
Common Mistakes
- Redirect chains (multiple hops)
- Redirect loops
- Redirecting everything to homepage
- Using 302 for permanent moves
- Blocking redirected URLs in robots.txt
Domain Migration Checklist
Pre-Migration
- Create SEO migration plan
- Collect benchmarks (GA4, GSC, rankings)
- Run site crawler; inventory all pages
- Create redirect mapping sheet (old URL → new URL)
- Purchase new domain; configure DNS
- Technical SEO audit
- Staging environment; backup
- Check for manual penalties on both domains
Launch
- Implement 301 redirects
- Update Google Search Console (change of address)
- Update sitemaps, robots.txt
- Verify new site works; test redirects (curl, Screaming Frog)
- Add GA4 annotation for migration date
Post-Migration
- Monitor GSC coverage; fix "Page with Redirect" issues
- Fix 404s immediately
- Expect temporary ranking fluctuation (2–4 weeks)
- Do not delete old site as fallback
Social Media Announcement
Three Phases
| Phase | Actions |
|---|---|
| Pre-Launch | Finalize new identity; audit social presence; secure handles across platforms; internal alignment |
| Build Anticipation | Tease with sneak peeks; cryptic visuals; influencer/ambassador previews; avoid announcing too soon |
| Execute | All platforms updated together; new bios, handles, visuals; compelling rebrand story (why, not what) |
What to Avoid
- Don't list steps or technical details—focus on story and benefit
- Don't announce before all pieces are in place (mixed messaging)
- Don't rely on one channel—multi-channel rollout
- Don't bombard with "why we rebranded" unless it resonates
Rebrand Story
- Anchor: Emotionally resonating narrative; why now; how it benefits customers
- Avoid: "We changed our logo" / "We updated our website" without context
Internal Communication
- Brief all employees before public launch
- Explain strategic reasons; equip them to answer customer questions
- Update email signatures, Slack, internal docs
- Internal FAQ for common rebrand questions
Output Format
- Timeline (phases, milestones)
- Redirect mapping approach (template, tools)
- Migration checklist (customized)
- Social announcement plan (phases, channels, content angles)
- Internal communication (briefing, FAQ)
Related Skills
- domain-selection: Domain choice (Brand/PMD/EMD, TLD); informs new domain choice when rebranding
- domain-architecture: Domain structure before/after rebrand
- website-structure: New site structure after migration
- schema-markup: Update Organization schema on new domain
- multi-domain-brand-seo: When old and new domains coexist during transition
- branding: Brand strategy, identity; rebranding implements the change
- brand-protection: Sync impersonation checks when rebranding; update official domain declaration
- gtm-strategy: Repositioning GTM; when repositioning includes rebrand
How to use rebranding-strategy on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add rebranding-strategy
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches rebranding-strategy from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate rebranding-strategy. Access the skill through slash commands (e.g., /rebranding-strategy) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★62 reviews- ★★★★★Pratham Ware· Dec 28, 2024
rebranding-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Mateo Harris· Dec 12, 2024
rebranding-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Alexander Shah· Dec 8, 2024
rebranding-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Harper Malhotra· Dec 4, 2024
rebranding-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Sofia Huang· Nov 27, 2024
We added rebranding-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ishan Lopez· Nov 23, 2024
We added rebranding-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Alexander Li· Nov 3, 2024
Solid pick for teams standardizing on skills: rebranding-strategy is focused, and the summary matches what you get after install.
- ★★★★★Alexander Thomas· Oct 22, 2024
We added rebranding-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Alexander Wang· Oct 18, 2024
Solid pick for teams standardizing on skills: rebranding-strategy is focused, and the summary matches what you get after install.
- ★★★★★Liam Johnson· Oct 14, 2024
Solid pick for teams standardizing on skills: rebranding-strategy is focused, and the summary matches what you get after install.
showing 1-10 of 62