Idea Refinement
addyosmani/agent-skills
Guides a conversation that takes a vague idea through divergent and convergent thinking and ends in a markdown one-pager covering scope and assumptions.
Diagnose why names don't work and guide creation of names that do.
$ npx skills add jwynia/agent-skills --skill naming -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jwynia/agent-skills naming --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/general/ideation/naming .claude/skills/naming && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "naming" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/ideation/naming into .claude/skills/naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jwynia/agent-skills/tree/main/skills/general/ideation/namingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jwynia/agent-skills --skill naming -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jwynia/agent-skills naming --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/general/ideation/naming .agents/skills/naming && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "naming" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/ideation/naming into .agents/skills/naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill naming -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jwynia/agent-skills naming --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/general/ideation/naming .cursor/skills/naming && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "naming" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/ideation/naming into .cursor/skills/naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jwynia/agent-skills.git --path skills/general/ideation/naming--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jwynia/agent-skills --skill naming -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jwynia/agent-skills naming --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/general/ideation/naming .gemini/skills/naming && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "naming" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/ideation/naming into .gemini/skills/naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jwynia/agent-skills namingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jwynia/agent-skills --skill naming -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/general/ideation/naming .github/skills/naming && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "naming" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/ideation/naming into .github/skills/naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill naming -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jwynia/agent-skills naming --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/general/ideation/naming .opencode/skills/naming && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "naming" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/general/ideation/naming into .opencode/skills/naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "naming", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
namingDiagnose why names don't work and guide creation of names that do.
Naming is an agent skill from jwynia/agent-skills. Diagnose why names don't work and guide creation of names that do. Use for brand names, product names, character names, place names, and titles when something feels off or when systematic naming is needed.
Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Naming loads about 3.6k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 1,710 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 1,710 words, ~3,641 tokens.
.claude/skills/naming/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.You diagnose naming problems and guide the creation of names that work. Your role is to identify why names fail and what makes names succeed across brands, products, characters, places, and titles.
Names operate on multiple layers that must align.
Every name communicates through sound, meaning, cultural resonance, and functional fit. When layers align, names feel inevitable. When they conflict, names feel wrong even if no one can articulate why.
Symptoms: Stakeholders reject names but can't say why. Gut reactions are negative despite meeting requirements. Something's "off."
Key Questions:
Diagnostic Checklist:
Interventions:
Symptoms: Product family feels disjointed. Character names seem from different worlds. Place names lack cultural coherence.
Key Questions:
Diagnostic Checklist:
Interventions:
Integration: For character/place naming in fiction, use the conlang skill to generate consistent phonological systems.
Symptoms: People can't recall the name. It blends into category. No distinctive hook.
Key Questions:
Diagnostic Checklist:
Interventions:
Symptoms: Audience interprets name differently than intended. Wrong category assumptions. Unintended associations.
Key Questions:
Diagnostic Checklist:
Interventions:
Symptoms: People misspell it. They mispronounce it. Domain unavailable. Hard to type.
Key Questions:
Diagnostic Checklist:
Interventions:
How it sounds and what sounds communicate.
| Sound Pattern | Association | Use For |
|---|---|---|
| Depth sounds (ɑ, o, u, m, n) | Weight, seriousness, gravitas | Authority brands, serious characters |
| Light sounds (i, e, l, s) | Speed, precision, elegance | Tech, luxury, agile brands |
| Power sounds (k, t, p, x) | Strength, impact, decisiveness | Performance, action brands |
| Flow sounds (l, r, w) | Movement, continuity, grace | Movement, music, flow states |
| Tech sounds (x, z, -ix, -ex) | Modern, digital, technical | Tech products, futuristic contexts |
High-frequency sounds (feel natural, trustworthy):
Low-frequency sounds (feel distinctive, exotic):
Principle: Common sounds for accessibility; rare sounds for distinctiveness. Too many rare sounds = unpronounceable.
| Pattern | Feel | Example |
|---|---|---|
| CV | Open, flowing | "Sora", "Kano" |
| CVC | Solid, complete | "Mark", "Bond" |
| CVCV | Balanced, memorable | "Toyota", "Roku" |
| CCV | Dynamic, energetic | "Slack", "Stripe" |
| Type | Description | Example |
|---|---|---|
| Descriptive | Says what it is | "General Motors" |
| Metaphorical | Implies qualities | "Amazon", "Apple" |
| Abstract | Coined, meaning assigned | "Kodak", "Xerox" |
| Portmanteau | Blended words | "Pinterest" |
Best names work on multiple levels—literal, metaphorical, and cultural.
| Category | Convention |
|---|---|
| Luxury fashion | French/Italian sounds |
| Tech startups | Dropped vowels, -ly, -ify |
| Law firms | Partner surnames |
| Pharmaceuticals | X, Z, scientific suffixes |
| Fantasy | Apostrophes, unusual clusters |
Strategic choice: Follow conventions to signal belonging; break them to differentiate.
| Test | Pass Criterion |
|---|---|
| Spelling | Intuitive from pronunciation |
| Pronunciation | Intuitive from spelling |
| Typing | No awkward key combinations |
| Search | Returns relevant results |
| Domain | Available or acceptable variant |
| Voice | Voice search recognizes it |
When someone brings a naming problem:
For each layer, check alignment:
| Layer | Question |
|---|---|
| Sound | Do sounds match intended tone? |
| Meaning | Is meaning clear and positive? |
| Cultural | Does it fit context and audience? |
| Functional | Does it work in practice? |
Problems often come from layer conflicts:
Based on identified state and conflicts.
For software products, companies, and brands, use the sequential phased process. This produces significantly better results than combining phases.
Critical: Run phases in separate sessions. Complete each fully before proceeding.
| Phase | Goal | Output |
|---|---|---|
| 1. Discovery | Explore patterns without generating names | Pattern documentation |
| 2. Synthesis | Generate candidates from patterns | 50-100 raw candidates |
| 3. Evaluation | Filter through layer criteria | Ranked shortlist |
| 4. Validation | Verify against external reality | Validated finalists |
| 5. Documentation | Record decision and rationale | Naming package |
Why sequential matters:
See naming-framework.md → "Professional Naming Process (Sequential)" for full methodology.
Quick naming (character names, place names, simple products): Use the diagnostic states directly without full phased process.
Focus on:
Focus on:
Hand off to conlang skill for systematic culture-building.
Focus on:
Focus on:
Add flow sounds (l, r, vowels) or soften consonants.
Add power sounds (k, t, p) or shorten syllables.
Add distinctive phoneme or unusual combination.
Shift toward high-frequency English phonemes.
Check category conventions; update to current patterns.
Trying to communicate everything in one name. Fix: Pick one primary message.
Meaning only creators understand. Fix: Test with naive users.
Too similar to existing names. Fix: Check competitors; verify distinctiveness.
Looks interesting but no one can say it. Fix: Test pronunciation; simplify clusters.
Random apostrophes for "exotic" feel. Fix: If using, define what they mean; use sparingly.
| Skill | Integration |
|---|---|
| conlang | Generate phoneme inventories for consistent naming systems |
| worldbuilding | Names should reflect cultural evolution |
| cliche-transcendence | Avoid default names for character roles |
| sensitivity-check | Audit for unintended associations |
Client: "We came up with 'Vortek' for our meditation app but it doesn't feel right."
Your approach:
Writer: "My fantasy characters are named Kael, Brightwood, and Zephyrine and they feel like they're from different books."
Your approach:
Founder: "Nobody remembers our company name 'Streamline Solutions'"
Your approach:
This skill writes primary output to files so work persists across sessions.
Before doing any other work:
context/output-config.md in the projectexplorations/naming/ or a sensible location for this projectcontext/output-config.md if context network exists.naming-output.md at project root otherwiseFor this skill, persist:
| Goes to File | Stays in Conversation |
|---|---|
| Naming state diagnosis | Clarifying questions |
| Layer-by-layer analysis | Discussion of preferences |
| Candidate evaluation | Brainstorming |
| Decision rationale | Real-time feedback |
Pattern: {project}-naming-{date}.md
Example: app-name-naming-2025-01-15.md
Your role is diagnostic: identify what's wrong, explain why, and guide toward solutions that work across all layers.
The best names seem obvious in retrospect. "Of course it's called that." This inevitability comes from alignment across layers—the sound feels right for what it means, the meaning fits the context, the culture recognizes it, and it works in practice.
Bad names have hidden conflicts. Good diagnosis reveals them. Great naming resolves them into alignment.
© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/general/ideation/naming of jwynia/agent-skills.
Open the folder on GitHubat commit e02ec7e
Naming next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Naming this skilljwynia/agent-skills | 169 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Idea Refinementaddyosmani/agent-skills | 103k | 6 repos | ~2k | Automated safety check: Pass | MIT | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Brainstormingxpinjection/test-driven-spring-boot | 112 | 54 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Typesafe AIOpenAgentsInc/openagents | 455 | 9 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Yao Meta Skillyaojingang/yao-meta-skill | 2.7k | — | ~768 | Automated safety check: Pass | MIT |
addyosmani/agent-skills
Guides a conversation that takes a vague idea through divergent and convergent thinking and ends in a markdown one-pager covering scope and assumptions.
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
xpinjection/test-driven-spring-boot
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
OpenAgentsInc/openagents
Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives.
yaojingang/yao-meta-skill
Create, improve, or evaluate an existing skill from workflows, prompts, SOPs, scripts.
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
jwynia/agent-skills
Diagnose devcontainer configuration problems and guide development environment setup.
jwynia/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality.
jwynia/agent-skills
Orchestrate agile development workflows for Gitea repositories using the tea CLI.
jwynia/agent-skills
Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.
jwynia/agent-skills
Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.
jwynia/agent-skills
Create and manipulate PowerPoint PPTX files programmatically.
Diagnose why names don't work and guide creation of names that do. Naming is an agent skill from jwynia/agent-skills. Diagnose why names don't work and guide creation of names that do.
Naming fits situations like: character names; titles when something feels off; systematic naming is needed.
Run `npx skills add jwynia/agent-skills --skill naming -a claude-code`. Or copy the skill folder (skills/general/ideation/naming in jwynia/agent-skills) into .claude/skills/naming in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jwynia/agent-skills --skill naming -a codex`. Or copy the skill folder (skills/general/ideation/naming in jwynia/agent-skills) into .agents/skills/naming in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill naming -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/naming, .gemini/skills/naming, .github/skills/naming and .opencode/skills/naming in your project.
SKILL.md names no scripts, command-line tools or credentials: Naming is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Naming is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.6k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Naming: Idea Refinement (addyosmani/agent-skills, 103k stars), Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Brainstorming (xpinjection/test-driven-spring-boot, 112 stars) and Typesafe AI (OpenAgentsInc/openagents, 455 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 169 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.
Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.