Product rename checklist

Name: Product rename checklist
Author: @slashclone

@slashclone/product-rename-checklist

Rename a product across code, copy, CLI, plugins, and docs without breaking anything: one name constant, a careful sweep, and a list of strings that must keep the old name (signing labels, key-derivation labels, OAuth client ids, stored rule ids, migrations). Shows the plan and asks before it edits.

SkillDevOpsv0.1.0 (latest)

Use in Claude Save Like Clone Comment

Activity: New: be the first to try it
Installs: 0 installs
Likes: 0 likes
Clones: 0 clones

One version so far.

This shows up once a second version is shared.

Use in Claude

Claude Code

/kit add @slashclone/product-rename-checklist

CLI

slashclone add @slashclone/product-rename-checklist

Codex

slashclone add @slashclone/product-rename-checklist --agent codex

Not enforced. Codex does not enforce the permissions this kit declares.

Cursor

slashclone add @slashclone/product-rename-checklist --agent cursor

Not enforced. Cursor does not enforce the permissions this kit declares.

claude.ai and the desktop app

Download for Claude

Not enforced. claude.ai and the Claude desktop app do not enforce the permissions this kit declares. How to upload it

As a file

Download .kit

One file with everything in it. slashclone add ./file.kit checks it against this page before installing.

Review before installing

Set up SlashClone in Claude

Health

No keep-alive checks yet

Checks run weekly once someone keeps the kit installed.

Run reports are off

Safety

Scan passed
Not reviewed yet
No tests

This kit reads ** and writes to **. Install it?

Full scan and review

Similar kits

Brand
@brandkit
The /brand command: make whatever you are working on match your brand. It finds your brand guide (or helps you write one), then fixes colors, fonts, logo use, voice, and spacing in a page, CSS, deck outline, email, or social post, and lists every change it made.
Dev prod parity rule
@slashclone
A CLAUDE.md rule that keeps development and production behaving the same: prefer explicit environment flags over NODE_ENV checks, and write down every unavoidable difference in the deploy guide in the same change.
Env secrets check
@shipcheck
Check your repo for leaked secrets before you push or launch: .env files git tracks or will pick up, .env files hiding in git history, server keys behind NEXT_PUBLIC_ or VITE_ prefixes that ship to the browser, provider key shapes (Stripe, AWS, GitHub, OpenAI, Anthropic, Supabase service_role), and passwords hardcoded in code. Reports names and redacted hints, never the values.
On brand check
@brandkit
Review a page, stylesheet, email, deck outline, or post against your brand guide and get a short fix list: off-palette colors (with the nearest brand color), wrong fonts, sizes and spacing off the scale, banned words, logo misuse, and voice. Reports only; changes nothing.

Link

https://slashclone.dev/@slashclone/product-rename-checklist

README badge

[![Install with SlashClone](https://slashclone.dev/badge/slashclone/product-rename-checklist.svg)](https://slashclone.dev/@slashclone/product-rename-checklist)

Embed

<iframe src="https://slashclone.dev/embed/slashclone/product-rename-checklist" width="480" height="200" title="@slashclone/product-rename-checklist" loading="lazy"></iframe>

Share card image