How do I install the Slim Rebranding skill?

Run npx skillmds@latest add majiayu000/slim-rebranding-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Slim Rebranding safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Slim Rebranding?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Slim Rebranding free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Slim Rebranding?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Slim Rebranding by majiayu000 — Agent Skill

Name: Slim Rebranding
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

Slim Rebranding

Comprehensive autonomous rebranding skill for projects. Handles all aspects of rebranding including text/naming, documentation, visual assets, colors/theming, and configuration files. Works with any codebase (Node, Python, Java, C++, Rust, Go, etc.). Auto-integrates free Phosphor icons. Presents detailed plan for approval before executing changes. Creates git branch and commits with clear messages. Validates changes with linters and build systems. Use when rebranding a project, changing project name, updating visual identity, or modernizing brand assets.

majiayu000 Updated Sep 22, 2026 567 repo stars

File contents

SLIM Website Rebranding

Workflow

Step 1: Input Collection

Collect project name, tagline, logo, organization details
Ask about external registry imports and local marketplace handling

Step 2: Git Branch

Create branch: rebrand/website-{old-slug}-to-{new-slug}

Step 3: Update Configuration

Update docusaurus.config.js fields: title, tagline, url, baseUrl, organizationName, projectName
Update brandingConfig: logoPath, hero settings, marketplace settings
Update slimConfig.registries if external imports requested
Place logo file if provided

Step 4: Registry Processing

Fetch external registry URLs if requested
Insert external registry entries with external_only: true and repository.url into docusaurus.config.js section for slimConfig
Clear local marketplace .claude-plugin/marketplace.json and static/data/registry.json based on user choice

Step 5: Documentation Generation

Generate docs/contribute/submit-best-practice.md
Generate docs/faq/README.md
Generate docs/about/README.md

Step 6: Final Updates

Update README.md references
Update package.json if needed
Run npm install; npm run build
Commit changes

Dependencies

src/utils/brandingUtils.js
src/hooks/useBrandingConfig.js

Prerequisites

SLIM-based Docusaurus website
Git repository initialized
Node.js and npm installed

---name: slim-rebranding-3description: Comprehensive autonomous rebranding skill for projects. Handles all aspects of rebranding including text/naming, documentation, visual assets, colors/theming, and configuration files. Works with any codebase (Node, Python, Java, C++, Rust, Go, etc.). Auto-integrates free Phosphor icons. Presents detailed plan for approval before executing changes. Creates git branch and commits with clear messages. Validates changes with linters and build systems. Use when rebranding a project, changing project name, updating visual identity, or modernizing brand assets.---# SLIM Website Rebranding## Workflow### Step 1: Input Collection- Collect project name, tagline, logo, organization details- Ask about external registry imports and local marketplace handling### Step 2: Git Branch- Create branch: `rebrand/website-{old-slug}-to-{new-slug}`### Step 3: Update Configuration- Update `docusaurus.config.js` fields: title, tagline, url, baseUrl, organizationName, projectName- Update `brandingConfig`: logoPath, hero settings, marketplace settings- Update `slimConfig.registries` if external imports requested- Place logo file if provided### Step 4: Registry Processing- Fetch external registry URLs if requested- Insert external registry entries with `external_only: true` and `repository.url` into `docusaurus.config.js` section for `slimConfig`- Clear local marketplace `.claude-plugin/marketplace.json` and `static/data/registry.json` based on user choice### Step 5: Documentation Generation- Generate `docs/contribute/submit-best-practice.md`- Generate `docs/faq/README.md`- Generate `docs/about/README.md`### Step 6: Final Updates- Update `README.md` references- Update `package.json` if needed- Run `npm install; npm run build`- Commit changes## Dependencies- `src/utils/brandingUtils.js`- `src/hooks/useBrandingConfig.js`## Prerequisites- SLIM-based Docusaurus website- Git repository initialized- Node.js and npm installed

Frequently asked questions