replica-brand
Skill399 starsChanged 40 days agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- realtahailyas/reverse-engineer-app-skillsword for word, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 1
- realtahailyas/reverse-engineer-app-skills★ 3100% same
Edited · 0
None found.
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-entrepreneurSkill
- replica-launchSkill
- replica-reconSkill
- replica-testSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 30
Read the angle from replica/fixes.md.
- Distinctive: line 74
Not a logo, a brief for whoever makes it (the user, a designer, an image model):
- Distinctive: line 79
must work at 16px (favicon) and as a 1024px app icon
- Distinctive: line 82
must not resemble the original's mark: no shared shape, colour pair or letterform trick.
≈ “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 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 fileWrites 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.
| check | where |
| US trademark | tmsearch.uspto.gov, the app's class (usually 9 and 42) |
| EU trademark | euipo.europa.eu eSearch, or TMview for many offices |
| Canada | ised-isde.canada.ca trademarks database |
| global | WIPO Global Brand Database |
| domain | whois name.com, or the registrar's search |
| App Store and Play | search the exact name |
| handles | X, Instagram, TikTok, GitHub |
| the web | search "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.jsonZero 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.jsonIt 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.
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.