vocabulary

Enforce a canonical noun-and-verb registry for naming NLPM artifacts.

111|29|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/xiaolai/nlpm --skill vocabulary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vocabulary
Source: https://github.com/xiaolai/nlpm/tree/main/codex/skills/vocabulary
Command: npx skills add https://github.com/xiaolai/nlpm --skill vocabulary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The vocabulary skill prevents inconsistent naming across NLPM artifacts by providing a single canonical registry of nouns and verbs, so scoring and checking can reliably detect drift instead of silently accepting synonyms.

Core Features & Use Cases

  • Canonical registry for naming: Standardizes the nouns and verbs used in commands, agents, skills, rules, workflows, and prose descriptions.
  • Drift detection and penalties: Enables /nlpm:check and /nlpm:score to flag synonym usage and enforce consistent terminology across the NLPM codebase.
  • Two-scope vocabulary boundaries: Distinguishes internal vs auditor scope terms to prevent homonym confusion while allowing sanctioned cross-scope identity where meanings match.

Quick Start

Use the vocabulary skill when writing or reviewing any NLPM artifact name or description by choosing terms directly from this registry instead of coining new synonyms.

Frequently Asked Questions about vocabulary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent vocabulary drift across NLPM artifacts?

To prevent vocabulary drift, use a canonical noun-and-verb registry that enforces consistent naming across commands, agents, skills, rules, and workflows so scoring and checking reliably detect synonyms.

What is vocabulary drift in naming conventions for NLP artifacts?

Vocabulary drift occurs when identical concepts use different synonym names across NLPM artifacts, causing confusion. A canonical registry standardizes naming conventions to ensure the same concepts keep the same names across internal and auditor scopes.

How do I enforce consistent terminology across commands, agents, and skills?

You enforce consistent terminology by registering canonical nouns and verbs in YAML frontmatter. This enables deterministic discovery by scorer and checker agents that detect and penalize synonym usage across your artifacts.

Can I distinguish internal scope from auditor scope terms for NLPM artifacts?

Yes, you can distinguish internal scope from auditor scope terms. This two-scope vocabulary boundary prevents homonym confusion while allowing sanctioned cross-scope identity where meanings match across your artifacts.

Does quality assurance drift detection support YAML frontmatter registration?

Yes, drift detection and quality assurance support YAML frontmatter registration. This provides deterministic discovery so checking and scoring agents can automatically flag synonym usage and enforce canonical naming conventions.

What are the limitations of using a canonical noun-and-verb registry for NLPM artifacts?

The registry requires strict adherence to YAML frontmatter registration and predefined naming conventions. It limits coining new synonyms, meaning all authors and reviewers must choose terms directly from the registry to avoid checker penalties.