metaskill-naming

# Naming Plugins and Atoms

Brainstorm and validate names for plugins and their components (atoms = skills/agents/commands).

## The Core Convention

### Verb Form by Type

| Type | Grammatical Form | Meaning | Suffix Pattern |
|------|-----------------|---------|----------------|
| **Skill** | Gerund (-ing) | "the activity of..." | -ing |
| **Agent** | Agent noun | "one who does..." | -er, -or, role noun |
| **Command** | Imperative | "do this" | base verb |

### The Golden Rule

**Plugin name = Common prefix of all atoms = Neutral noun**

```
✅ GOOD prefix (noun):
   skillsmith-    → skillsmith-authoring, skillsmith-tester, /skillsmith-create
   codeforge-     → codeforge-reviewing, codeforge-reviewer, /codeforge-review
   datakit-       → datakit-processing, datakit-processor, /datakit-process

❌ BAD prefix (already verb-formed):
   skill-authoring-  → skill-authoring-??? (prefix is already -ing!)
   code-review-      → code-review-??? (prefix looks like imperative!)
```

### No Type Postfixes

```
✅ GOOD: metaskill-authoring, metaskill-tester
❌ BAD:  metaskill-authoring-skill, metaskill-tester-agent
```

The directory structure already indicates the type.

## Brainstorming Process

### Step 1: Identify the Domain

What is this plugin about? Write 3-5 words describing the core activity:
- "creating skills for Claude Code"
- "reviewing code for security"
- "managing database migrations"

### Step 2: Find Neutral Noun Candidates

Transform the domain into neutral noun forms:

| Domain | Noun Candidates |
|--------|-----------------|
| creating skills | skillsmith, skillforge, skillcraft, skillkit |
| reviewing code | codeforge, codescan, codeguard, codewatch |
| managing databases | datakit, dataforge, dbsmith, migrator |

**Naming patterns that work:**
- **-smith**: One who forges (skillsmith, codesmith)
- **-forge**: Place where things are made (skillforge, codeforge)
- **-craft**: The craft of making (skillcraft, codecraft)
- **-kit**: Toolkit for (skillkit, dat