replica-brand
Skill1 starsChanged 18 days agoMITView on GitHub
Name and rebrand an app clone so it is the user's own: name candidates with trademark checks to run (Rospatent/FIPS, USPTO, EUIPO, WIPO), domains, store and handle checks, a new palette checked for contrast, a logo brief, a voice, and a sweep tool that finds anything of the original left in the code, including Russian transliterations. Use for 'name my app', 'rebrand', 'make it mine', 'logo brief', 'check for leftovers'; RU: название для приложения, ребрендинг, сделать своим, проверка товарного знака.
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- realtahailyas/reverse-engineer-app-skillsedited, first seen Oct 25, 2026
- Jakeschincariol/replica-skilledited, first seen Oct 3, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- Jakeschincariol/replica-skill★ 39920% same
- realtahailyas/reverse-engineer-app-skills★ 320% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- replica-architectSkill
- replica-backendSkill
- replica-buildSkill
- replica-deploySkill
- replica-designSkill
- replica-diffSkill
- replica-launchSkill
- replica-reconSkill
- replica-testSkill
- replica-usersSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Read replica/region.txt (written by /replica-recon): ru, global or both.
- Distinctive: line 35
Never write "available" for a check nobody ran.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
replica-brand
Nothing launches under the original's identity. This is the line between a clone and your app.
python3 sweep.py . --config replica/brand.jsonWrites replica/brand.md and replica/brand.json (avoid, domains, colors), used by
sweep.py, listing.py and /replica-deploy.
Region
Read replica/region.txt (written by /replica-recon): ru, global or both. It decides the
stack, the stores, the laws and the trademark checks. python3 ../replica-architect/stack.py
--region <region> prints them. No file yet: ask where the app will be sold and write it.
Step 1: the name
From the angle in replica/fixes.md, twenty candidates across styles (descriptive, compound,
invented, metaphor, verb), cut to five: not confusingly similar to the original in sound, look or
meaning (the test trademark offices use: no puns on their name, no one-letter twin); short and
spellable after hearing it once; no awkward meaning in Russian or English; supports the angle.
For ru and both: it reads well in Cyrillic and in Latin, and the Latin spelling is the one
for the domain.
Step 2: checks, run and dated, never assumed
Per candidate, one row per check, marked to run or with the result and the date it was run. Never write "available" for a check nobody ran.
| check | where |
| Russia trademark | FIPS open registers (fips.ru), classes 9 and 42 |
| US trademark | tmsearch.uspto.gov |
| EU trademark | EUIPO eSearch or TMview |
| worldwide | WIPO Global Brand Database |
| domain | the registrar's search (.ru, .рф, .com, .app) |
| stores | the exact name in RuStore, App Store, Google Play |
| handles | Telegram, VK, X, Instagram, TikTok, GitHub |
| the web | "name + category", in both languages |
These are screening checks, not clearance. Before money goes into the name, a trademark lawyer runs a proper search.
Step 3: palette
A primary hue from a different family than the original's, written into the same token roles,
then ../replica-design/contrast.py: zero AA failures. The original's colours go into
brand.json so the sweep catches survivors.
Step 4: logo brief
The idea in a line, the mark type, works at 16px and as a 1024px app icon, deliverables (SVG, iOS icon 1024x1024 with no transparency, Android adaptive icon, favicon set, 1200x630 share image), and it must not resemble the original's mark: put both side by side and check.
Step 5: voice
Three words with what each does not mean ("direct, not blunt"), five do and don't pairs, then the ten most-seen strings rewritten in that voice, in every language the app ships.
Step 6: the sweep
Replace every placeholder, then sweep.py. It searches contents and file names for the original's
names (also inside identifiers and in Cyrillic transliteration), domains and colours, skipping
node_modules, build output and replica/. Exit 1 means something is left. Then by eye: favicon,
titles, email templates, share image, app icon.
Next: /replica-launch.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.