Przejdź do treści
Biblioteka skilli
Marketing i treści · Analiza

mint

/mint

Diagnozuje, dlaczego nazwa marki, produktu, skilla lub postaci nie działa, i prowadzi przez tworzenie nazw, które działają.

Repozytorium
empire ↗
Licencja
MIT
Ostatnia zmiana repozytorium
07.10.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 07.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Diagnozuje, dlaczego nazwa marki, produktu, skilla lub postaci nie działa, i prowadzi przez tworzenie nazw, które działają.

Wyzwalacze z opisu

name thisthis name doesnbrand namingproduct namingnames donforgettable namewrong associationsmint a name
Oryginalny opis (EN)

Diagnose why names don't work and guide creation of names that do — brand, product, skill, character, place names, and titles. Use when a name feels wrong but no one can say why, a name family feels disjointed, a name is forgettable, or systematic naming is needed. Trigger phrases: "name this", "this name doesn't feel right", "brand naming", "product naming", "names don't match", "forgettable name", "wrong associations", "mint a name", "/empire-product:mint". Findings stay local — never post to GitHub.

Jak działa

SKILL.md bez nagłówków drugiego poziomu · 116 linii, 711 słów

Podgląd SKILL.md
---
name: mint
description: >
  Diagnose why names don't work and guide creation of names that do — brand, product,
  skill, character, place names, and titles. Use when a name feels wrong but no one can
  say why, a name family feels disjointed, a name is forgettable, or systematic naming
  is needed.
  Trigger phrases: "name this", "this name doesn't feel right", "brand naming",
  "product naming", "names don't match", "forgettable name", "wrong associations",
  "mint a name", "/empire-product:mint".
  Findings stay local — never post to GitHub.
compatibility: Designed for Claude Code (or similar agents).
---

<section id="core">

**Names operate on multiple layers that must align.** When layers align, names feel inevitable. When they conflict, names feel wrong even if no one can articulate why.

Four layers: sound, meaning, cultural, functional. Problems arise from layer conflicts — sound says "playful" but meaning says "serious"; cultural layer says "luxury" but the name is a typo trap.

</section>

<section id="states">

### N1: Doesn't "Feel Right"

**Symptoms:** Stakeholders reject names but can't say why. Gut reactions are negative despite meeting requirements. Something's "off."

**Key questions:** Do sounds match intended emotional tone? Is there a meaning conflict between layers? Does it violate category expectations?

**Checklist:** sound pattern matches desired attributes; no unintended negative associations; pronunciation is intuitive; fits cultural context.

**Interventions:** analyze sound layer independently; check for hidden meaning conflicts; test with naive audience for associations.

---

### N2: Names Don't Belong Together

**Symptoms:** Product family feels disjointed. Names seem from different worlds. No cultural coherence.

**Key questions:** Is there a consistent sound palette? Do syllable structures match? Is there a unifying pattern?

**Checklist:** phoneme inventory defined; syllable templates consistent; naming conventions documented; outliers identified.

**Interventions:** define phoneme inventory; establish syllable templates (CV, CVC, CVCV, etc.); create naming conventions; regenerate outliers.

---

### N3: Forgettable

**Symptoms:** People can't recall the name. It blends into category. No distinctive hook.

**Key questions:** Is there a memorable sound pattern? Does it have a meaning anchor? Is it too similar to alternatives?

**Checklist:** distinctive sound feature; meaning hook exists (metaphor, unexpected reference); differentiated from competitors; passes "phone test" (easy to convey verbally).

**Interventions:** add sound distinctiveness (unusual but pronounceable); create meaning hook; test against alternatives for differentiation.

---

### N4: Sends Wrong Signals

**Symptoms:** Audience interprets name differently than intended. Wrong category assumptions. Unintended associations.

**Key questions:** What does this name sound like it should be? What category conventions is it following/breaking? Are there unfortunate associations?

**Checklist:** sound patterns match intended category; cultural references understood by audience; no negative meanings in target markets; international check done (if relevant).

**Interventions:** audit category sound conventions; test with target audience; check cross-cultural meanings.

---

### N5: Doesn't Work Practically

**Symptoms:** People misspell it. They mispronounce it. Domain unavailable. Hard to type.

**Key questions:** Is spelling intuitive from pronunciation? Are there common mistypings? Does it work in all required contexts?

**Checklist:** spelling matches pronunciation; no typo-prone letter combinations; domain/handles available (if needed); voice search recognizes it (if relevant).

**Interventions:** test spelling from dictation; check typo patterns; verify availability; test voice recognition.

</section>

<section id="layers">

Four layers to check for alignment: sound, meaning, cultural, functional. Misalignment is what makes a name "feel wrong."

Full lookup catalog — sound patterns, syllable templates, meaning types, cultural conventions, functional tests — in `references/layers.md`. Read it for brand/product naming or any deep layer analysis; quick naming can work from the states alone.

</section>

<section id="diagnostic-process">

1. **Identify the problem state** — N1 (feels wrong), N2 (disjointed family), N3 (forgettable), N4 (wrong signals), N5 (practical issues)
2. **Analyze by layer** — sound, meaning, cultural, functional. Check alignment (catalog in `references/layers.md`).
3. **Identify conflicts** — where do layers contradict?
4. **Recommend interventions** — based on identified state and conflicts

For brand/product names: SHOULD run phases sequentially (Discovery → Synthesis → Evaluation → Validation) rather than generating and evaluating in the same pass. Discovery constrained by premature evaluation produces mediocre patterns.

For quick naming (character names, places, skill names): use diagnostic states directly.

</section>

<section id="quick-fixes">

- Name feels harsh → add flow sounds (l, r, vowels) or soften consonants
- Name feels weak → add power sounds (k, t, p) or shorten syllables
- Name feels generic → add distinctive phoneme or unusual combination
- Name feels foreign → shift toward high-frequency English phonemes
- Name feels dated → check category conventions; update to current patterns

</section>

<section id="anti-patterns">

**The Kitchen Sink** — trying to communicate everything in one name. Fix: pick one primary message.

**The Inside Joke** — meaning only creators understand. Fix: test with naive users.

**The Sound-Alike** — too similar to existing names. Fix: check competitors; verify distinctiveness.

**The Unpronounceable** — looks interesting but no one can say it. Fix: test pronunciation; simplify clusters.

**The Apostrophe Catastrophe** — random apostrophes for "exotic" feel. Fix: if using, define what they mean; use sparingly.

</section>
Pliki w paczce (2)
  • SKILL.md 6 KB
  • references/layers.md 3 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · marcoskichel/empire90MIT
AdinathChaudhari/website-mcp100MIT

Migawka bazy z 13.11.2026 · wersja paczki 398ec10959ce (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100naming-6-gates
    Wymyśla nazwy marek, produktów i firm, które działają w różnych językach, na asystentach głosowych i w rekomendacjach AI.
  • 100arn-spark-naming
    Prowadzi przez wymyślanie nazwy marki produktu: analiza strategiczna, generowanie pomysłów, ocena jakościowa i sprawdzenie dostępności.
  • 85product-name
    Proponuje pięć oryginalnych nazw produktu z uzasadnieniem, zgodnych z wartościami marki i grupą docelową.
  • 100brand-naming
    Prowadzi pełny proces nazywania marki dla założycieli, agencji i firm: pomysły na nazwy, ocena i ranking istniejących opcji na podstawie briefu marki.
  • 100brand-naming-method
    Generuje propozycje nazw marki, odsiewa je archetypami i regułami fonotaktycznymi, a pozostałe punktuje według dostępności domeny, nasycenia rynku i ryzyka znaku towarowego.
  • 100brand-naming-method
    Układa listę nazw marki, odfiltrowuje ją archetypami i regułami fonotaktycznymi i ocenia ocalałe nazwy: dostępność domeny, nasycenie rynku i ryzyko znaku towarowego.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.