metaskill-naming

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Naming Plugins and Atoms

插件与原子命名

Brainstorm and validate names for plugins and their components (atoms = skills/agents/commands).
为插件及其组件(原子 = Skill/Agent/命令)构思并验证名称。

The Core Convention

核心规范

Verb Form by Type

按类型区分动词形式

TypeGrammatical FormMeaningSuffix Pattern
SkillGerund (-ing)"the activity of..."-ing
AgentAgent noun"one who does..."-er, -or, role noun
CommandImperative"do this"base verb
类型语法形式含义后缀模式
Skill动名词(-ing)“……的行为”-ing
Agent施动名词“执行……的角色”-er、-or、角色名词
Command祈使语气“执行此操作”动词原形

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!)
插件名称 = 所有原子的通用前缀 = 中性名词
✅ 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.
✅ GOOD: metaskill-authoring, metaskill-tester
❌ BAD:  metaskill-authoring-skill, metaskill-tester-agent
目录结构已能表明类型。

Brainstorming Process

构思流程

Step 1: Identify the Domain

步骤1:确定领域

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"
该插件的核心用途是什么?用3-5个词描述核心活动:
  • “为Claude Code创建Skill”
  • “为代码进行安全审查”
  • “管理数据库迁移”

Step 2: Find Neutral Noun Candidates

步骤2:寻找中性名词候选

Transform the domain into neutral noun forms:
DomainNoun Candidates
creating skillsskillsmith, skillforge, skillcraft, skillkit
reviewing codecodeforge, codescan, codeguard, codewatch
managing databasesdatakit, 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, datakit)
  • -bench: Workbench for (skillbench, codebench)
  • -works: Workshop (skillworks, dataworks)
  • meta-: Meta-level tools (metaskill, metadata)
  • -guard/-watch: Protective monitoring (codeguard, datawatch)
将领域转换为中性名词形式:
领域名词候选
创建Skillskillsmith, skillforge, skillcraft, skillkit
代码审查codeforge, codescan, codeguard, codewatch
数据库管理datakit, dataforge, dbsmith, migrator
有效的命名模式:
  • -smith: 打造者(skillsmith, codesmith)
  • -forge: 创作场所(skillforge, codeforge)
  • -craft: 创作技艺(skillcraft, codecraft)
  • -kit: 工具包(skillkit, datakit)
  • -bench: 工作台(skillbench, codebench)
  • -works: 工坊(skillworks, dataworks)
  • meta-: 元级工具(metaskill, metadata)
  • -guard/-watch: 防护监控(codeguard, datawatch)

Step 3: Generate Atom Names

步骤3:生成原子名称

For each candidate prefix, generate the full set:
Prefix: skillsmith
├── Skills (-ing):
│   ├── skillsmith-authoring
│   ├── skillsmith-triggering
│   └── skillsmith-packaging
├── Agents (role noun):
│   ├── skillsmith-trigger-tester
│   └── skillsmith-quality-checker
└── Commands (imperative):
    ├── /skillsmith-create
    └── /skillsmith-test
针对每个候选前缀,生成完整的名称集合:
Prefix: skillsmith
├── Skills (-ing):
│   ├── skillsmith-authoring
│   ├── skillsmith-triggering
│   └── skillsmith-packaging
├── Agents (role noun):
│   ├── skillsmith-trigger-tester
│   └── skillsmith-quality-checker
└── Commands (imperative):
    ├── /skillsmith-create
    └── /skillsmith-test

Step 4: Validate Names

步骤4:验证名称

Check each name against:
  • Prefix is neutral noun - not a verb form
  • Skills end in -ing - gerund form
  • Agents end in role noun - -er/-or or natural role
  • Commands end in imperative - base verb
  • No type postfixes - no -skill, -agent, -command
  • Pronounceable - can say it out loud
  • Memorable - distinctive enough to remember
  • No conflicts - doesn't clash with existing plugins
对照以下标准检查每个名称:
  • 前缀为中性名词 - 非动词形式
  • Skill以-ing结尾 - 动名词形式
  • Agent以角色名词结尾 - -er/-or或自然角色名词
  • Command以祈使动词结尾 - 动词原形
  • 无类型后缀 - 不添加-skill、-agent、-command
  • 易于发音 - 可口头念出
  • 易于记忆 - 具有足够辨识度
  • 无冲突 - 不与现有插件名称重复

Step 5: Test with Full Table

步骤5:用完整表格测试

PrefixSkillAgentCommand
skillsmithskillsmith-authoringskillsmith-author/skillsmith-author
skillsmith-triggeringskillsmith-trigger-tester/skillsmith-trigger
skillsmith-groupingskillsmith-group-designer/skillsmith-group
Does the table look consistent? Do the names feel natural?
前缀SkillAgentCommand
skillsmithskillsmith-authoringskillsmith-author/skillsmith-author
skillsmith-triggeringskillsmith-trigger-tester/skillsmith-trigger
skillsmith-groupingskillsmith-group-designer/skillsmith-group
表格中的名称是否一致?名称是否自然?

Example: This Plugin

示例:本插件

Domain: "meta-tooling for creating Claude Code skills"
Brainstorming:
  • skillsmith, skillforge, skillcraft → good but generic
  • metaskill → captures "meta" aspect, clear noun
  • skillet → fun but might confuse with cooking
Chosen:
metaskill
TypeNameFollows Convention?
Pluginmetaskill✓ Neutral noun
Skillmetaskill-authoring✓ Ends in -ing
Skillmetaskill-triggering✓ Ends in -ing
Skillmetaskill-grouping✓ Ends in -ing
Skillmetaskill-packaging✓ Ends in -ing
Skillmetaskill-naming✓ Ends in -ing
Agentmetaskill-trigger-tester✓ Ends in role noun
领域: "为创建Claude Code Skill提供元工具支持"
构思过程:
  • skillsmith, skillforge, skillcraft → 不错但过于通用
  • metaskill → 体现“元”属性,明确为名词
  • skillet → 有趣但易与烹饪工具混淆
最终选择:
metaskill
类型名称是否符合规范?
插件metaskill✓ 中性名词
Skillmetaskill-authoring✓ 以-ing结尾
Skillmetaskill-triggering✓ 以-ing结尾
Skillmetaskill-grouping✓ 以-ing结尾
Skillmetaskill-packaging✓ 以-ing结尾
Skillmetaskill-naming✓ 以-ing结尾
Agentmetaskill-trigger-tester✓ 以角色名词结尾

Common Pitfalls

常见误区

1. Verb-Form Prefix

1. 动词形式前缀

❌ skill-authoring-trigger    # "skill-authoring" is already -ing
✅ metaskill-triggering       # "metaskill" is noun, "-triggering" is -ing
❌ skill-authoring-trigger    # "skill-authoring"已是-ing形式
✅ metaskill-triggering       # "metaskill"是名词,"-triggering"是-ing形式

2. Awkward -ing Forms

2. 生硬的-ing形式

When -ing sounds unnatural, rephrase the activity:
❌ metaskill-trigger          # Missing -ing
❌ metaskill-triggering       # Could mean "firing events"
✅ metaskill-triggering       # Context: "configuring triggers" (acceptable)
✅ metaskill-trigger-tuning   # Alternative: explicit "tuning"
当-ing形式听起来不自然时,重新表述活动:
❌ metaskill-trigger          # 缺少-ing
❌ metaskill-triggering       # 可能被误解为“触发事件”
✅ metaskill-triggering       # 上下文:“配置触发器”(可接受)
✅ metaskill-trigger-tuning   # 替代方案:明确表述为“调优”

3. Conflicting Meanings

3. 含义冲突

Test if the name could mean something else:
  • "triggering" → firing events? or configuring triggers?
  • Context usually disambiguates, but consider alternatives if confusing
测试名称是否有其他含义:
  • "triggering" → 是触发事件?还是配置触发器?
  • 上下文通常能消除歧义,但如果容易混淆,可考虑替代名称

Quick Reference Card

快速参考卡

┌─────────────────────────────────────────────────────────────────┐
│                    NAMING CONVENTION                            │
├─────────────────────────────────────────────────────────────────┤
│  Plugin Name = Common Prefix = NEUTRAL NOUN                     │
│                                                                 │
│  ┌──────────┬────────────────────┬─────────────────────────┐   │
│  │   Type   │   Suffix Form      │   Example               │   │
│  ├──────────┼────────────────────┼─────────────────────────┤   │
│  │ Skill    │ -ing (gerund)      │ metaskill-authoring     │   │
│  │ Agent    │ -er/-or (role)     │ metaskill-trigger-tester│   │
│  │ Command  │ imperative verb    │ /metaskill-create       │   │
│  └──────────┴────────────────────┴─────────────────────────┘   │
│                                                                 │
│  ❌ NO type postfixes: -skill, -agent, -command                 │
│  ❌ NO verb-form prefixes: reviewing-, authoring-               │
└─────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────┐
│                    NAMING CONVENTION                            │
├─────────────────────────────────────────────────────────────────┤
│  Plugin Name = Common Prefix = NEUTRAL NOUN                     │
│                                                                 │
│  ┌──────────┬────────────────────┬─────────────────────────┐   │
│  │   Type   │   Suffix Form      │   Example               │   │
│  ├──────────┼────────────────────┼─────────────────────────┤   │
│  │ Skill    │ -ing (gerund)      │ metaskill-authoring     │   │
│  │ Agent    │ -er/-or (role)     │ metaskill-trigger-tester│   │
│  │ Command  │ imperative verb    │ /metaskill-create       │   │
│  └──────────┴────────────────────┴─────────────────────────┘   │
│                                                                 │
│  ❌ NO type postfixes: -skill, -agent, -command                 │
│  ❌ NO verb-form prefixes: reviewing-, authoring-               │
└─────────────────────────────────────────────────────────────────┘

Related Skills

相关Skill

  • For skill structure and writing, see
    /metaskill-authoring
  • For trigger optimization, see
    /metaskill-triggering
  • For skill group patterns, see
    /metaskill-grouping
  • For plugin packaging, see
    /metaskill-packaging
  • 如需了解Skill结构与编写,请查看
    /metaskill-authoring
  • 如需优化触发器,请查看
    /metaskill-triggering
  • 如需了解Skill分组模式,请查看
    /metaskill-grouping
  • 如需插件打包,请查看
    /metaskill-packaging