Skip to content
cccskills
FreePublished on GitHub

replica-brand

Develop an app’s own identity through name candidates, a distinct color palette, a logo brief, and writing guidance. Track name screening checks and scan project files for leftover names, domains, and colors from the original app.

OriginalShow the original description

Names and rebrands an app clone so it is the user's own: name candidates with the trademark, domain, store and handle checks to run, a new palette checked for contrast, a logo brief, a voice guide, and a sweep tool that finds anything of the original left in the codebase. Use when the user says "name my app", "rebrand the clone", "make it mine", "pick a name and colours", "logo brief", "brand voice", "check for leftovers", or after /replica-entrepreneur. Always runs before /replica-launch.

See how to install

Good for

  • Shortlist app names and track screening checks
  • Choose a distinct palette with readable contrast
  • Prepare a logo brief and consistent interface wording
  • Find leftover branding in project files

Files included (2)

  • SKILL.md4.2 KB
  • sweep.py7.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

replica-brand

Nothing launches under the original's identity. This skill is the line between "a clone" and "your app".

Tool in this folder:

python3 sweep.py . --avoid "Original Name,Its Company" --domains original.com --colors "#006bff"
python3 sweep.py . --config replica/brand.json        # same, from the brand file

Writes replica/brand.md and replica/brand.json (avoid, domains, colors, used by sweep.py, listing.py and replica-deploy).

Step 1: the name

Read the angle from replica/fixes.md. Generate 20 candidates across styles: descriptive (Booklink), compound (Slotwise), invented (Calvo), metaphor (Harbor), verb (Book). Then cut to 5 with these filters:

  • Not confusingly similar to the original in sound, look or meaning, and not to any other app in the same category. That is the test trademark offices use, so it is the test here. No puns on their name, no "-ly" twin.
  • Short, spellable after hearing it once, no awkward meaning in big languages.
  • Says something about the angle, or at least does not fight it.

Step 2: the checks, run, not assumed

For each of the 5, a row per check. Mark each to run, or the result with the date it was run. Never write "available" for a check nobody ran.

checkwhere
US trademarktmsearch.uspto.gov, the app's class (usually 9 and 42)
EU trademarkeuipo.europa.eu eSearch, or TMview for many offices
Canadaised-isde.canada.ca trademarks database
globalWIPO Global Brand Database
domainwhois name.com, or the registrar's search
App Store and Playsearch the exact name
handlesX, Instagram, TikTok, GitHub
the websearch "name + category"

These are screening checks, not legal clearance. Before spending money on the name, a trademark lawyer should do a proper search.

Step 3: palette

A new palette, written into the same token roles replica-design set up. Pick a primary brand hue from a different family than the original's (if theirs is blue, yours is not a nearby blue). Then:

python3 ../replica-design/contrast.py replica/design/tokens.json

Zero AA failures. Add the original's brand colours to brand.json so the sweep catches any that survive.

Step 4: logo brief

Not a logo, a brief for whoever makes it (the user, a designer, an image model):

  • the idea in one line, tied to the name and angle
  • mark type: wordmark, symbol plus wordmark, or monogram
  • must work at 16px (favicon) and as a 1024px app icon
  • deliverables: SVG, app icon 1024x1024 with no transparency for iOS, favicon set, social image 1200x630
  • must not resemble the original's mark: no shared shape, colour pair or letterform trick. Put the original's logo next to the drafts and check.

Step 5: voice

Three words for how it sounds, with what each does not mean ("direct, not blunt"). Five do and don't pairs. Then rewrite the 10 most-seen strings in the clone (sign up, empty states, the main button, the confirmation, the error) in that voice. All fresh, none echoing the original's phrasing.

Step 6: the sweep

Replace every placeholder name, colour and string. Then:

python3 sweep.py . --config replica/brand.json

It searches file contents and file names for the original's name (also inside identifiers like CalendlyEmbed), domains and colours, skipping node_modules, build output and the replica/ planning folder. Exit 1 means something is left. Fix until it says clean. Also check by eye: the favicon, the page titles, the email templates, the OG image, the app icon.

Output

replica/brand.md (name with checks, palette, logo brief, voice), replica/brand.json, updated tokens, rewritten strings, and a clean sweep. Next: /replica-launch.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Turn research about an existing app into a technical plan for a new implementation. Choose technologies, define database tables and access rules, map API routes, and order development around a small, complete core workflow.

  • Choose technologies for an alternative app
  • Design database tables, indexes, and access rules
  • Map API routes and scheduled background jobs
Jakeschincariol/replica-skill4.8KUpdated Oct 3, 2026

replica-backend

FreeSummary

Build the backend for an app modeled on an existing service, including login, database access rules, Stripe test payments, email, and integrations through official APIs. Track implementation and security checks in a dedicated checklist.

  • Add login and account management
  • Connect screens to a database
  • Implement Stripe payments in test mode
Jakeschincariol/replica-skill4.8KUpdated Oct 3, 2026

replica-build

FreeSummary

Implement an app screen by screen from research and design documents, starting with its core workflow. Write fresh code and interface text, cover loading and error states, and track progress with a feature matrix and screenshots.

  • Build app screens from research and design documents
  • Implement the core workflow from start to finish
  • Cover empty, loading, error, and mobile states
Jakeschincariol/replica-skill4.8KUpdated Oct 3, 2026

replica-deploy

FreeSummary

Prepare and publish an app built from an existing reference, covering release checks, production services, domain and email records, payments, sign-in, monitoring, and mobile distribution. It records results and requires user approval before going live.

  • Checking whether an app is ready for release
  • Connecting a custom domain and email settings
  • Preparing production payments and sign-in
Jakeschincariol/replica-skill4.8KUpdated Oct 3, 2026

replica-design

FreeSummary

Rebuild an app’s visual system as reusable design values and component specifications. It covers typography, spacing, component states, implementation, and contrast checks while replacing the original app’s branded assets with independent alternatives.

  • Reconstructing design rules from app screenshots
  • Defining shared tokens and component states
  • Checking text and background contrast
Jakeschincariol/replica-skill4.8KUpdated Oct 3, 2026

replica-diff

FreeSummary

Compare a recreated app with its reference using weighted feature coverage, screenshot layout differences that ignore color, and workflow reviews. Generate a report showing missing functionality, release readiness, and the next five implementation priorities.

  • Measuring how much reference functionality is implemented
  • Comparing screen layouts after changing brand colors
  • Reviewing workflow and error-handling differences
Jakeschincariol/replica-skill4.8KUpdated Oct 3, 2026

See all skills by Jakeschincariol

Report a problem with this skill