naming-brands-and-products
Skill1 starsChanged 3 months agoMITView on GitHub
Use when a brand, product, service, feature, or program needs a name that must fit strategic positioning, language constraints, category context, and preliminary availability checks.
In this repository65 other files it gives its agents.
- analyzing-change-blast-radiusSkill
- analyzing-developer-career-opportunitiesSkill
- art-directing-web-interfacesSkill
- assessing-developer-proficiencySkill
- auditing-dependency-riskSkill
- auditing-pixel-perfect-frontendSkill
- bootstrapping-modern-web-appsSkill
- brag-slimSkill
- building-brand-guidelinesSkill
- building-conversion-product-pagesSkill
- building-developer-career-roadmapsSkill
- building-hybrid-game-assetsSkill
- building-premium-nextjs-interfacesSkill
- building-project-showcasesSkill
- building-regression-testsSkill
- building-reliable-node-api-boundariesSkill
- choosing-application-architectureSkill
- craft-premium-motionSkill
- creating-character-sprite-pipelinesSkill
- defining-brand-strategySkill
- designing-action-combatSkill
- designing-developer-portfolio-evidenceSkill
- designing-relational-data-modelsSkill
- designing-software-boundariesSkill
- designing-test-strategiesSkill
- designing-ui-systemsSkill
- designing-visual-identitiesSkill
- documenting-architecture-decisionsSkill
- editing-for-clarity-and-toneSkill
- engineering-gsap-animationsSkill
- evaluating-developer-proficiencySkill
- evolving-postgres-schemas-safelySkill
- humanizing-generated-proseSkill
- implementing-reference-faithful-uiSkill
- investigating-codebase-semanticallySkill
- managing-implementation-slicesSkill
- mapping-existing-codebase-structureSkill
- optimizing-frontend-motion-performanceSkill
- orchestrating-cinematic-web-motionSkill
- planning-codebase-changes-with-evidenceSkill
- planning-engineering-workSkill
- planning-launch-distributionSkill
- planning-safe-refactorsSkill
- planning-written-communicationSkill
- preparing-project-launchSkill
- profiling-postgres-query-performanceSkill
- reconstructing-images-as-threejsSkill
- reviewing-api-securitySkill
- reviewing-apple-platform-interfacesSkill
- reviewing-pull-requestsSkill
- reviewing-web-securitySkill
- selecting-working-methodsSkill
- shipping-github-vercel-changesSkill
- teaching-developer-conceptsSkill
- testing-integration-boundariesSkill
- testing-playable-gamesSkill
- testing-web-applications-end-to-endSkill
- threat-modeling-applicationsSkill
- tracing-code-execution-pathsSkill
- translating-figma-to-nextjsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Write a naming brief from the brand strategy: audience, offer, desired associations, personality, category frame, languages/markets, naming …
- Distinctive: line 16
Run a linguistic screen. Read candidates aloud, test likely pronunciations and misspellings, inspect meanings and unintended associations …
- Distinctive: line 17
Test names in realistic context: spoken introduction, URL/search result, product UI, endorsement line, sub-brand extension, and support …
- Distinctive: line 18
Run preliminary availability checks for obvious conflicts.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Naming Brands and Products
Core principle
Naming is strategic selection under constraints, not a contest for the cleverest word. Generate broadly, evaluate consistently, and separate creative preference from linguistic, operational, and legal risk.
Naming workflow
- Write a naming brief from the brand strategy: audience, offer, desired associations, personality, category frame, languages/markets, naming architecture, and hard constraints.
- Define evaluation criteria before generating candidates. Typical criteria include strategic fit, distinctiveness, memorability, pronunciation, spelling, extension potential, and avoidable negative associations.
- Build several naming territories instead of one word list. Territories may use descriptive, suggestive, metaphorical, invented, founder/place, compound, or other structures when they fit the brief.
- Generate breadth inside each territory. Do not evaluate every idea while generating; premature filtering collapses diversity.
- Run a linguistic screen. Read candidates aloud, test likely pronunciations and misspellings, inspect meanings and unintended associations in relevant languages, and flag confusing similarity to category terms or competitors.
- Test names in realistic context: spoken introduction, URL/search result, product UI, endorsement line, sub-brand extension, and support conversation.
- Run preliminary availability checks for obvious conflicts. Search target markets and relevant goods/services using authoritative trademark databases where available. Treat domains and social handles as operational signals, not proof of trademark availability.
- Score the shortlist against the criteria and document trade-offs. Prefer a small set of candidates with clear rationale over dozens of unranked options.
- Escalate legal clearance when the name will carry material commercial value. A naming exercise or database search is not legal advice and cannot guarantee registrability or freedom to use.
Red flags
Reject or downgrade a candidate when it:
- needs a long explanation before it makes sense;
- is only distinctive through unusual spelling that harms recall or pronunciation;
- creates a misleading category or product promise;
- has obvious conflicts in a target market;
- works only in a design mockup but fails when spoken or typed;
- blocks likely future extensions without a strategic reason.
Verification
For each finalist, record the territory, strategic rationale, pronunciation, likely spelling errors, linguistic concerns, preliminary trademark-search notes, digital-operational notes, and unresolved risks. The shortlist should make the remaining decision explicit rather than hide uncertainty.
References
- WIPO Global Brand Database: https://www.wipo.int/en/web/global-brand-database
- WIPO, checking trademark availability before filing: https://www.wipo.int/en/web/madrid-system/check-availability
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.

