From example-skills
Renames projects, repositories, systems, and concepts with dense ontological titles combining essence, function, domain using -/-- separators. Provides Latin/Greek translations. Use for naming/renaming.
How this skill is triggered — by the user, by Claude, or both
Slash command
/example-skills:ontological-renamerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create dense, meaningful names for projects, systems, and concepts using ontological principles and classical language translations.
Create dense, meaningful names for projects, systems, and concepts using ontological principles and classical language translations.
What IS the thing? (noun/subject)
Questions:
- What category does it belong to?
- What is its fundamental nature?
- What metaphor best describes it?
Examples:
- A collection → repository, vault, archive
- A process → engine, forge, factory
- A connection → bridge, link, weave
What does it DO? (verb/action)
Questions:
- What transformation does it perform?
- What problem does it solve?
- What capability does it provide?
Examples:
- Creates → forge, builder, generator
- Connects → bridge, link, mesh
- Organizes → lattice, matrix, graph
What CONTEXT does it operate in?
Questions:
- What field or industry?
- What system or ecosystem?
- What users or actors?
Examples:
- AI/ML → agent, model, neural
- Development → code, build, deploy
- Knowledge → wisdom, expertise, craft
Form a 3-4 word compound that reads like a dense sentence.
Pattern: [Domain]-[Function]--[Essence]-[Modifier]
Examples:
- agent-skill--knowledge-forge
- code-craft--pattern-vault
- data-weave--insight-engine
Use for magnetically close concepts that form a compound:
skill-bundle → "bundle of skills" (compound noun)
agent-powered → "powered by agents" (adjective)
code-craft → "craft of coding" (compound noun)
knowledge-base → "base of knowledge" (compound noun)
Use for conceptual distance or category separation:
agent-skills--knowledge-engine
├── agent-skills (what it contains)
└── knowledge-engine (what it is)
frontend-toolkit--design-system
├── frontend-toolkit (domain)
└── design-system (function)
| Relationship | Separator | Example |
|---|---|---|
| Adjective + Noun | - | smart-agent |
| Noun + Noun (compound) | - | skill-bundle |
| Category + Instance | -- | dev-tools--linter |
| Domain + Function | -- | ml-ops--model-registry |
| What + How | -- | data--transform-engine |
When forming names, filter out:
Articles: a, an, the
Prepositions: of, for, to, in, on, by, with
Conjunctions: and, or, but
Strong Nouns:
✓ forge, vault, engine, lattice, codex
✗ thing, stuff, helper, manager
Active Verbs:
✓ forge, weave, craft, build
✗ do, make, handle, process
Specific Terms:
✓ authentication, pipeline, schema
✗ security, flow, structure
| Domain | Strong Words |
|---|---|
| AI/Agents | agent, model, neural, inference, swarm |
| Development | code, build, deploy, pipeline, stack |
| Data | schema, query, transform, pipeline |
| Security | vault, shield, guard, sentinel |
| Knowledge | codex, archive, wisdom, expertise |
| English | Latin | Greek |
|---|---|---|
| skill | ars, artis | technē |
| knowledge | scientia | epistēmē, gnōsis |
| agent | agens, agentis | praktōr |
| forge | fabrica | chalkeion |
| vault | camera | thalamos |
| codex | codex | biblos |
| mastery | magisterium | epistasia |
| bundle | fasciculus | desmos |
| craft | ars | technē |
| power | potestas | dynamis |
skill-codex--agent-mastery
├── Latin: artium-codex--agentis-magisterium
└── Greek: technōn-biblos--praktoros-epistasia
agent-skill--knowledge-forge
├── Latin: ars-agentis--scientia-fabrica
└── Greek: technē-praktor--epistēmē-chalkeion
Context: A repository of skills that extend AI agent capabilities.
Step 1: Essence
Step 2: Function
Step 3: Domain
Step 4: Generate Candidates
1. agent-skill--knowledge-forge
"A forge of knowledge for agent skills"
2. skill-codex--agent-mastery
"A codex of skills for agent mastery"
3. capability-weave--agent-loom
"A loom that weaves agent capabilities"
4. praxis-bundle--agent-expertise
"A bundle of practical expertise for agents"
5. craft-matrix--agent-powers
"A matrix of crafts that power agents"
Step 5: Evaluate
| Name | Clarity | Memorability | Domain Fit |
|---|---|---|---|
| skill-codex--agent-mastery | High | High | High |
| agent-skill--knowledge-forge | High | Medium | High |
| capability-weave--agent-loom | Medium | Medium | Medium |
Winner: skill-codex--agent-mastery
Context: A library for handling user authentication.
Candidates:
1. auth-guard--access-sentinel
"A sentinel guarding access through authentication"
2. identity-forge--credential-vault
"A vault of credentials from an identity forge"
3. login-shield--session-keeper
"A shield and keeper of login sessions"
When generating names, provide:
naming_proposal:
context: "Brief description of what's being named"
candidates:
- name: "english-compound--name"
meaning: "What this name conveys"
latin: "latin-translation"
greek: "greek-translation"
pros: ["list", "of", "strengths"]
cons: ["list", "of", "weaknesses"]
recommendation:
name: "recommended-name"
rationale: "Why this is the best choice"
❌ Generic Names
my-project, cool-tool, awesome-thing
❌ Overloaded Terms
manager, handler, service, util
❌ Acronyms Without Meaning
XYZPT, QWERT
❌ Too Long
super-advanced-machine-learning-based-intelligent-agent-system
❌ Unclear Separators
agent_skill-knowledge--forge (mixing _ and -)
✓ Evocative Metaphors
forge, vault, weave, lattice
✓ Domain-Specific Terms
codex, praxis, schema
✓ Clear Compound Structure
skill-bundle, knowledge-forge
✓ Balanced Length (2-5 words)
agent-skill--knowledge-forge
references/naming-patterns.md — Compound naming patternsreferences/separator-conventions.md — Detailed separator rulesreferences/translation-guide.md — Latin/Greek translation guidancereferences/workflow-integration.md — Ecosystem integrationassets/word-roots.md — Common Latin/Greek rootsnpx claudepluginhub a-organvm/a-i--skills --plugin document-skillsProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.